Closed jonoberheide closed 5 months ago
Thanks for reporting, would you mind enable debug for the library and share the raw data being parsed?
The way to mitigate the issue depends on what the raw data shows :)
Here's the log file: log.txt
I'm able to skip that EventBuffer/Begin topic by tweaking some logic in decode()/decode_from_list() and then the event stream appears to start. However, I don't seem to get receive relay events from the A9188...which may be an independent issue.
What access rights does the user have? For port control it needs to be admin, not sure if that affects the event stream itself though
Yep, it's the admin user.
Here's the log file: log.txt
I'm able to skip that EventBuffer/Begin topic by tweaking some logic in decode()/decode_from_list() and then the event stream appears to start. However, I don't seem to get receive relay events from the A9188...which may be an independent issue.
Main file does a few things extra and it seems to be broken, ignore the await device.vapix.initialize_event_instances()
in the main.py and it should proceed
Strangely, I can see the events coming from the device using the gstreamer rstpsrc client, but not the axis one. I'm not quite sure yet where the protocol sequence is differing though...
Strangely, I can see the events coming from the device using the gstreamer rstpsrc client, but not the axis one. I'm not quite sure yet where the protocol sequence is differing though...
I did skip out and didn't implement the rtcp channel which has worked great for a long time and I think I even tried it on a 9188 once.
I appreciate you are looking at it!
Here's the log file: log.txt
I'm able to skip that EventBuffer/Begin topic by tweaking some logic in decode()/decode_from_list() and then the event stream appears to start. However, I don't seem to get receive relay events from the A9188...which may be an independent issue.
Sorry didn't get to this until now, would you mind share the debug log output when you get that event over the rtsp stream
I ended up going a different route for my use case, so I no longer need to consume the events from the A9188, so I'm ok to close this if it makes sense for you.
Also, maybe a separate issue (but again, no longer relevant), when I just tried re-adding my A9188 to the latest version of HA, it successfully set up the device, but did not create any entities for it, which I'd swear there were relay/IO switch entities set up in a past version (as I referenced in https://github.com/home-assistant/core/issues/109345 )
I ended up going a different route for my use case, so I no longer need to consume the events from the A9188, so I'm ok to close this if it makes sense for you.
No-one else has reported that issue so I guess if you're not concerned with it we can close it, even though I would like to see complete debug logs so I could solve it proactively :)
Also, maybe a separate issue (but again, no longer relevant), when I just tried re-adding my A9188 to the latest version of HA, it successfully set up the device, but did not create any entities for it, which I'd swear there were relay/IO switch entities set up in a past version (as I referenced in home-assistant/core#109345 )
Yes please create a new issue and we can look at it
Ok, I suppose I will keep the issue open and we can revisit once I'm able to reproduce the issue.
I'll file a new issue...assuming the HA project is the right place for that as opposed to here.
I would say this is safe to close now, given that the RTSP event streaming is working A-OK for the 9188 through HA.
Allright! Thanks for the swift actions!
In trying to debug an Axis HA issue (https://github.com/home-assistant/core/issues/109345), I used this library to query the A9188 device in question.
I get an exception when processing the various event types:
It appears there is an event type returned that does not have a MessageInstance body:
I'm not sure if this event type should just be skipped, or if some different parsing logic is required.