home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
69.77k stars 28.92k forks source link

Onvif only works for 1 device after the 2022.8.0 core update #76156

Closed XalaTheShepard closed 1 year ago

XalaTheShepard commented 1 year ago

The problem

Hello,

I have currently 3 devices (cameras) running in my Onvif integration. This used to work without any issue. I always install the latest version of HA Core, but after the installation of HA Core 2022.8.0 none of my Onvif devices, except for the one last added, worked anymore. I have tried to delete them and add them again, but I got an error message saying that the maximum number of trying to connect was reached. They still work perfect in Onvif Device Manager. I even restored a backup of this morning with the latest 2022.7.7 HA Core version and they all worked again. But as soon as I update to HA Core 2022.8.0 the issue emerges again.

What version of Home Assistant Core has the issue?

2022.8.0

What was the last working version of Home Assistant Core?

2022.7.7

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Onvif

Link to integration documentation on our website

https://www.home-assistant.io/integrations/onvif

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant[bot] commented 1 year ago

onvif documentation onvif source (message by IssueLinks)

probot-home-assistant[bot] commented 1 year ago

Hey there @hunterjm, mind taking a look at this issue as it has been labeled with an integration (onvif) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

DaHype commented 1 year ago

Same issue since Update to New Version. Hope for fix soon..thanks

JRoc1212 commented 1 year ago

I am using 10 current model Hikvision cameras via ONVIF integration and none are working after the latest core update.

Deleting and re-adding the cameras does not work to bring them back online. Changing the user privileges to admin in the camera settings does not work either. Only solution as mentioned above is to downgrade to 2022.7.7 HA Core.

cloudbr34k84 commented 1 year ago

I have 3 cameras via the ONVIF integration and they no longer work as well

frenck commented 1 year ago

🀚 I have the same issue! πŸ‘‡ Read below

Hi there! Sorry to read you are experiencing the same issue as more people here. Nobody likes having issues 😞

Finding an issue on a GitHub issue tracker that matches your problem is kinda nice: At least you know you are not alone. So, let's leave a commit with: "Yeah, I have the same issue", or "+1!!!". 🚫 No!

Please do not create "I have the same issue" comments!

Not just this issue or this project, but anywhere on GitHub or any issue tracker on the internet even. It doesn't add to triaging the issue. It only generates noise when reading / triaging the case.

What to do instead?

Instead, go to the top of the issue, and add a πŸ‘ emoji reaction. That way, we can still see that you (and how many others) experience this issue while keeping the issue threads nice and clean.

Thanks! ❀️

../Frenck

FranMaverix commented 1 year ago

Hi, I had 4 working ONVIF ip-cameras on HA 2022.7.7 and now with 2022.8 only 3 cams are working. As I see that are more people with this issue, I think we must say what cameras work fine and what cameras not, after update, for better diagnostics.

(HA OS on Raspberry pi 4B)

My working ONVIF cameras after update:

My failed ONVIF camera after update:

ONVIF ERROR: "VictureCam No se pudo configurar"

Pardon, @frenck , I was writing this post when You published the yours... sorry

DaHype commented 1 year ago

My expensive

Blaupunkt VIO B-30 NOT working

Cheap Ctronics CTIPC-246CWS720PAN working ;-(

HA OS on Raspberry PI 3B+ 64Bit

I Had to Go Back to HAS 2022.7.7 :-(

2022-08-03 17:24:46.521 ERROR (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'General', please verify that the credentials are correct. Error: Invalid data

XalaTheShepard commented 1 year ago

My Imou camera is still working fine. My two Risco camera's can not log in.

rbartha commented 1 year ago

Hi same here. Tapo C200 is still working. Both of the H.View cameras stopped. According to the logs the login credentials are not valid what is not the case. Went back to 2022.7.7 and all works again.

rhodan412 commented 1 year ago

Am using RLK16-820D8-A NVR and Dome Cameras as well as the Duo PoE. I have tried 2022.7.7, 2022.8.0, and 2022.8.1 and the results are the same for me.

When I install the Duo PoE it will work. If I install the dome cameras (even one) the PoE goes away and is replaced by any of the dome cameras that are installed.

DaHype commented 1 year ago

2022.8.1

Also Not fixed for me. So Back to 2022.7.7 again :-((

frenck commented 1 year ago

@DaHype This issue ain't closed, and you can check the release notes for patch releases as well. No need to report it isn't fixed in X when the issue is still open. Let's keep the noise in the issues low. Thanks! πŸ‘

quikote commented 1 year ago

If it helps, in my case I only have 2 cameras in my system, model Victure PC730 and working perfectly till 2022.7.7 Now both doesn't work since 2022.8 and neither with 2022.8.1

paulaltomare commented 1 year ago

Similar issue here...had 4 Dahua cams working with the Onvif integration prior to upgrade, now only 3 work.

Usandu commented 1 year ago

Camera IP POE B4 ZINTRONIC 5MP (Based on HeroSpeed) - Same issue here, not sure if listing models help, but some did do so.

Pistoletjes commented 1 year ago

EC101-X15 360eyes.club has same issue.

mag2bue commented 1 year ago

My Hikvison camera doesn't work since 2022.8 and neither with 2022.8.1.

2022.7.7 is working fine!

DaHype commented 1 year ago

Set NTP Setting in Cam Settings ON, solved for me the issue πŸ‘

pastrybaker commented 1 year ago

Set NTP Setting in Cam Settings ON, solved for me the issue πŸ‘

Helped for me as well ☺️ Thanks a lotπŸ‘

JRoc1212 commented 1 year ago

Set NTP Setting in Cam Settings ON, solved for me the issue πŸ‘

Thanks @DaHype, NTP (Network Time Protocol) allowed HA to see my 10 Hikivsion Cameras on 2022.8.2.

For those with Hikvision cameras, log into your camera via IP address and select 'Configuration' tab, this brings you to 'System Settings' then click the 'Time Settings' tab at the top. Make sure "NTP" is selected and the default values should work (click test button to confirm) then click "Save".

I did this prior to upgrading to 2022.8.2 and post-update everything is working as it should so far.

Those with different camera brands should be able to make the change in their settings. If you need NTP values, here is what Hikvision uses as default:

Server Address: time.windows.com NTP Port: 123 Interval: 1440 minute(s)

paulaltomare commented 1 year ago

Unfortunately, setting NTP to ON did not work for me. I have 4 Dahua cams using the ONVIF integration. 3 of the 4 continue to work.

XalaTheShepard commented 1 year ago

Setting the time settings solved the issue for me. Although now the time of my camera's is off with 1 hour.

FranMaverix commented 1 year ago

I have set my Victure cam to time zone +00 and now it's working... (the NTP already was configured, but did not work)

XalaTheShepard commented 1 year ago

Setting the time settings solved the issue for me. Although now the time of my camera's is off with 1 hour.

Edit: after a reboot some camera's are offline again

XalaTheShepard commented 1 year ago

Editing the time settings using the Onvif Device Manager temporarily solved the issue for me. For some unknown reason the camera's are back unavailable after a reboot, although the time settings are not changed during the reboot.

annunity commented 1 year ago

My guess is that the time clocks on those cameras aren't super accurate and the time has deviated enough for the authentication to fail.

XalaTheShepard commented 1 year ago

Is someone still looking into this topic? I know there is a (temporary) solution with enabling the NTP server, but not all devices support this. Every time I reboot HA, I have to adjust the camera settings and this still is a hit and miss. I noticed there is also almost no feedback coming in for this issue anymore.

cloudbr34k84 commented 1 year ago

Is someone still looking into this topic? I know there is a (temporary) solution with enabling the NTP server, but not all devices support this. Every time I reboot HA, I have to adjust the camera settings and this still is a hit and miss. I noticed there is also almost no feedback coming in for this issue anymore.

i have reolink cameras and they are not working still

quikote commented 1 year ago

Is someone still looking into this topic? I know there is a (temporary) solution with enabling the NTP server, but not all devices support this. Every time I reboot HA, I have to adjust the camera settings and this still is a hit and miss. I noticed there is also almost no feedback coming in for this issue anymore.

My Venture cameras still not working neither. This camera has no NTP option in the settings so I think an update in the HA core is needed to solve the problem. The cameras worked flawlessly till 2022.07.*

n2ocharged commented 1 year ago

How do you go back to a previous version?

DaveeKol commented 1 year ago

Hallo,

I have 2 cameras, Dahua and Hico and no one can connect to HA from 2022.8 So I have last version of 2022.7 and waiting for resolve this issue. Will be resolve in future? Why the connection is interupt?

ljmellor commented 1 year ago

I've just managed ot overcome this issue for the first time in the 2022.8 branch. It appeared that my issue was down to daylight savings time here in the UK. Having recently had a camera replaced under warranty I'd quickly thrown a config together whilst in a rush and accidentally set the time zone wrong. Upon upgrade to 2022.8.7 I noticed that just the new camera was working, upon inspection I noticed that it displayed the time correctly but mentioned +08:00 on the end.

As a result I've gone into my other 3 cameras (Lilin 5mp models), set it to sync with an NTP server on my network with a time zone of Taipei +8.:00, then DISABLED ntp syncing and synced the time up with my laptop via the camera's interface. It now shows the correct time with (+08:00) on the end but the time displays correctly in the camera feed.

Hopefully this helps others and may give some insight into a real fix. I can only presume that the devs live in an area where daylight savings isn't used (most countries other than the UK).

KimCarlsen commented 1 year ago

7 out of 8 cameras didn't work on 2022.8.7, so i tried the brand new release 2022.9.0 and that made all of the cameras die. reverted back to old version, and was back to one working one. All cameras have NTP set, and tried with and without DST, with no changes.

paulaltomare commented 1 year ago

I could not get 1 of 4 cameras to work after upgrading to .8 even with identical settings to the other 3. It is a Dahua Cam so I was able to get it back using the Dahua integration instead of Onvif just for the 1 cam.

enkikus commented 1 year ago

I have a Dahua cam (model IMOU Looc) that didn't work and this morning I've tried to apply the opcion PC Sync using the sofware ToolBox > Config Tool and it worked! Hope this could be a useful tip for Dahua cam owners.

DaveeKol commented 1 year ago

Hallo,

I unchecked on both cameras DST setting in time and move time-zone about 1 hour to the next zone (from UTC-1 to UTC-2 in my case). So time is good and now with Onvif integration is OK and normally connected! So my solution was no use DST setting. BUT I must manually move time-zone every DST change (twice per year).

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment πŸ‘ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.