Axis A8105-E does not detect call button etc

[jcbrooks75]

The problem

The Axis A8105-E door station contains a camera, call button and numerous configurable I/O ports. The Axis integration only discovers the camera, not the call button or configurable I/O ports.

What version of Home Assistant Core has the issue?

core-2024.1.1

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-dd31d69246976cf8960c24b1476766d0.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Nothing really in the logs.

Additional information

1. Axis Device Firmware version: 1.65.12
2. Using an admin account
3. Connecting to device via http

[home-assistant]

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

Code owner commands

Code owners of axis can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign axis Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

axis documentation
axis source
_{^{(message by IssueLinks)}}

[jcbrooks75]

[Kane610]

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

[jcbrooks75]

Thanks, no firewall, but it's in bridge mode. This would block any ports advertised in (presumably) the SETUP command. I assume I can't configure a port range for RTSP? This would allow me to leave it in bridge mode. I'll reconfigure to use host networking and see if it resolves the problem.

[Kane610]

Thanks, no firewall, but it's in bridge mode. This would block any ports advertised in (presumably) the SETUP command. I assume I can't configure a port range for RTSP? This would allow me to leave it in bridge mode. I'll reconfigure to use host networking and see if it resolves the problem.

I had a separate request for this just today but I don't support it right now.i guess adding a port range wouldn't be that much work.

[jcbrooks75]

Cool! I think from an engineering/security perspective integrations should document inbound ports as well as allow for the configuration via environment variables. I think this is more consistent with the 12 factor app. What do you think?

[Kane610]

I agree it might be a good thing to improve, I won't promise when I will get to it though

[jcbrooks75]

FWIW, I tried switching out to host networking today. It didn't work. Host networking is not supported in docker swarm. You simply can't run HA in swarm because of these unpublished ports. I can add a feature request in if you'd like, let me know.

Host networking in case you're interested.
https://docs.docker.com/compose/compose-file/compose-file-v3/#network_mode

[jcbrooks75]

Well, I went back into the web app just now and I can see the peripherals now. I'm not sure why this is working. I'll look at the networking on the container to figure out what is going on.

[jcbrooks75]

Here's what's happening:

1. network_mode is not supported in docker swarm per https://docs.docker.com/compose/compose-file/compose-file-v3/#network_mode
2. by setting the network name to host you can run in host mode. It's not clear if this is officially supported. It's also an anti-pattern in the world of devops. Here is the compose file I used:

`version: "3.7"

services:
ha:
image: 'homeassistant/home-assistant:2024.1.1'
volumes:
- config:/config
- /etc/localtime:/etc/localtime:ro
networks:
- outside
deploy:
placement:
constraints:
- "node.hostname==compute1"
logging:
driver: "fluentd"
volumes:
config:

networks:
outside:
external: true
name: "host"`

[Kane610]

Closing this as its run in a way not recommended by home assistant. I might still solve it in a while.