Vmd4 is supported by the updated component 
The SWEEEEET thing from a HASS persprctive IS the I/O though. Especially when using a wifi camera. I have one hooked up in my garage, using a reed switch connected to the Axis input to determine if the garage door actually IS closed.
It will be back, I just want to evaluate how it works together with outputs
1 Like
I have 22 Axis cameras. 4 212PTZ and 18 using 3 Axis #7406 blades.
I had these working in 87.1. but going to 90.2 lost them.
Will upgrade to 91 this weekend and would love to get them back up in HA.
I have saved the axis.conf file and still have
axis: ← see that with 91 I need to remove this from configuration.yaml but them what?
in configuration.yaml. But nothing shows up.
Would really like some direction how to get new axis config requirements correct to get going again.
My axis.conf look like this for each camera:
"mac_address": {
"host": "IP_address",
"include": [ "camera" ],
"location": "",
"name": "camera_name",
"password": "password","port": port_number,
"trigger_time": 0,
"username": "username"
},
Hmm. There shouldn’t be any behavioral changes in regards to operational state. Mainly on adding devices.If you’re doing it from scratch. Go to integrations pane and add them through the Axis device item.
If you see issues. Please share logs. Even better if you could create a hass github issue with all information
Thanks for the quick reply.
With 90.2 axis is not listed in the integrations pane any more. At least not in mine.
Again, I do have axis: in configuration.yaml hoping that would trigger it.
No it is added with 91.
For debugging add this to your configuration.yaml
logger:
default: info
logs:
axis: debug
homeassistant.components.axis: debugOK. Got it. Will upgrade on my return from work today. Thanks for all your work on this.
I have 2 different cameras one with firmware 6.50 and the other is 5.60 and I just upgraded to .91.
Both of the cameras work with the following configuration as generic cameras:
- platform: generic
name: driveway_gen
username: root
password: !secret camera_password
still_image_url: http://192.168.1.41/axis-cgi/jpg/image.cgi
stream_source: rtsp://192.168.1.41/axis-media/media.amp
verify_ssl: false
authentication: digest
Without digest authentication only the 5.60 camera worked.
In the previous version of the axis component it was possible to select the features you wanted to enable in configuration.yaml.
I cannot find anywhere to do that in 0.91.2
The result is that my ui is cluttered with a lot of VMD-sensors that I am not interested in. The logbook is also cluttered with lots of VMD events. I am not using Homeassistant to monitor and manage movements and recordings.
Is it possible to disable the creation of unwanted sensors?
Not at this moment. The problem was that it was a lot of complicated pieces and logic fit together to handle all of that and I wanted to back up a bit to clean it up and rework the backend.
I am planning on adding it back later on.
Well… If you mean you only want video? Then yes you can manually edit the config entry file to disable those
OK, keep up the excellent work!
1 Like
Yes, I am happy with video only for the time being. How do I disable the rest?
Go into your home assistant folder open the .storage/core.config_entries file and just change the events = True to false per device config entry
1 Like
I am having a problem with one of my cameras. It is a 6.50 firmware with VMD4 which works. But after about 12 hours it stops working. If I click the test button in the VMD4 configuration window HA never receives the signal even if I am still streaming video. I added debug to the log and i get these rtsp session errors once every minute.
2019-04-12 10:21:11 DEBUG (MainThread) [axis.rtsp] Received data ['RTSP/1.0 454 Session Not Found', 'CSeq: 4', 'Server: GStreamer RTSP server', 'Date: Fri, 12 Apr 2019 08:21:13 GMT', '']
2019-04-12 10:21:11 DEBUG (MainThread) [axis.rtsp] 192.168.1.41 RTSP 454 Session
2019-04-12 10:21:11 DEBUG (MainThread) [axis.rtsp] RTSP session state playing
2019-04-12 10:21:11 DEBUG (MainThread) [axis.rtsp] RTSP session state playing
2019-04-12 10:21:32 DEBUG (MainThread) [axis.rtsp] OPTIONS rtsp://192.168.1.42/axis-media/media.amp?video=0&audio=0&event=on RTSP/1.0
CSeq: 4
User-Agent: HASS Axis
Session: {REDACTED}
Rebooting the camera will force HA to reconnect and get a new session. Is there is something that is a HA problem?
Do you see any point in time where that message first appears if the keep-alive message is sent with over a minutes interval?
You can try to increase the RTSP timeout to 120 seconds perhaps?
root.Network.RTSP.Timeout=60
I added that to the camera but it didn’t help. Here is a part of the log where it loses the session. https://pastebin.com/UiZjxVaB Be aware I have 2 cameras and the other one is also in the log. It is hard to see which log line is from which camera but the one with problems has the ip ending in .41 and the session it uses is t5kAaPsS42YcKJMo
I ran some more tests, I think the issue is that the raspi becomes overloaded and bogs down for a few minutes missing the rtsp timeout call. Here you can see just one camera. https://pastebin.com/UiZjxVaB There were some lines from other components that timed out that I removed between 09:42:46 and 09:43:23 but I think my pi hung up pretty bad there for about a minute.
If I set a longer time on the camera it would keep the session from going away correct? But then how can I get the axis HA component to make the call to Options to keep the session alive more frequently? If timeout is 2 min on the camera, can the HA component call that at 1 min to try to keep it alive.
But this doesn’t answer the bigger question on why it doesn’t try to re-authenticate when it gets the 454 error? And why does it only effect this one camera and not the other one?