Great! I will look into this.
The discovery method is supposed to work around this issue but apparently not in all cases…
What version of VMD is supported? 3? 4? 4 is a significant improvement on 3.
I’m gonna upgrade the component during the coming weeks. Then vmd4 support will be added
Hey @Robban
Will it be possible to choose between vmd3 and vmd4? I am asking because I am using the Axis Companion App and this one still works with vmd3 and as far as I know, using 3 and 4 together does not really work. No idea why axis still could not implement vmd4 support on their own software.
That looks awesome 
Can’t wait to try it out
Its more than halfway there. It will take a couple of more weeks to finish due to a busy schedule and it being quite complex. I don’t expect it to be in before 0.84
Any updates on a new release for the component? Maybe I could help. I just got 2 Axis cameras that I can use Motion Detection 4 with so I am hoping to get this up and running soon.
Config entry options are done so I’m back on working on axis component
I know how things are structured you shouldn’t have to write a specific driver for Axis gear. You write support for their features and then ask the device which ones they support and it will let you know. Then, you can enable whatever it supports. If that makes any sense.
I can get my hands on pretty much any Axis product so if you need testing, let me know.
1 Like
Thanks! I appreciate that. The issue has mainly been with design with a long term approach in mind, requests for doing backend changes for hass ( config entry options and areas), making improvementsin other components and having some well deserved breaks from home automation. The Axis component my first component and still very important to me with a lot of plans to incorporate th different product types in the long term.
@Robban - Sent you a PM as well, but as I have searched and not found I take it here as well:
I want to use the I/O ports and use VAPIX. I know my way around, and can read the documentation for VAPIX on www.axis.com, but how do i use the service? How do I declare it when using axis.vapix_call?
Any enlightenment is greatly appreciated!
/R
The service will be removed with next release of hass. There where too many issues with it. I rather see suggestions of generic support of the different parts of axis devices and do a proper implementation with HASS that will benefit everyone
Can you clarify what you mean by this? Are you planning on using the new generic camera framework in HA?
There are a lot of features that could get a better integration than trying to use the service. So suggestions on what
If you are asking what integration we would like to see…
I would like any analytic as a trigger. VMD3/4, Guard Suite, Perimeter Defender. Any third party analytics if you can write a generic integration. Being able to hit a virtual input would also be nice.
If you can find the metadata for guard suite or perimeter defender I can add them
It looks similar to these xml schemas listed here https://github.com/Kane610/axis/blob/master/tests/event_fixtures.py
If someone would like to help out I’ve been looking a bit into supporting Axis cameras with the new stream platform but couldn’t get it to work. If someone would like to play around to try to find a configuration to work with it that would be awesome.
1 Like
I am a little confused by the release notes for .91 with the Axis component. The notes only talk about what is not working but not really what the changes are and why we need to remove the Axis part from configuration. How can I help with the new camera stream? Should I try to get a generic camera working now and share my config?
1 Like
Regarding camera stream; if you could try configurations and settings and debug the transport to identify what would work with the camera stream that would be awesome. This is nothing requiring a development environment so I hoped I could crowd source solving this issue and I can focus on improving the backend instead.
Breaking changes; the only real breaking change is the axis service and support for some types of sensors disappear (IO ports and tampering); IO is because they can be used as both a sensor as well as a controllable switch so I’d like to look more at them how to best support them with hass. So really there is nothing fundamentally breaking, but if you want to signal that some expected behaviours has changed that’s the only clean way to document it with the release.