Question on ZHA checkin events

SandmanXX · July 24, 2022, 6:23pm

I am suddenly getting a LOT of checkin events fired through ZHA. Below is an example. How can I turn these off, and should I?
Thanks.

sebbe1985 · August 29, 2022, 6:19pm

Wondering the same thing

Frankge · September 19, 2022, 2:47pm

Im getting the same with a single device

timelf123 · December 20, 2022, 8:41pm

I’m getting the same spam with a multisensor - zhaquirks.samjin.multi2.SmartthingsMultiPurposeSensor2019

SandmanXX · January 2, 2023, 11:52pm

I haven’t seen anything I could do to turn these log entries off? Or at least hide them?

teskanoo · February 4, 2023, 9:10pm

There are several of us wondering the same

github.com/home-assistant/core

Unable to (find a way to) Exclude ZHA Events from Logbook

opened 09:52PM - 26 Dec 22 UTC

teskanoo

integration: logbook integration: zha feature-request

### The problem Since I switched from Deconz to ZHA, my logbook is overrun with… entries created by the ZHA Integration I have found no way to prevent these entries from appearing in the logbook (which makes the logbook very difficult to read) ![image](https://user-images.githubusercontent.com/65863752/209585076-5ec950a0-98c0-4900-826f-180e873d6315.png) Having over 100 Zigbee devices this results in the Logbook consisting of about 70-75% ZHA Events with the remaining 25-30% being those events in which I have expressed an interest in being reported I have attempted to exclude ZHA events in the logbook configuration by domain ``` logbook: exclude: domains: - zha ``` I have attempted to exclude ZHA events in the logbook via recorder configuration where I can exclude event_types ``` recorder: exclude: event_types: - zha_event - zha.zha_event ``` Recorder config, IMO, should be the solution to remove these logbook entries - I can only imagine that I am targeting the wrong event_types, however this is how they appear in my (MariaDB) Database I have attempted to prevent the logging in logbook by reducing the logging level for the integration (in the vain hope that this might be a factor) ``` logger: default: info logs: homeassistant.components.zha: critical ``` I have verified that this issue occurs regardless of the Enable/Disable debug logging setting for the integration ![image](https://user-images.githubusercontent.com/65863752/209584437-6f7e4c9b-43eb-41ca-9891-cc2470f92f0a.png) I have attempted to identify in the codebase if and where any recorder and logbook exclusions are taken into consideration when the deciding to log into the logbook ### What version of Home Assistant Core has the issue? 2022.12.8 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue ZHA, Logbook ### Link to integration documentation on our website https://www.home-assistant.io/integrations/zha/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml Snippets from recorder and logbook configurations that I have tried to exclude these events from the logbook recorder: exclude: event_types: - zha_event - zha.zha_event logbook: exclude: domains: - zha ``` ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information Forum post concerning this matter (which has been present since August 2021 but has not, as far as I can see, been raised as an issue) https://community.home-assistant.io/t/exclude-zha-events-from-logbook/452501/13

PhilippeP · June 2, 2023, 5:58pm

I found an answer there : ZHA - Checkin Event was fired ever feww seconds · Issue #85342 · home-assistant/core · GitHub

SandmanXX · June 17, 2023, 11:23pm

Sorry Phillip, that doesn’t help me at this time.
I’m still getting the events, about every minute or so. When I try following the directions of pull attrib, when I click the read attribute, it runs for a few secs, then gives me a red stopsign-looking icon for a couple seconds, and never fills in the value.
I have a HUB-z controller plugged into my Odroid N2+.

SandmanXX · July 22, 2023, 6:50am

This is still happening. It started maybe within a month or so of me posting, one of the updates. If I look in the logbook for any of the device/entities, it doesn’t show any checkin event/attribute event, anything, so apparently it is not an entity. Anyone still looking into this?

mrcriter · July 25, 2023, 1:52am

Please help! My logbook is full of these. It’s nearly impossible to find certain logs because of all of these events firing.

Podds · November 5, 2023, 3:52pm

If you still have an issue: Re-configuring the entity with reporting issues fixed the issue for me. I can see you have multiple entities, but I think you could try it anyways. Could be that an update of ZHA caused this…

SandmanXX · February 13, 2024, 4:54am

I think so. I’m having more ZHA problems now, at least with a battery card, but the issue is still here, as I posted the pic above.

janrothkegel · July 11, 2024, 2:15pm

My heater valve does the same thing. However, I don’t care about the logbook. My problem is that the LED lights turn on every time this happens… Any way to fix the root cause on the device? (I know this rather a Zigbee problem than HA but I am interested anyway.)

michaelh · February 5, 2025, 9:49pm

Still no input from devs? I’m seeing the same thing and would love to know why and what I should do about it

HA-Userr · August 5, 2025, 9:26pm

Hi! I have recently encountered the same problem. I have 6 leak sensors, which are identified as Sonoff SNZB-03. They all work properly, react to leak events. But about every hour I see the event “Checking event was fired” on three of them. The signal level is sufficient and the power supply is stable. But for some inexplicable reason I can’t get rid of these events.

I have already tried:

Changing the interval PollControl >> checkin_interval. but I can’t read the attribute value or change it, getting an error.
I tried resetting the sensors and setting them up again by deleting them from Home Assistant, sending them the attribute “reset_fact_default”. But it didn’t work.
I checked the power supply of the sensors, put them in close proximity to the ZigBee Home Assistant transmitter and powered them from a lab power supply with 3v. The events continued to bother me.

Any ideas on how to fix this?

olddawgpowers · August 7, 2025, 10:13pm

I am having a similar issue with Sonoff SNZB-05P Leak Sensor. The SNZB-03 I believe, is a motion sensor. The first time it took for several minutes to complete the configuration. The second time I re-paired it I, i paired it to a local repeater and not the hub. Once it showed Configuring I would briefly tap the Reset/Pair button to keep it alive until it completed configuring. It is no longer doing the CheckIn but I did get a couple of Warnings today in Homeassistant.log about checkin but it didn’t identify the device. I like the build on these sensors and hope the problems can be sorted out.

HA-Userr · November 5, 2025, 10:49am

If I understand correctly, these warnings are caused by the availability check interval being too short for battery-powered devices. Devices should periodically (I’m not sure how often) send an “alive” packet to notify the server that they are still online, their batteries haven’t died, and the network hasn’t been lost. For battery-powered devices, this interval is very long. For example, I noticed that my leak detectors contact the server about once a day. Try increasing the availability check interval to 24 or 48 hours.

For me, this solved the problem with the leakage sensors, as well as with several temperature sensors.