Axis camera motion sensor becomes unavailable #91558
Comments
|
The issue still occurs in 2023.5.0 |
|
Hey there @Kane610, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) axis documentation |
|
Hello. Do you get any errors in the logs? Can you enable debug logging for the Axis integration and share logs when it happen? |
|
Hi. No, there are neither errors nor warnings. They just become unavailable. I just reloaded the integration and the motion sensors became available. I enabled debug logging. Once they become unavailable I will attach the log. |
|
Hi. I run HA as a container. It appears that when I reset the container and start it, the binary_sensors of my two P3228 just remain unavailable. They will not become available later. I am no longer sure whether they become unavailable or whether they are unavailable from the beginning. However, this only appears when resetting the container and when HA is initialized. When reloading the integration und restating HA they remain available. I will check further if they will become unavailable. Here's the log |
|
I kept an eye on it. It appears that after restarting HA the binary_sensors become unavailable. HA was stopped/started at around 10:39 The binary sensor became unavailable: Here's the log |
|
You mean that when restarting core it becomes unavailable? If you reload the integration it will work? Which IP belongs to which device? |
|
Yes, when I restart core the binary sensors become unavailable, sometimes (!) And yes, if I reload the integration they become available. As far as I can see the will keep available. 192.168.10.13 = Cam-Vorgarten |
|
And Garten is the one this issue is about? |
|
No, both are affected. Both are an AXIS P3228-LVE. 192.168.10.14 = Cam-Zugang-Garten is an AXIS M3106-LVE Mk II that runs fine. |
|
What happens if you disable .13 and .14 and then restart core? Would .15 load up properly? |
|
That’s hard to predict. I need to test. It’s not every time that the binary sensors become unavailable. I hoped the log would provide more infos. |
|
It's hard to see what source data comes from and it all looks OK data wise afaics |
|
I deleted .14 and .15 restarted core and the binary sensors of .13 are unavailable. I just saw that not every binary sensor is unavailable. I don't know if this random. |
|
Hi. The issue still occurs. I just installed HA 2023.5.3 and when HA started the binary sensors were unavailable. I reloaded the integration and they became available. Please find attached the log. I saw an stream client offline messag ein line 1466 |
|
I haven't forgotten about this, I will look at the new logs shortly |
|
Thanks for the update. The main issue seems the restart of HA which results in unavailable sensors. |
The system sends a teardown just before that Regarding the unauthorised messages; are you using a viewer account on the device? The IPv6 error is something between home assistant and a client, not related to this issue. |
Does this log show the case where you start hass and the integration is not loaded and then the restart and after that it works? |
|
Yes an no. In that case a new hass version was installed (the container was updated). While updating the container hass is shut down. After I started hass the integration was loaded successfully. Only the binary_sensors were unavailable. The camera entity as well as some switches were available. Thus I reloaded the integration. After that the binary_sensors became available. All of that was logged. |
|
I'm having the same issue with the same Cameras, Axis P3228-LVE |
Are you also seeing the IPv6 error? |
|
Sorry for the slow reply. Don't believe I'm getting an IP V6 issue. I've attached the debug log. It seems to randomly disable certain sensors. |
|
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. |
|
It seems the issue is gone. |
|
Scary :/ I am continuing my work on improving the axis integration and will probably rework the related flows as time goes on. |
|
The issue still appears |
|
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. |
|
Got a separate question about a similar issue, at least you're running as container and maybe they are related. As you're running it as a container, which network mode do you have? Events are sent over RTSP meaning it negotiates its own ports to communicate, it needs "--network=host" and if you have a firewall enabled on your machine you need to configure it |
Not the same issue as OPs system works after restart. Open a separate issue |
|
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. |
issue-triage-workflows
bot
closed this as not planned
The problem
The motion sensors (vdm4) of my Axis cameras (both P3228-LVE) turn unavailable after a certain time.
When I restart HA or reload the integration the sensors are available. There is no specific warning or error in my log.
This only happens for my Axis P3228-LVE. The sensors of my M3106-LVE-MkII are working fine.
What version of Home Assistant Core has the issue?
core-2023.4.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Axis
Link to integration documentation on our website
No response
Diagnostics information
config_entry-axis-47ce93b23c1c4bee8a76864553d9854c.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: