Something is polling my Zigbee outlet

I have a generic Zigbee outlet (aotec is the brand). In my logs, I can see that something is polling it every 5 minutes

dev:1642023-01-15 07:01:04.931infoXMas Plug 1 is off [physical]

dev:1642023-01-15 06:56:04.963infoXMas Plug 1 is off [physical]

dev:1642023-01-15 06:51:04.833infoXMas Plug 1 is off [physical]

dev:1642023-01-15 06:46:05.010infoXMas Plug 1 is off [physical]

How can I trace this to see why this polling is happening?

The XMas Plug is used by two simple automation rules (on at sunset and off at 10p)

I used to have a switch binding set up (using the custom Switch Bindings app), but have already uninstalled that app.

Thanks for any suggestions

1 Like

Can you see anything in the event tab of the device itself? It's a little odd that it reports as physical vs digital. Normally a physical change is one initiated outside of HE's control but I don't see how that could be the case with a zigbee device. I do believe that is driver dependent though so that may be a red herring.

1 Like

My guess it is in the driver. All my devices using the generic zigbee outlet or generic zigbee switch are polled every 5 minutes regardless of the brand.

1 Like

Zigbee devices arent polled, they just report on their own, though there isnt any reason its doing it every 5 minites...

2 Likes

Some devices are sending the on/off status periodically, like a keep-alive or heartbeat.

Here is an exemple of one device. I have 34 like that.

It does not bother me. It just fill the log with useless info.

1 Like

I appreciate the quick responses and insight. My take-away is the this polling isn't detrimental.

As a relatively new Hubitat user, what I was really hoping for what some insight into how I investigate an issue like this one. For example, in the log entries I see is there someway to figure out where this message is being generated? I don't know if it's the device, the rules engine, an application, etc

Is there a good debugging guide somewhere?

1 Like

Some of my Zigbee outlets and also Zigbee contact sensors will just randomly report their current status. They are not being polled it is just the way the device is sometimes.

2 Likes

If it does not load your hub then I would not worry about it.

1 Like

I do hate not being able to have any logging turned on for my eWeLink plugs. 12-15 reports per hour from each of eight plugs is too much to look at. :grinning:

our driver sets the maximum reporting interval to a very very high value over 65,000 seconds, so if the device is reporting more often than that, then it is ignoring the reporting configuration being sent to it, which is not cool...

I really don't think it's the driver. I have another aotec outlet that doesn't exhibit the same behavior.

I checked the config of both outlets. The only difference is that the one that is polling every 5 minutes has a State Variable called "bin" that is set to -1. One the quiet device the bin is 1

State Variables

  • bin : -1
  • flashing : false

Does anyone know what "bin" is for? Or how to change it?

And any ideas how can I figure out where these logging messages are coming from?

you can click on the dev:### to be directed to the app that is running the polling

Bin is used to track physical vs digital so nothing to concern yourself with

I already said that the device is generating them on its own, see previous posts from me in this regard.

As an aside if you have to poll a zigbee device to get its state then the device or your mesh is crap...

1 Like

mike.maxwell - I saw your note, but since the two devices are reporting differently I was working with the theory that something else in the system is causing the difference in behavior.

It seems like it's not the driver, otherwise both would behave the same (I think?)

dadarkgtprince - when I click on the dev:### is just get a log that is filtered for that device. It doesn't link me to an app. Do I need to change something in my Hubitat set-up to activate the link you are talking about?

Is it possible you had a different driver, like a community driver, at one point?

Did you try changing this to the "Device" driver, (save device) and clearing all scheduled tasks? Then switch back to the correct driver (save device again) and see what happens?

You went through all "in use by" at the bottom of this device's settings page, and there isn't an app you forgot about using this outlet?

3 Likes

And click configure

1 Like

The "physical" between brakets in the log tells you it originate from the device itself. As Mike stated, these seems to ignore the reporting interval set by the driver so they will send their heartbeat at their own rate regardless of any app or driver setting. (In my case every 239 seconds exactly)

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.