Zigbee Radio Offline

🛎️ Get Help Devices
1

Today I was noticed that many of my devices were not responding. Then I got a notification via a Rule I have that my Zigbee radio went offline. A quick search of the logs showed this

Capture
Capture1630×498 132 KB

Device 2 seems to be implicated. It's my Office Desk Light, a very simple on/off lamp controlled by a Generic Zigbee Outlet (actually an Innr SP 222-2). I have several of these, all of which have been operating just fine for months.

A reboot of the HE brought the Zigbee radio back online, and everything seems to be back to normal (inclduing the Office Desk Light), but I'm a bit concerned as to what my cause this.

Any ideas what could be the cause, or where I could start looking?

2

those logs indicate that a job was scheduled (checkPresence) with a non hubitat driver, then the driver was changed to a hubitat driver which doesn't have a checkPresence method.
You can remove this scheduled job by temporarily replacing the current driver with the "Device" driver and clicking the deleteAllScheduledJobs command

3 Likes
3

Thanks Mike, I’ll look into that.

However, why would this happen? This switch was pretty much the first thing I set up when I got my HE in November 2021 and i haven’t touched it since

4

There's only one reason this happens - if the driver for a device was changed. And I've never experienced a driver changing by itself.

5 Likes
5

I agree that doesn’t make sense. But I haven't changed it, and certainly not today as i was out all morning

6

I'm confused, the driver change caused the zigbee radio to go offline or was the cause of the logged errors or both ?

7

I have no idea what happened

I was out all morning but received a notification via a rule i have that zigbee had gone offline. When i got back home later i searched in the logs for zigbee and came up with the info shown in the screenshot in my first post.

A reboot fixed the issue and all now appears to be fine. I've removed the scheduled jobs as suggested by Mike above, and then put the driver back as "Generic Zigbee switch"

As I said, I am certain I did not change the driver - this was my first device in HE, the driver was chosen automatically when I added the device, and I've never touched it since in 7/8 months

Fingers crossed that's the last of it, but I still have no idea what happened

1 Like
8

Can you post a screen shot of the Drivers Code page located under developer tools?

1 Like
9

Capture
Capture1397×721 87.6 KB

Capture
Capture1418×803 99.8 KB

Capture
Capture1436×845 92.6 KB

10

right, so one of those (no idea which one) is a match for the zigbee outlet that we are talking about, when this is the case the system will choose the user driver over the system driver when the device is joined...

Bottom line is the only way that job could have been scheduled was via a user driver since none of the inbuilt drivers use or have ever used or implemented a method named checkPresence.

1 Like
11

Thanks Mike...I'll see if I can find out which one..

1 Like
12

It is one of the zigbee plug drivers (Salus or TuYA).

2 Likes
13

I do have a couple of Salus SP600 smart plugs, but neither of them are in use at the moment (by which I mean they are in a cardboard box in my office, not plugged into power, and not utilised by any rules). The devices themselves are no longer defined to HE, so the drivers are not used. Anyway, just to be on the safe side, I have deleted the drivers from HE

The only Tuya device I have is a Smart Knob using the Tuya Scene Switch TS004F driver. This is defined to HE, but not used at the moment, so again to be on the safe side I have deleted the device and the associated driver.

2 Likes