Axis M2036-LE: Only single entity displayed #109029
Assignees
Labels
Comments
|
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 |
|
There was another similar report home-assistant/home-assistant.io#24655, but unfortunately it was posted in the wrong section and never got answered. cc @renaatdb |
|
I have tried to downgrade to Axis OS 10.12.213 including a factory reset, removed and re-added the camera in HA, but the issue unfortunately remains. The only things I can find in the debug log are |
|
I also checked that the MQTT Broker configured in HA receives messages from the Axis device: The Axis device connects to the broker just fine and the connect message is received in the HA MQTT frontend when listening for though no entities are automatically discovered (automatic discovery is turned on). |
|
I've added the ONVIF integration, which finds 5 entities for the AXIS camera. In order to debug this further, here's the Click to expand
There are a few interesting lines, e.g. is answered with |
|
MQTT endpoint requires admin settings to switch to using, I have to admit that the mqtt source is not as well tested as the rtsp source yet. |
Thank you for your reply. I have changed the HomeAssistant user role to Do you have any more ideas how to debug this further? |
You can enable debug logging per the instructions in the integration documentation. It could be that no additional entities are created if the device does not provide any supported data, do you have any motion detection settings configured? |
Already done, here's the full log when reloading the Axis integration: And when reloading the MQTT integration
Yes, I have enabled both applications for object and motion detection and also set up two event rules, one including the option to publish an MQTT event. |
|
The log show nothing related to axis integration. Can you also enable debug logging for the axis library |
|
Here's the full debug log (I had forgotten to add Click to expand
|
|
The logs look fine, everything needed for setup has been shown, you don't seem to get any events over rtsp or mqtt. Without receiving the events the integration will not create any entities I see that you have changed the topic prefix, this is a current limitation I should improve but right now the integration only looks at $serial/# Im currently reworking the axis library and soon the integration and stuff like this can more easily be improved. |
Any idea why? Could this be due to a wrong configuration from my side related to the camera, HomeAssistant or the server or all I can do now is waiting until you have reworked the integration? :-)
If I got you right, I have changed the MQTT topic in the camera to $serial (and reloaded) w/o success.
\o/ |
There have been a few occurrences of people reporting it and Im not sure why it wouldn't start sending the events, it can be an issue on both sides. MQTT most definitely needs a revisit :) |
"Any" can't be correct, otherwise the Axis integration wouldn't add the entity "camera-stream"?
How would an event, which results in adding an entity, look like in the debug log? Just to understand it correctly, if I hadn't set up an MQTT broker / enabled MQTT on the camera or HA, the Axis integration would only use RTSP to query events and add entities? If MQTT is enabled, it uses both? In case of entities to add, would RTSP alone be sufficient or can a subset of all existing entities only be added over MQTT? Edit: Does the Axis integration make directly use of the MQTT integration, i.e. uses the Discovery prefix configured there for instance?
Thank you! Looking forward to testing! :) |
|
Alright, after adding the right |
|
Some time later ... I finally ran into #91558 :-( |
Do you see anything in the logs that could hint why it stops? |
|
I tried to look it up now, but I had to notice that the logs don't reach back in time far enough, what a pity! Should it pick up and loose the entities again, I will check it immediately. Edit: I see that there are occasionally events received: but it doesn't result in any entity created. The MQTT events for motion and object detection do in general work as they keep triggering custom scripts in Home Assistant. |
|
Hello! As your running the container; how is your network setup with the container? |
Camera and the HA host are on the same internal subnet (192.168.120.0/24) both with a fixed IP, connected over an OPNsense HW FW. HA and Mosquitto run together in a pod on a Debian 12 system, whereby the pod does a 1:1 port forwarding from the host to its internal container subnet (10.89.1.0/24):
The network setup hasn't been changed since I have setup the system. Besides from that, MQTT messages (QoS = 2) from the camera arrive just fine to trigger self written Motion and Object detection scripts. |
|
Do you run the container with "--network=host" a problem people run into is that the rtsp stream used by the integration to connect to the device needs to negotiate input ports for the camera to send events on |
|
Looks like it was running in If you want to try it out yourself, here's my full Click to expand
which can be started by Edit: mind the paths and volumes. |
Port mapping, which I do, can only be used with Bridge or slirp4netns networking |
So does this mean my setup cannot work, because I'd need to forward these ports into the container? |
|
So I will of course improve the MQTT in the Axis integration and I might also add the option to supply a port range to configure RTSP ports within (#110794) but I can't promise when I get to it. |
No problem, thank you very much for your efforts anyway! :) |
|
Hey @mesonium ! With 2024.4.0 there are improvements to the MQTT support of the Axis integration. Is it working as expected to you now? |
Hey! I'm now on 2014.04.1 but unfortunately the issue still persists. |
I know rtsp is not fixed but any improvement to mqtt? |
Hi! Sorry for the long delay, I will answer this question once I get access to the HA device again. :) |
|
Hello, |
|
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. |
|
Hello, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
I have integrated an Axis M2036-LE, but it only shows a single entity, i.e. the camera stream. There are no binary sensors or switches available.
What version of Home Assistant Core has the issue?
core-2024.1.5
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
https://www.home-assistant.io/integrations/axis/
Diagnostics information
config_entry-axis-020e5b3a2bf0c9dc5308c5bbdc060475.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
The Axis OS Firmware is 11.8.61. I run HA together with Mosquitto in a podman pod. Other devices, such as an APC UPS work fine and display all available entities. Unfortunately, there are no errors displayed in the log regarding the Axis device.
The text was updated successfully, but these errors were encountered: