Zigbee binding

Kim_Andersen · July 28, 2019, 2:25pm

I do… Specially when doing changes to openhab, I always have the tail log open to make sure I pay attention to every changes are not given some stupid error
Andrew also mentioned above his device doesnt update this frequent. (but perhaps he didnt notice ).

Not yet I havn´t got as far as having changed the logsettings yet… Will do in a moment, and then delete and re-add the device again…

chris · July 28, 2019, 2:30pm

Look, I’m not going to argue - if you say something has changed, then fine. All I’m saying is that changing the coordinator WILL NOT change the application layer, and if you are running the same binding, then clearly that has not changed either.

There may be bugs, but I’m not sure what you are trying to say has changed!

chris · July 28, 2019, 2:55pm

I have found a Hue SML001 sensor so I will do some tests on that.

Kim_Andersen · July 28, 2019, 2:56pm

You misunderstand…
I´m not trying to argue with you. I´m trying to find answers:

I see a different behaviour of a device.
I told you what I have changed.
I asked you if this different behaviour could be due to the different coordinator.
You said no - I agreed and accepted that.

Then what? Should I just ignore the different behaviour of the device?
I was simply trying to finde the reason for this different behaviour which obvious is there, and specially since Andrew said his device does not update this frequent.

Btw. Here is the DEBUG log for removing and re-adding the device.
Zigbee Debug log.txt (35.8 KB)

Andrew_Rowe · July 28, 2019, 2:59pm

NO… I have influxdb and gafana. Before I create an automation, I always make sure I know I know what I think I know… if you… know what I mean

chris · July 28, 2019, 3:02pm

We aren’t trying to look at what has changed in Andrews system - we were trying to work out what has changed in YOUR system. Andrew might have a different sensor (there are a few around) or a different binding, or something else.

As above - I have found an SML001 so I will have a look at this. I think there is a configuration issue with this cluster, but that has always been there and has not changed (if indeed it’s a bug) so it doesn’t explain your issue still.

Kim_Andersen · July 28, 2019, 3:12pm

Agree, he could have a newer sensor/device… Mine is rather old, I believe one of the first Philips did. That may be the reason for the different behaviour between him and I.
Also agree that, whatever Andrew is discovering, doesnt explain the different behaviour I´m having here.

chris · July 28, 2019, 3:14pm

Do you care to share what version you have?

My guess is that your device has probably always done this and you’ve just missed it. In any case, it probably doesn’t matter - as we’ve seen, there appears to be no change in software, so I think the best thing is to simply resolve the issue and update the binding.

Kim_Andersen · July 28, 2019, 3:21pm

Sure no problem…

I´ll try to see if I have some old logfiles.

Wouldn´t the best option be to remove the .xx (decimals number) if possible? I doubt anyone would ever going to miss them, as it makes no sence for a lumiance sensor.

chris · July 28, 2019, 3:22pm

Thanks - This is the same model I have here.

You can always format things as you like, but the formulae here is completely wrong, so this will change anyway.

Andrew_Rowe · July 28, 2019, 3:24pm

yes… for sure different binding… my zigbee binding is 2.4 stable

just for reference:
Hue motion sensor model:9290012607

and again, just to be clear, I can make my sensor report several times a minute, like Kim’s is in the log by putting my hand over the sensor then removing my hand from the sensor. It takes a couple seconds (maybe 2) for the lights to react but my can be made to report 4-5 times a minute like in Kim’s log snippet in first post. Basically… the sensor is capable of reporting that often

chris · July 28, 2019, 3:26pm

Wow - super old

Andrew_Rowe · July 28, 2019, 3:32pm

You know Chris… watching the reintegration and ensuing IDE problems you’ve encountered trying to continue to develop this and the zwave binding has made me very gun shy to touch anything
it works
btw… great binding, great support of your bindings
thank you… we all owe you a or a

chris · July 28, 2019, 3:34pm

And with that I can completely agree - it’s been a painful few months .

Thanks.

Kim_Andersen · July 28, 2019, 4:00pm

HMM… I found an debug log from the 11th of June this year… I cant say this has actual made anything clear, except it does seems like the device do make very frequent reporting around 14-15 o´clock in day time…

A coupple of hours later, it´s alot more less frequent. At night (when light in my office is off), it hardly ever update. And while having the light bulb turned on, it does even less frequent update.

This is a snip from the debug log. I have created some empty lines inbetween the update sequence to notice the different at different times a day.

10-Jun-2019 22:48:56.762 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 102.46
10-Jun-2019 22:49:06.791 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 102.00
10-Jun-2019 22:49:28.042 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 102.46
10-Jun-2019 22:49:33.145 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 102.91
10-Jun-2019 22:49:38.055 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 102.46
10-Jun-2019 22:57:26.631 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 102.00
10-Jun-2019 22:57:31.611 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 102.46
10-Jun-2019 23:04:37.142 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 101.54
10-Jun-2019 23:09:45.765 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 102.00
10-Jun-2019 23:11:45.619 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 101.54

11-Jun-2019 03:11:51.243 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 0.00
11-Jun-2019 03:59:08.526 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 0.00
11-Jun-2019 04:31:48.158 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 12.15
11-Jun-2019 04:36:47.750 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 24.64
11-Jun-2019 04:41:47.382 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 36.45
11-Jun-2019 04:46:46.889 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 45.73
11-Jun-2019 04:51:46.505 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 57.38
11-Jun-2019 04:56:46.117 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 61.05

11-Jun-2019 14:16:52.556 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 239.24
11-Jun-2019 14:16:57.494 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 240.80
11-Jun-2019 14:17:02.362 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 240.57
11-Jun-2019 14:17:07.400 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 240.40
11-Jun-2019 14:17:10.268 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 240.46
11-Jun-2019 14:17:22.056 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 239.72
11-Jun-2019 14:17:27.119 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 240.44
11-Jun-2019 14:17:31.993 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 240.52
11-Jun-2019 14:17:36.990 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 239.62
11-Jun-2019 14:17:42.058 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 239.51
11-Jun-2019 14:17:42.964 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 239.53
11-Jun-2019 14:18:53.598 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 240.52
11-Jun-2019 14:18:58.512 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 240.63
11-Jun-2019 14:19:03.475 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 240.59

11-Jun-2019 17:33:45.299 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 190.68
11-Jun-2019 17:38:45.002 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 195.40
11-Jun-2019 17:43:44.556 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 202.37
11-Jun-2019 17:48:44.155 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 215.43
11-Jun-2019 17:53:43.753 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 229.18
11-Jun-2019 17:58:43.179 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 235.72
11-Jun-2019 18:03:42.839 [DEBUG] [inding.zigbee.converter.ZigBeeBaseChannelConverter] - 0017880102139D00: Channel zigbee:philips_sml001:ZigbeeStick:0017880102139d00:illuminance updated to 236.87

The less frequent update after 17 untill late a night, (after midnight) is probably what I´m used to see, cause it´s in this time of day I usually do changes.

So…
The device can and will most probably do a very high frequent reporting of lumiance, all depending on the light level. I´m really sorry for taking up your time on this one

chris · July 28, 2019, 4:06pm

Ok, so this is then as I expect. It means that nothing has changed, and you simply did not notice this before.

The reason is that the delta change is incorrectly set in the binding - so whenever there is any change, the device will send a report. This is why it’s sending a lot of reports during the day (when small changes in light probably aren’t noticable to the eye, but ARE noticable to the sensor) but not at night when it’s dark.

The number of times people tell me “it wasn’t like that before” and later find it was is quite high

Kim_Andersen · July 28, 2019, 4:27pm

Most probably!

When beeing convinced on something, and see what seems like a difference after making changes, it´s fair to believe the differences is cause by the change.
In this case I was wrong, because I wasn´t used to notice the lumiance change at that hour of the day where is do alot of reporting. Perhaps I should set up persistence and grafana in the future for devices like this. It would have showen the same very fast

chris · July 28, 2019, 4:49pm

Sorry - I don’t really agree. I agree that it’s certainly common that people jump to this conclusion, and for sure it’s fair to ask the question of “what has changed”, but it also causes many problems since people assume that the change is the cause and ignore other possibilities.

We see that an awful lot on the forum, and it is actually best to keep an open mind as quite often it is not the cause. Quite often, issues were already there, or something else changed that was not obvious, and by making the assumption that the change is the cause people end up blinkered and unable to accept other options.

Anyway…

This issue isn’t so simple to resolve with a single setting in the binding because there is a logarithm in the conversion to lux. The binding currently doesn’t convert the illuminance data correctly - I’ve just fixed this, but given that indoors values range from 0 to (say) 200 with bright lights, and outdoors values go up to (say) 20000 (and if you have your sensor where it can significantly be influenced by the outdoor levels, then indoors can probably go up to 1000), this is difficult to set.

Indoors a change of 5 or 10 is probably a good number, and outdoors it possibly needs to be 50 or 100. I will look at converting this channel to support the configurable reporting so that people can make their own setting, but at the moment the system doesn’t account for the calibration, so this may be rather confusing

curlyel · July 28, 2019, 4:57pm

Andrew_Rowe · July 28, 2019, 5:11pm

yeah but… but… I like it this way… don’t change it!!!
sorry, but anyhow, the option to make it report on every change should/could be a option hopefully? For use cases like mine where I want it to report on each change
(I’ll change batteries, this is one of my favorite parts of my automation, please don’t take it)

Kim, getting influxdb and Grafana set up and working was not easy for a beginner (me a few months back) and I consider it so important to be able to go back and look at what the system is doing and what values are being reported for developing a working automation system that I can not believe it isn’t ‘built in’ (working upon install of OpenHAB)