I have few Zigbee devices that goes to offline after random periods of time. I have two plug-in switches and four Aquara temp sensors. I am aware there are issues with Aquara but the issue is with the plugin switches. After a while it will show offline in PaperUI but can actually turn them on and off through the app just fine.
Using Openhab 2.5.6
Device: HUSBZB-1 (Boost Mode, High Power)
Openhab-cli shows the devices are still online even though PaperUI/HABmin shows them offline.
Note tat the State shown in the console is not linked at all to the state of the Thing. This state comes from the lower level zigbee libraries and is not used in the binding.
The binding will use reports from the device to decide if a device is online or not. If it doesn’t receive a report when it expects, then it will mark it offline. This assumes that a device respects the reporting that the binding configures (which it should as it’s part of the standard) and some cheaper devices (eg Xiaomi) will ignore this. The lights I see in your device list should be fine, but if the RF link is not perfect, it could miss some reports.
Log files may help understand what is happening.
Distance isn’t everything. It depends on many other factors - antennas, antenna alignment, walls, radios, TVs and other devices nearly, any metal in the area, etc, etc. Distance is a good first approximation, but there can be a lot more to establishing if the RF link will work.
Thanks for explaning this. I didn’t know and just wanted to give some informations which might help.
Before grabbing the logs or generate some meaning full let me emphasize on the essential observation:
THINGS are marked offline i pUI
every ITEM is working as disired (afaik)
I never saw this before openhab 2.5.6
The attached logfile is default loglevel and starts right after the update to 2.5.6-2. there are errors an warning at the beginning, i normally ignore until i did the 2cnd or 3rd restart of openhab. This seems to be a known problem while starting after cache cleared: ITEMS not loaded when RULE already starts - you may know about that.
If this log does not show the information required, please let know, which actions to take. I’ll set the loglevel to debug as described for the binding and take the actions then.
I have had this issue for years.
I have two Zigbee dongles, and they both behave the same. Devices simply stop responding randomly and switch to offline. Only chances of getting them back is to remove the thing and include them again.
The distance is very close, aprox 1-5 meters.
I wonder if this will ever gona be stable. After my last try, it took a few weeks, and now the only device online is, funny enough, a xiaomi mija motion sensor.
That’s interesting. I thought it was a dongle issue. Other than the Aquara temp sensors which gives no response, found out that they work just fine connecting to the dongle directly and not part of a hop. The switches still work and responsive but shows offline…
I appreciate you have had continued issues, and I don’t know why - I’m sorry I’ve not been able to help. This binding and libraries are used commercially by a number of companies - most of which I can’t mention, but I think it’s clear that Qivicon / DT are using this since they were helping with the development for quite some time. It’s just a shame that we’ve never got your system working, but thousands of other systems out there work very well.
So this all looks “ok” to me. By this, I mean it is working as it is designed - there are no reports during this period (30 minutes) so the device is set to OFFLINE. This is how it is meant to work.
The question is why there is no reporting. A device should be configured to report every 15 minute in theory. This log does show the startup of the binding so I can confirm that this is what is happening (see below), and the binding sets the device OFFLINE if it doesn’t send 2 reports, so this all looks correct.
What i changed lately was the setup of the telegesis (19200 to 56700), while investigating these problems. This has been at about the same time i updated openhab and realized what we are writing about here.
My openhab needs some maintenance, some sort of backup/restore and i just received an ups for my rpi. When i implemented these topics, i’ll give an other zigbee controler a chance i think.
I know you have tried Chris… And I know others out there are using Zigbee without any hassle. That just makes this (my problem) much more strange. Remember, I have been trying for a coupple of years now, with several different openhab setups and two different Zigbee coordinators. The only thing I can think of is some external devices which is messing things up. I have no idea how this should be possible, but I really doubt its a openhab core/dongle issue anymore. For the last year, my Odroid C2 has been used to test Zigbee only, except for running Velbus server. Thats all there is install on that openhab setup.
As for external devices, I´ve got two. One is my Philips Hue brigde and then a Xiaomi hub (v2). They both communicate “almost” the same 2.4ghz , but they havnt got any issue at all.
One of the latest Zigbee binding and lib released wouldnt even connect to my Philps Hue devices. They usually were the devices which only gave problems in the long run. A big surpise was, that I was able to add a Xiaomi motion sensor. This has always failed. But now its the only device running after weeks, and its still running. The rest eventually stopped responding, and after a while went offline, just as they used to, (beside the Hue devices wouldnt even connect).
I really have no idea whats going on… But I have to be honest with you, I doubt I´m the only one with this issue. As you can tell from this thread, there are a few more out there with the same experience… Maybe I have just been more patient than others, how may have given up insted.
I’m late to this party, so you may have already tried this: I’m using a USB CC2531 dongle on a Raspberry Pi 3B+. I’m using zigbee2mqtt rather than the Zigbee binding. I’d find that my device (yeah, I’ve only got one!) would go offline randomly, and the thing that seems to have fixed it is putting the dongle on a USB extender, and then plugging that extender into the Pi - i.e. moving the dongle away from the Pi.