Posts made by Foxy

I have to own up that it turns out to be my fault. Terminating the very heavy duty cable ,even with a 2-part RJ45 was a pig, as the individual wires are very tight in the 8 holes, and despite my best efforts while pushing them in 2 had crossed. When I used the cable tester I only looked at the lights at one end...didn't realise that the remote end could be displaying something different. Still worked for internet browsing, speed test and the camera, except when adding the switch. Live and learn.

In short, the problem lies in the new cat6 cable to the garage, passes test but maybe a high res contact..

Progress today: but describing it seems to breach the community guidelines somewhere, and I can't see where.

@joseph_1979
Thanks again.. I may or may not be quite following your 2nd sentence.. Nothing is active on this laptop other than the ethernet adapter, so the only IP in use is the one set as the ipv4 address of the PC, 192.168.1.100. The address of the camera is 192.168.1.103. ip config only lists the 100 address. What do you mean by gateway IP in this context? I understand (ish) that a default gateway only comes into play if moving data from one LAN to another (via a router)?

@joseph_1979 That's exactly what I have done
By turning off ivP6 (which I believe the cameras do not support) I can now ping the camera, but still no connection.
When working via my main PC and router the camera is dicoverable on the network, so I guess it's domething in the laptop LAN config...

@joseph_1979
Reverting firmware didn't change the issue so I connected the doorbell via a short ethernet cable directly to the LAN port on my laptop (no switch). Set the laptop to the same IP address (diff host No), established the 'unidentified network', but got no connection at the Reolink client. Tried pinging and get 'destination host unreachable' with no packet loss (i.e. not sent / no route). My networkink knowledge is minimal, so I can't figure out why. (Firewall is off). ipconfig shows no default gateway...is that right?

@joseph_1979 Thanks for your suggestion.. DHCP is active. I'll await the easy firmware rollback though before trying anything else. It's not POE, and works OK over WiFi, but signal to the location is weak, hence (attempted) move to ethernet.

@joseph_1979
Indeed it should.... This is a simple home network. No VLAN. An unmanaged switch on an otherwise direct line to the router. I've tried two switches and one old router operating as a switch. Only the latest switch connects at all, but drops the connection after a few seconds. Rinse and repeat every so often. Makes no difference if there is no other client on the switch. Anything else that I do put on the switch works fine (Inverter for solar stats and a laptop for speedtest, so far)

@joseph_1979
Thanks... Yes, I realise that's the 'proper' way, and tried asking via support chat, but they suggest it will be 24hrs before replying.
Seems a bit dumb that they don't include the last prior version on the download links.... rolling back is a very frequent requirement, and Reolink don't seem any better than average at doing adequate pre-release testing.
At the moment I'm on the 11th email exchange with Support (starting 7th March) to try and establish why the doorbell camera won't communicate over ethernet with the router if there is a switch inbetween.

Could someone possibly post a link to the previous version of the firmware? I want to see if it is the new one that's causing my issues and as it's a new doorbell I don't have any earlier pak files.
Thanks!

Today I changed from WiFi to Ethernet after a full reset, and coincidentally or not, the doorbell notification setting saves.
I can't tell whether it works or not though, because connecting via a switch has almost completely killed connectivity!

@ruben-vanlommel_60754004429
No, just installed the update and can enable the new doorbell notification, but as you state, it does not save, or work while the setting page is open.

@wolfgang_789771938767034
I think (but open to correction) that the notification sound is entirely controlled by the phone, so can only be on or off for any notification from the reolink app.