Closed pimw1 closed 2 years ago
logbook documentation logbook source (message by IssueLinks)
Hey there @home-assistant/core, @bdraco, mind taking a look at this issue as it has been labeled with an integration (logbook
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
deconz documentation deconz source (message by IssueLinks)
Hey there @kane610, mind taking a look at this issue as it has been labeled with an integration (deconz
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
It's likely the event is missing the device_id so it can't be linked to the device. Can you find the row in the events table that is missing?
Sure, here is the row:
Sure, here is the row:
Can you post the row with data_id 504 from the event_data table as well?
Sure, it returns 13 rows:
The content of the event is in another table called event_data. The data_id in the events table links to the row in the event_data table that has the actual event data for that event.
In your case it looks like the same event data happened 13 times so we only store the contents of the event data once.
We need to look at the contents of that data to see if the device_id is missing or there is some other reason we can't automatically find it in the database
It shows the following in event_data for data_id 504:
So we have the device_id, thats good.
Can you post the full url path (without the hostname) from this image?
The url is as follows: http://192.168.178.2:8123/config/devices/device/dc95c6af56c3b3643c4872c42d29371e
This is the same device_id as retrieved from the event_data table for data_id 504 (dc95c6af56c3b3643c4872c42d29371e)
That all looks good.
I'm not sure why its not displaying. I'll try to add some tests for deconz events late this week and see if I can find the problem
Great, thank you for helping out.
If it helps, we can share screens and have a conference call in Discord as well.
If it helps, we can share screens and have a conference call in Discord as well.
If I can't find it with the tests, I may take you up on that. I'm traveling this week so I won't have a stable enough connection until this weekend.
As soon as https://github.com/home-assistant/core/pull/73918 merges I can look at this one.
https://github.com/home-assistant/core/pull/73918 will fix the historical ones assuming you are using MySQL or PostgreSQL
No luck replicating this one in testing so I ordered one of those buttons for testing Delivery by parcel to Houston, TX 77007 Estimated Delivery Date June 28, 2022 09:00 AM - 05:00 PM
Haha nice! Good to know is that i see this behaviour for Philips Hue switches too. My best guess is that this happens for any stateless zigbee switch in Deconz.
Do you see it with a Hue Remote ?
Yes indeed :)
I see one exception: events for zigbee buttons (Hue, Ikea, etc.), such as the Tradfri shortcut button (Zigbee),
Ok good. My hue remote works fine so I think this is deconz only.
Yeah it has to be. You're using another solution than Deconz?
I did testing with the hue bridge and zha
Good news. The button came in and it shows up in the live logbook but not the device page so I have a place to start debugging
Found the bug. If we exclude all entities because they have a UOM we don't check for devices as well
Great that you found the root cause! Thank you very much for helping out.
The problem
Hi,
For most of my devices, the new live logbook are displaying everything that i expect. I see one exception: events for zigbee buttons (Hue, Ikea, etc.), such as the Tradfri shortcut button (Zigbee), connected via Conbee II + Deconz.
The event is showing in the traditional logbook.
Zigbee sensors are displaying state changes as expected (so the issue seems limited to events from zigbee devices that are stateless?).
What version of Home Assistant Core has the issue?
core-2022.6.6
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
logbook
Link to integration documentation on our website
https://www.home-assistant.io/integrations/logbook/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
It seems not related to https://github.com/home-assistant/core/pull/73419 , since the issue is persistent and not solved by a restart of Home Assistant.