-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Critical events in log #79
Comments
@AnetworkIT which hub do you have? There is no support for UA-G2-Pro. It may still work but if it's got quirks they're unknown/unhandled by the integration. Is everything working as expected other than the warning? |
Thanks @imhotep, just using the standard UA-HUB. We don't use the doorbell features with HA, but everything else seems to work just fine. |
I also see these events for the G2-Pro connected to the UGT. For the time being they probably just need to be suppressed. |
Just to clarify, the UA-G2-Pro isn't a hub, it's the video doorbell / keypad, and is plugged into the hub. I suspect it shouldn't even be getting past the hub into the websocket updates, but it definitely is (even when nothing happens on the UA-G2-Pro itself). I wouldn't be shocked if the same thing happens with the other devices like the UA-G2. |
@slyglif I have UA-G2-Pro keypad and a UA-Pro hooked up to 2 different UAHs and none of them are appearing in the websocket messages. So perhaps a bug in the API? Are you seeing that yourself with your hub? |
I am seeing it. I just checked the last 2 messages, hoping that there would be something different in them to indicate something is changing, but they are identical (which seems odd, because even the "event_object_id" is identical). Maybe it's related to the firmware version on either the hub or the reader. My G2-Pro has firmware 1.6.28. |
@imhotep I'm having the same issue as described here. On 2024.11 and 2024.12 HA releases. Here is an example of the full log event, partially sanitised:
|
@imhotep Thank you for all your work. For me the integration is working, but I had to add the integration files manually to the HACS folders - the custom HACS repository somehow didn't get picked up. I have these "CRITICAL" events in the log as well. Very much like maxw3l. Are these Unifi Access events? I think these JSON chunks are logged in sequence as I was testing my UA Pro and UA Reader Lite connected to my UA Hub. Did perhaps the JSON format change and they get logged to attract attention? Speaking of attention... Unifi JSON events are huge and seem to contain a lot of stuff. More like memory dumps rather than events. Maybe it's just me. On the plus side you always get the full state in each JSON message. Sorry to hear about your UA-Pro screen deterioraition. Looking at the device it feels like it shouldn't be used outside. I wonder how long mine will last. |
In the HA log, I’m getting 1000’s of “UniFi access Hub type UA-G2-Pro unknown” followed up by {event.data.device.update……….} the logs are marked as (Critical)
everything seems to be working just fine.
I’ve only noticed this on the latest version of the integration. 1.2.4
Core
2024.9.2
Supervisor
2024.09.1
Running UniFi access 2.3.20
G2 Pro - 1.6.28
This error originated from a custom integration.
Logger: custom_components.unifi_access.hub
Source: custom_components/unifi_access/hub.py:437
integration: Unifi Access
First occurred: 26 September 2024 at 22:58:33 (396 occurrences)
Last logged: 08:58:33
UniFi Access Hub type UA-G2-PRO unknown
The text was updated successfully, but these errors were encountered: