Zigbee binding

fuu · June 21, 2019, 4:32pm

Is there a way to test and debug this without fiddling with an openhab setup - Running it from an IDE or something? I have a conbee 2 stick and a metering plug for testing here.

chris · June 21, 2019, 4:33pm

Sure - you can develop directly with the Z-Smart Systems libraries.

jfrank1845 · July 12, 2019, 2:54pm

Hi Chris - hope you have been well. I just wanted to pass two things by you .

I have noticed my devices(mains powered ones) will consistently ‘fall off’ and turn offline for a bit. Generally they will eventually come back to online without any intervention at some point but I can also hasten the process by disabling and re-enabling the thing. is there some sort of setting that I can enable that will help prevent this from happening? Everything works just fine while they show as online. I have only noticed this since moving to a new home and as such my network size did increase - I’ve got at least 30 or so devices now. I was thinking maybe there is some setting that I may need to adjust to work better with this network? I’ve attached a subset of logs that hopefully can help… I dont know that it includes one falling off to offline but I did include re-enabling the thing where it instantly comes back online. I also wasn’t sure if it was maybe just a java issue or something with the thread locking up.
Is there still any discussion about the binding and the ‘UNDEF’ logic between the ColorColor item and the CT item? I"ve attempted to use this as an ‘indicator’ of color/CT status but i’ve found it to not be reliable - I’ve been forced to use a manual independent switch to track it myself. I’ve also noticed that this UNDEF logic causes me to constantly lose status on if the light is online / brightness. I’ve linked a dimmer and a switch to the ColorColor item but when I initially send a CT and change its status these loose their info until I manually edit the switch or brightness. Once I do that I’m able to see the status as well as adjust the CT temp.

I do understand some of this may be improved in the latest libraries release - if you think that is the case let me know / let me know of a snapshot version you’ve been running that seems ok and I can give that a try. I’ve been with the understanding the latest snapshots have been a mess so I’ve stuck on the M release for now but I can change that. Thanks for all of your help!

openhab.log (581.3 KB)

chris · July 13, 2019, 9:27am

If it is systematic, then there are a few reasons I guess. Firstly, there could be issues in the network that are causing this, and if so, this is going to be hard to spot as all we will see in the logs is, well, nothing other than the timeout.

It could of course be a bug in the binding with the detection of the OFFLINE device. This uses a timer that expects to receive data from the device at least once in a certain period. This period is a little more than twice the minimum of the polling period, or the reporting period. If the device doesn’t report as it’s configured by the binding, then this could cause this.

Now we know that some devices (ie the Xiaomi devices) don’t respect the configuration, so it’s quite possible that this would happen in this case, but most devices that are really ZigBee should respect the configuration of reporting period.

The only way to be sure here is with a log. Unfortunately I’m not sure what the log you’ve provided is trying to show. I don’t see any nodes going offline, and the log is very short (just a few minutes) so we can’t build up a picture of what is happening from this.

Not that I’m aware of. Personally I don’t really like the way this is implemented, but this is what was agreed to provide the same functionality across bindings.

I don’t think the new libraries will change much in relation to these issues.

jfrank1845 · July 19, 2019, 1:24am

That is crazy - so no way to tell if a bulb is online or not when in CT mode. I can’t imagine why other bindings are that way as well. Is there any way I’m missing to get an on/off status that works 100% now? I’ve had a switch item linked with the color channel but it goes haywire once the color channel goes undef because of CT mode and I can’t link a switch item to a colortemperature channel.

I’d like to have something on my sitemap/habpanels that truly represents the state of the light.

jfrank1845 · July 19, 2019, 1:59am

Disregard the previous edit of this post - i was able to get things happy by flipping some bulbs on and off. seems they got into an odd state. I have linked to a folder of logs, however, that should include data on a bulb thing going offline and then coming back online. A number of them just came online right before I pulled the log - the things came online as a command was sent to the channels. Sorry the files are big- i had edited it down to 10 meg rollover but apparently an update reset that. I still wish I could find good advice on splitting out the zigbee /zsmart logs into their own file but still working on that. Thanks for all of your help!

Regards,
Jared

weakfl · July 26, 2019, 4:21pm

@chris is it possible to configure the polling interval of a channel through HABmin/PaperUI? If not, how can it be configured?

chris · July 27, 2019, 4:01pm

I want to say “yes”, but at the moment I can’t work out how to get this working under PaperUI. It may not be available for all channels, but for some channels at least there should be channel level configuration options available, and polling should be one of the settings (along with other reporting configuration).

This is available for the dimmer and switch channels at least (I just checked the source), but at the moment I can’t see where to configure this in PaperUI. I thought that it was an option in the channels list, but I’m not seeing that in my test system here (which I’m still struggling with given all the changes to the build environment).

HABmin should show this, but I’ve not got it configured in my dev system as I’m trying to run a simple system so we can work out what is wrong with the IDE. I’ll see if I can add HABmin into the IDE and hope the development environmentl doesn’t break

weakfl · July 27, 2019, 4:33pm

Thanks @chris! I noticed that my OH version (2.5M1) is probably too old. It looks like it was released before the relevant PR was merged. I’ll try to update to a recent snapshot. I was a bit hesitant to do so because of the recent stability issues…

The transition time setting isn’t available in PaperUI either, so maybe HABmin is required for polling as well?

chris · July 27, 2019, 4:35pm

Were other channel configuration options available? The binding attempts to work out what is supported by different devices, and will only provide configuration options if the appropriate configuration attribute is supported.

weakfl · July 27, 2019, 4:57pm

As mentioned, it seems like my OH version is too old to support other configuration options than “Default Transition Time”, but even that is only available in HABmin.
I only have things with “Dimmer” and “Switch” channels, but none of those channels show any configuration options in PaperUI.

weakfl · July 27, 2019, 5:10pm

I forgot about the bulbs, they have “Default Transition Time”, “On/Off Transition Time” and “On Level” configuration options in HABmin, none in PaperUI.

chris · July 27, 2019, 5:28pm

Thanks for the info - so it looks like PaperUI has lost its channel configuration options. I’m sure it was in the same place as the profile configuration is now when editing channels

Oh - and I do have your USB stick here - my Mrs put it in a safe place when it arrived and I only found it on Thursday. I’ll try and get that back in the post on Monday.

weakfl · July 27, 2019, 5:44pm

Thanks Chris, whenever you have time is fine.

I’ll report back about the polling configuration once I’ve updated OH to a recent snapshot.

weakfl · July 28, 2019, 9:15am

@chris I’ve updated to 2.5.0~S1645-1 and the reporting/polling configuration options are now available in HABmin (still nothing in PaperUI).

I’ve set “Polling Period” to 15 seconds and it’s working as expected. Out of curiosity I’ve also tried to set the “Maximum Reporting Period” to 15 seconds, but that didn’t work. That was expected though, the relay channel(s) never honoured the reporting configuration (that’s why I wanted to configure polling in the first place).

So thanks a lot, finally the UI gets updated in a timely manner when the wall-mounted switches are used to change state

AFromD · July 28, 2019, 10:22am

I think that I am doing the same thing that weakfl is doing in habmin by adding

, zigbee_reporting_polling="15"]

to my thing in the .things file, correct? Or is zigbee_reporting_polling something else than "polling period"in habmin?

chris · July 28, 2019, 10:35am

To be honest, I’m not 100% sure, but I don’t think it is correct.

This configuration is on the CHANNEL, not the THING, so my guess is that it will not work if this is added to the thing, but I’m not sure where to set channel configuration so I could be wrong.

Kim_Andersen · July 28, 2019, 11:19am

Hi @chris
Just a curious question.
I have just installed an fresh openhab 2.5M1 on an Odroid C2. My old setup was running an Rpi with the Elabs Zigbee hat for Rpi, also using the Zigbee binding 2.5M1.

With the Odroid C2, I use the EM357 Long Range USB dongle I had for sniffing, cause the Elabs cant go into the GPIO because there is an battery extension sitting there.

Anyway - I have noticed a huge difference in the two zigbee coordinators, which I dont quite understand.
When adding the Philips Hue motion sensor to the Elabs coordinator, it only frequently reports the lumiance state (several minutes interval). But now, using the EM357 coordinator on the Odroid, it reports the lumiance state alot more, like this:

2019-07-28 12:51:23.713 [vent.ItemStateChangedEvent] - HUE_illumiance changed from 246.33 to 246.43
2019-07-28 12:51:28.722 [vent.ItemStateChangedEvent] - HUE_illumiance changed from 246.43 to 245.68
2019-07-28 12:51:33.646 [vent.ItemStateChangedEvent] - HUE_illumiance changed from 245.68 to 245.91
2019-07-28 12:51:38.721 [vent.ItemStateChangedEvent] - HUE_illumiance changed from 245.91 to 246.00
2019-07-28 12:51:42.846 [vent.ItemStateChangedEvent] - HUE_illumiance changed from 246.00 to 246.54
2019-07-28 12:52:46.598 [vent.ItemStateChangedEvent] - HUE_illumiance changed from 246.54 to 244.90

How is it possible that one coordinator act in another way than another coordinator on this matter? Is there anywhere I can change this to less frequent reporting? I believe this would affect the battery, right?

chris · July 28, 2019, 11:22am

The change in coordinator will not make any difference here - only the binding, or the device can impact this.

The binding might have the ability to configure the reporting for this channel - I’m not sure, so you would need to check.

Kim_Andersen · July 28, 2019, 11:39am

Which is why I asked… Cause I havn´t changed anything, except the coordinator (and ofcouse the server hardware).

It doesnt seem to be an option.