Doorbell First New Firmware! Support More Smart Home Features & ONVIF with Two-Way Audio

[Roy Geraets_628423401263138]

@Reolink-Fiona Hey,

Do you have an update on when the new firmware will be re-released?
Really would love to work with these extra features.

Thank you and keep up the good work.

[user_655104416477196_655104416477196]

Thanks to Joris on Discord I found a github with all versions. Most firmware links to reolink official mirror.

https://[censored]/AT0myks/reolink-fw-archive

[joseph_1979]

@user_655104416477196_655104416477196 Yes, I came across this some time ago on Reddit. Ensure that the firmware loaded is the one corresponding to the HW version.

[BigBlue007_631330884632579]

@joseph-chircop_497308027822318 In case of the Doorbell, there is only one firmware variant available anyways.

I also found that archieve some days ago. Wasn't sure if it's a good idea to post this here or not, so I didn't.

The FW from there (dated 04/16/23) still doesn't enable any of the announced features regarding Smart Home integration. I still cannot enable a notification, let alone an automatically starting live stream, on an Echo device. In the Alexa app, the Doorbell still shows up as a standard camera without any of the added configurable options that a real doorbell normally shows up with. Not sure if this is something that depends on the firmware, or that would also require the new app version that is not yet available.

Still some time available for me to wait until the return window closes... But to be honest, I don't really believe that this will work in time.

[robert stein_219110424309923]

I can not tell if I have this firmware for my DOORBELL. The link you provided forces me to see a page that asks for device which no option exists for DOORBELL. My current info in settings of DOORBELL with wifi and chimes shows v3.0.0.1459_22102806 . so can you tell me if I have latest
firmware or not? Note: I am using WINDOWS 11 with MS edge browser. Checking your REOLINK website appears to need the DOORBELL
added to your devices or is it hidden under another name currently there? BTW, the DOORBELL software is working but is too slow when added to all my reolink devices to catch who's at my door like my older RING doorbell did and still does on other door which is not overloaded with other devices...

[user_655104416477196_655104416477196]

@robert-stein_219110424309923
Hi Robert,

The page on GitHub lists firmware for a lot of devices. The page you're directed to has some kind of list if you scroll a little bit down, there you will be able to click on Firmwares. Last device on the list is the doorbell WiFi.
The firmware you're currently on is the original firmware it came with. So not the latest, but as mentioned above, the updates have been pulled by Reolink. Most of the time that means there are bugs, probably major ones, in the released firmware. This website is just some 'archive'. There are 3 firmwares available for Doorbell WiFi, the original and 2 updates. The one listed as original isn't hosted by Reolink, so beware! The other download links direct you to the original Reolink server, but again, they've been pulled for a reason!

Your second question is how to access it via your browser I think? For that you'll have to find the IP-address it has on your network. To find the IP address you can go to the settings of your doorbell in the ReoLink app. (Mine is in Dutch, but I'll try to translate as good as possible)

• once you're in the settings you press on the icon of your doorbell on top of the settings page.
• next page has "network" as last option of the 'first group'
• If you tap that, you'll see the IP-address (for instance 192.168.1.100)

Now that you know the IP-Address you go to your browser and enter the following in your address bar:

http://192.168.1.100 (substitute with YOUR IP-address)

There you can sign in with the account you've created when you installed your doorbell.

As to your last question about being to slow, I don't have such a problem so it's hard for me to comment on that one. Is your signal strength okay?

[perkins tony_647500713214819]

I hope there is news on an update soon. I'm becoming increasingly frustrated with the instability of this product. I only have 4 days left to return it.

[swrobel]

The silence from Reolink here is deafening. If you pulled the firmware, just say so! It's fine, we'll wait for a fixed version, but to leave these posts up announcing that the new firmware is out, when it's not really here is maddening.

[user_630727559069699_630727559069699]

@swrobel

Regarding the WEB interface not working :

*********************************************************************************
*********************************************************************************
******* UPDATE MAY 09 ------ Possible Solution **************************
*********************************************************************************
*********************************************************************************
The solution is not logical, but it helped me regain access to the camera through a browser.

-> Inside the doorbell's setting using the reolink client, select NETWORK -> ADVANCED - SERVER SETTINGS
-> ENABLE RTMP (although it's *not* logical at all) - SAVE

It solved my problem of not being able to connect to the doorbell using a browser.

IT'S VERY DISAPPOINTING THAT CUSTOMERS NEED TO TRY THESE THINGS TO GET THINGS WORKING
I love Reolink and have about 10 devices, but this kind of support and firmware updates is just not ok.

[Keith_653336186290211]

There is no POE doorbell option in the dropdown box. Please attach the correct link for the POE doorbell firmware.

[BigBlue007_631330884632579]

@keith_653336186290211 Well, there is no Doorbell option at all! Neither PoE nor WiFi. That's what the whole discussion here is all about...

[perkins tony_647500713214819]

Submitted my return request today.... So unfortunate as I really like the product WHEN it works.

[joseph_1979]

@perkins-tony_647500713214819 So what was the issue if I may ask.

[BigBlue007_631330884632579]

@joseph_1979 Really???

[svchnetv2_528701419749624]

Seems to be back - but no info what got fixed, why it was pulled or whatsoever... Really shitty support currently...

[BigBlue007_631330884632579]

@svchnetv2_528701419749624 Indeed. Also no sign of the app update which is required for most of the announced new features. I have 5 days left before I need to return it...

The new fw has the same filesize than the one that was pulled but was still downloadable from that Github site, but has differences when doing a binary compare. So obviously no code change but just some adjustmens of some parameters.

[Paul_223190891585696]

The video of the doorbell (and all other camera's) can now be played directly in the Google home app.

Unfortunately, the Doorbell is still seen as a Camera in Google Home.

It would be great if the Doorbell would be recognized for what it's, and an action could be triggered by a ring or motion detection.

[joseph_1979]

@paul_223190891585696 Note that a new firmware has been uploaded in the download center.

[tobie_123_439581789864114]

I can confirm that I was able to download the new firmware from the download center.
Download Center – Reolink
v3.0.0.2033_23041300

Recommendation for upgrade: Because there are many updates in this version, it is recommended to check the Reset Configuration option when upgrading.

What's New

1. Release new smart home functions:
1) Support preview, 2-way audio, notification, voice wake-up on Alexa (notification will be available after finishing Cloud update);
2) Support preview, notification, and voice wake-up on Google Home (notification will be available after finishing Cloud update);
2. Support GOP settings.
3. Remove the original automatic frame drop, incorporate multi-level frame drop, and support frame rate control function
4. Support adjustable range of CDS value
5. Support working with IOT devices
6. Add status light control button for doorbell camera (Available to the App version of 4.37 or later)
7. Add ringing control switch for doorbell camera (Available to the App version of 4.37 or later)
8. Fix known bugs

[user_691429305987252_691429305987252]

Finally, it's back online !

Just tried (checked the reset configuration box) and... and now I'm stuck out of the web interface.
Cannot connect to the LAN IP address, getting a ERR_CONNECTION_REFUSED.

Tried from different browsers, computers (linux/windows), and Android devices...

From the android app, I can't figure how to access network configuration.
I get the network information, but no configuration, is this normal or am I missing something ?

After 3 weeks of tests: Too many software/firmware inconsistencies, and communication is abyssal... Still 6 days left before returning window closes.
Looks like I'm gonna switch to Dahua.

[joseph_1979]

@user_691429305987252_691429305987252 I update mine without any issue at all. However, I didn't reset the configuration.

In your case if the camera is not back in operation then you need to restore it.

[user_691429305987252_691429305987252]

@joseph_1979 Thanks for your feedback... I tried a reset (button on the back) with no success...
When you say restore you mean to put the old firware back ?

[NdR_690347593457817]

I'm trying every Firmware Update of this doorbell, but every time I understand that this is a "Beta Product" sold at his full price.

For example every time I ask to Alexa to see the Camera Doorbell, it fails saying "The Doorbell is not responding". If I ask it again, also after only 1 second, Alexa is able to show It.

Also, please fix the Product Category: this is not a "Camera" but a "Doorbell". This makes a lot of difference when connected to Alexa or Google Home.
With Doorbells you can set up some routines with the button pressed as a trigger.

[joseph_1979]

@ndr_690347593457817 Two days ago they released a new firmware. Have you installed it?

[NdR_690347593457817]

@joseph_1979 Sure, v3.0.0.2033_23041302

[BigBlue007_631330884632579]

I'm done. Sending it back today. Good luck everyone!

[BigBlue007_631330884632579]

BTW, the new app version 4.37 is available for iOS since yesterday. None of the announced Smart Home features are working though. The doorbell is still recognized as "Camera" by the Alexa app, which prevents any of the additional functions that an actual "Doorbell" device has.

[user_692920038768787_692920038768787]

@bigblue007_631330884632579 Would I be right in thinking that to have any kind of integration between the Reolink Doorbell and Alexa I would need to pay for a Reolink Cloud subscription in order to link the Reolink skill to Alexa?

[NdR_690347593457817]

@user_692920038768787_692920038768787

The skill is already available and the doorbell is working fine, but as a Camera. This means you can call it and speak with the 2way audio, but right now you need some kind of third party hub if you want the "ring" feature via Alexa. I'm using Home Assistant for this purpose, but It still has some issue: the first time Alexa open the streaming to the doorbell, it fails. If you ask it again after also 2 seconds, it's working.

[perkins tony_647500713214819]

Well, I returned my Doorbell and exchanged for a new one in hopes that would help. I now have the newer one updated to the latest firmware and twice so far I've had to remove the doorbell so I can power cycle it after it locks up hard.

[user_688312255041690_688312255041690]

@perkins-tony_647500713214819

was this an issue you previously had?
did you hav this problem with the original firmware?
mine has no problems at all, and i dont want to introduce issues by upgrading

[joseph_1979]

@perkins-tony_647500713214819 Is this the WIFI or PEO model? And what is the issue?

[perkins tony_647500713214819]

@user_688312255041690_688312255041690 I've just had general stability issues from day one. I use frigate which is up most of the time I'm at my PC so I notice things that others might not encounter. It's hard to say if the newer firmware is better or worst at this point.

[perkins tony_647500713214819]

@joseph_1979 It is the wifi model. I think the main issue I have currently is on occasion it will stop working. I did notice the last time it stopped working it eventually recovered on its own without a power cycle. Happy to share more info if you know how to capture debug info.

[joseph_1979]

@perkins-tony_647500713214819 Reolink removed the export of diagnostic file. Since you are unable to connect and don't receive any notification you consider that the doorbell stopped functioning. Can you insert a microSD and enable recording on person and visitor? When you think that it stopped working then go near camera so it will record you. Take note of the time. When it reconnects check whether you have been recorded. If yes then there is an issue on the transport (WIFI).

I also suggest you to change to 2.4G for the test as this has more range (longer wavelength). Be careful not to forward any wireshark traces .

[perkins tony_647500713214819]

@joseph_1979 Talk about perfect timing... I was just checking on responses here and noticed the doorbell cam in frigate was frozen/garbage. I went downstairs to check and the doorbell was completely dead. No light, no ring when pressing the button, nothing. Couldn't access it via browser or app. By the time I got back up stairs it was back up and working, so assuming it locked up and rebooted. I do have an sdcard in it and checked it. There was activity before and after it rebooted but nothing during the time it was locked up.

How do I force it to connect to 2.4g wifi? I do have a mesh node about 10ft from the doorbell and when it's working I have no issues with connectivity in general. I wish there was some form of core dump that could be analyzed.

[joseph_1979]

@perkins-tony_647500713214819 So you use the same SSID for both 2.4G and 5G. In this case not possible. I told them to add the feature to force camera to connect to either 2.4G or 5G but so far not implemented.

How did you power the doorbell? Using the transformer or supplied power adapter. I am thinking of power interruption considering that there was no light.

Can you recheck the power terminals?

[perkins tony_647500713214819]

@joseph_1979 I'm powering it with the existing wiring. I can double check that but I never had any issues when I had a eufy doorbell installed, so I'm thinking the power is good. I'm hoping it's good because where the doorbell is located would be a major challenge to run cables to.

[joseph_1979]

@perkins-tony_647500713214819 Are you using the power adapter provided by Reolink or you are powering it through a transformer?

[perkins tony_647500713214819]

@joseph_1979 Sorry, by existing wiring I meant the old doorbell transformer.

[perkins tony_647500713214819]

@joseph_1979 FYI, I was checking my Frigate logs the last time the doorbell appeared to lock up. It took about 2 - 3 minutes for it to recover and come back online.

[joseph_1979]

@perkins-tony_647500713214819 What is the secondary VAC of the transformer? For Reolink doorbell it has to be 12-24VAC 50/60Hz.

[perkins tony_647500713214819]

@joseph_1979 I checked at the doorbell and it's getting 18.7v

[joseph_1979]

@perkins-tony_647500713214819 That should be fine. And this is the second reolink doorbell right and yielding same symptom. I still think there is something wrong in power. How about feeding it with the provided power adapter? Just to test and eliminate AC power.

[perkins tony_647500713214819]

@joseph_1979 I'll give that a try. Thanks.

[perkins tony_647500713214819]

@joseph_1979 When using the DC adapter should I be concerned about polarity?

[joseph_1979]

@perkins-tony_647500713214819 I think it is protected as show in https://support.reolink.com/hc/en-us/articles/10300451805465-How-to-Power-Video-Doorbells-Using-Power-Cables-/ and https://www.youtube.com/watch?v=wR3oOPA8-rU

[perkins tony_647500713214819]

@joseph_1979 Ok, since the video shows the wires connected differently from the static page you sent I will assume there is not specific polarity. The video doesn't mention anything about it either.

[joseph_1979]

@perkins-tony_647500713214819 Correct.

[perkins tony_647500713214819]

@joseph_1979 Ok, the doorbell is now being powered by the supplied power adapter. Will keep you posted.

[joseph_1979]

@perkins-tony_647500713214819 Excellent. This should eliminate any power issue. Have a nice day ahead.

[perkins tony_647500713214819]

@joseph_1979 I also added my cameras to my uptime tracking tool, Uptime Kuma.

Unfortunately the doorbell has gone down and rebooted itself 3 times so far. I also disabled RTSP, RTMP and ONVIF hoping that might help. The last outage lasted about 10 minutes before it recovered.

Is there no way to get diagnostic data from the device?

[joseph_1979]

@perkins-tony_647500713214819 How do you know it rebooted three times? There is no logs available to users and the export of diagnostic file has been removed.

Rebooting is normally either a power or hardware issue. I have even came across users who fail to seal the reset cable and when it rains it causes rebooting (shorting reset button).

i think you have exhausted all the tests and the best way forward is to ask Reolink support for a replacement.

The firmware of my wifi doorbell is v.3.0.0.2033_23041300. What is your firmware?

[perkins tony_647500713214819]

@joseph_1979 I spend much of my day at my home office. I have a triple monitor setup that includes a monitor with all of my cameras displayed. I notice when a camera fails and often go to the Reolink app to access the camera. I am assuming it has locked up because the times that I've gone down to the front door and checked it the device was non responsive. No light, no doorbell ring when pressed, etc. The uptime monitoring app checks the web access URL every 30 seconds and indicates when there is no response. Those indications correspond with the times I've seen the video freeze or garble.

I am assuming at this point that when the video stops and the web interface is inaccessible, as well as access via the app, that the doorbell has locked up and some watchdog process eventually reboots it. Fortunately it DOES reboot and come back online. This is the second unit I've had that exhibits this behavior so I don't have high hopes that a 3rd unit will solve my issue but I suppose it doesn't hurt to try. Other than the unreliable Reolink implementation of RTSP ( I use the http method of capturing video ), I'm quite pleased with the other 5 Reolink cameras .

[joseph_1979]

@perkins-tony_647500713214819 I do have a lot of models including this wifi doorbell and have no issue at all. Did you check the firmware? You are using the power adapter provided by Reolink. When it is working can you use the talk function and see if it reboots?

[perkins tony_647500713214819]

@joseph_1979 Seems to be current.



I am using the supplied power adapter. The doorbell is under a porch so not exposed to rain. I submitted a return request on Amazon so will try one more unit to see if I'm just that unlucky.

I did try talk mode and it worked fine.

[joseph_1979]

@perkins-tony_647500713214819 I asked you to use the talk function as it drains more power. Logs are very important to diagnose and troubleshoot. I guess this is accessible only by support engineers. You may issue a trouble ticket to reolink support.

[perkins tony_647500713214819]

@joseph_1979 Thank you. If I continue to have this issue with the new unit I'll reach out to them. I do appreciate your help here.

[joseph_1979]

@perkins-tony_647500713214819 You're welcome. I am a customer like you but have engineering, Telcoms, computing and software skills and assist wherever possible members of this community in my free time.

[perkins tony_647500713214819]

@joseph_1979 Early indications are the 3rd doorbell is performing worse than the previous. I suspect a memory leak at this point.

Can I ask a favor? Can you install something like Uptime Kuma and set up a basic "ping" to check the health of your doorbell? I'd like to see if you have similar issues and just haven't noticed yet.

I have a theory. IF the doorbell is self recovering in a reasonable time most users probably never notice it has an issue. The ones I've tested do seem to recover but I would like to understand better what is actually wrong here.

[joseph_1979]

@perkins-tony_647500713214819 This leads us to either a firmware or hw issue. Yes, it could be a leaky buffer which can cause the camera to reboot. Do you have an older firmware to try out?

I am not at my other house. I will do the monitoring next week.

Once I told them to include uptime but was never implemented.

What is the frequency of occurrence? Every day...every other day...

You can also check that the camera stops sending messages to the P2P servers to update its public and private IP. Wireshark trace at the egress of the router will show this.

[perkins tony_647500713214819]

@joseph_1979 I did try with the original firmware and the newly updated. Lockup/reboots seem to happen multiple times per day. They typically resolve fairly quickly. I'm looking for a way to capture the actual time frame here.

The behavior is the same across 3 different doorbells, so it leads me to believe it's a firmware issue and not hw.

I'll see if I can monitor the P2P messages for additional info.

Like I said before, I'm happy that the watchdog process works on the device so I'm leaning toward keeping it and continuing the quest for a root cause here. It's hard to overcome the decades of engineering and troubleshooting mentality.

[perkins tony_647500713214819]

@joseph_1979 FYI, this is what uptime kuma sees when the unit starts to have issues then ultimately stops responding and then reboots and come back online. This is simply hitting the ip addr, http://192.168.50.60/, and checking for a http 200 response.

[perkins tony_647500713214819]

@joseph_1979 FYI, I opened a ticket with Reolink today. Hopefully they can help resolve this.

[perkins tony_647500713214819]

@perkins-tony_647500713214819 I've engaged support. I did try one other experiment and I believe I've found what contributes to the issue and why many others aren't seeing this problem. IF I remove the doorbell from my frigate/go2rtc setup so that I'm not streaming from the device 24/7, it doesn't appear to lock up and reboot. Well, at least for the last 21 hours it hasn't. And since it was rebooting about 5 times per day I'm guess this is the issue. The device is incapable of providing a reliable 24/7 video/audio stream. I've passed that info along to support and hopefully we can resolve this. My setup is designed to be completely local and leverages google coral for detection, so I need the 24/7 stream, which the 5 other Reolink cameras are doing without issue.

[perkins tony_647500713214819]

@perkins-tony_647500713214819 Support said they were unable to recreate the issue. I'm surprised at this because I was able to recreate the issue 3 times with 3 different doorbells. I'm not sure they actually set one up as I have it.

If you have time and would like to help resolve this, could you set up a frigate/go2rtc instance and configure it to pull a stream from the doorbell 24/7. Also, set up a monitoring tool to detect when the web interface becomes unavailable. This will indicate when the device has locked up. I would bet you a cup of coffee if you do this you will see the device reboot at least 5 times per day. I would be curious to see if this happens with the reolink nvr pulling the stream as well.

Thanks,

Tony

[perkins tony_647500713214819]

@joseph_1979 I posed this in a new thread, but thought I'd let you know.

A simple way to determine if you would have the same issue I'm seeing.

Open the stream in VLC and leave it running. When I did this it locked up fairly quickly and the VLC player stopped at the time of lock up. So possibly no need for a separate uptime tool.

I used fmt: http://192.168.50.60/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=***&password=***

[user_633871731654661_633871731654661]

@perkins-tony_647500713214819

I have the same problem here. I have a wifi model but I use a cable connection. I use Home Assistant, frigate with go2rtc, but even using a simple rtsp or onvif, the doorbell freezes and restarts, taking up to 2 minutes to allow a new connection. It's frustrating that after a long wait to have it, its operation lets me down when I need it most.

[user_688312255041690_688312255041690]

2 qustions

has anyon with the PoE model upgraded to the new version
mine is working perfectly and I'm worried about what it might cause with what I am seeing

@joseph_1979
its not reassuring that
the firmware was originally removed without explanation
then re-added without explanation
why was it pulled and what was changed?

[Seb_526812765704330]

@user_688312255041690_688312255041690
So far, mine working normally with new firmware

[joseph_1979]

@user_688312255041690_688312255041690 It must had something wrongly set as otherwise it would have been left.

If you notice any abnormality please report to support. I have the wifi model with the latest firmware and so far no particular noticeable issue.

We as customers wish to see more features and enhancements on this product.

If you want to be extra safe ask support to provide you with your current apk file. Upgrade with the most recent and in the event of an issue roll back to the older version.

[MikeL_694285116776640]

I have just updated to v3.0.0.2033_23041302 and the doorbell has stopped connecting by browser and Home Assistant. Still work fine in the app
Hopefully will find a way round it or they release another update soon.

Found a solution:

Go to Advanced Network settings in the app and Set Up Server Settings enable the HTTP (and others that you may want). It looks like these MUST be explicitly enabled in this new firmware.

[joseph_1979]

@mikel_694285116776640 Yes, http is disabled. But you could have used https which is enabled by default.

[michael_627201693360487]

@joseph_1979 So http was enabled on my doorbell, but ever since the firmware upgrade, TCP RTSP connections are getting refused by the doorbell. Did the URL also change? I am using:

rtsp://admin:my-secret-password@doorbell.ip.address:554/h264Preview_01_main

[carlobuzzer_664707991901016]

Dear Team,

i miss the Feature to call my Phone. Under all the push messages, you can't hear the ringing! Is something like this planned for the next update?

Best regards
Carlo

[phaseangle_594850628747928]

@carlobuzzer_664707991901016
What version was that I might roll back to that as so far I have missed all notifications.

[jleung7_664526975243058]

Signed up for the free basic cloud service, but appears the doorbell wifi isn't supported. It does say on the website that it is supported but support may vary by country. Also, when I installed the Alexa skill it was working at first but now when I press the speaker button I hear no audio. I do hear it on the native app and my ring camera. When will this be fixed? Thanks for adding ONVIF support for third party NVRs. Do Reolink NVRs support third party cameras? It says they don't.

[perkins tony_647500713214819]

I've noticed an interesting issue. I've been troubleshooting my lock up/reboot issue and have been turning on/off various settings. I just noticed that if I turn OFF RTMP the web interface stops working altogether. I can no longer access the doorbell via a browser. It seems to continue working in the app. I have to power cycle the unit to get access via web.