Iâve now rediscovered one of my HUE motion sensors and Iâm now getting some more channels discovered.
I do remember that Chris said one day, that not all discovered channels are supported necessarily by the particular deviceâŚ
Anyway: Now Iâve noticed a âswitchâ channel (in addition to âoccupancyâ,âtemperatureâ, âbattery level/voltage/alarmâ), which is new compared to my former tries (up to now I had just âmotionâ, âtemperatureâ, âilluminanceâ, âbattery levelâ).
Do you know, what the âswitchâ-channel is meant for and if it is working (and how)?
Is it probably the LED indication switch as I asked here:
This is discovered as âUnknown Zigbee device âŚâ with the seven channels as described above.
After adding this thing to the configurred things, a second thing is discovered as âPhilips SML001 - Hue motion sensorâ
If I accept the second one too, then this thing will have just the former four channels
Both seem to work (one with âmotionâ and the other with âoccupancyâ)
Seems if the device is announcing itself in two different flavoursâŚ
The log doesnât really show anything relating to the discovery - all the requests are timing out. This is probably also why you see different flavours of the device being detected - the binding looks for the services that the device reports - if these requests donât get a response, then the binding doesnât know the service exists. Maybe sometimes the device responds, and other times it doesnât - this results in different services being reported.
I think the switch channel is what I said earlier, although thereâs no information in this log, but I seem to recall that it is what these devices report. So, itâs probably not a useful channel as it can only be used to report movement in a similar way to the other channelsâŚ
This device is acting pretty strange in discovery mode.
I have mine discovered fine and added. But even though, when I start discovery again, the coordinator finds the same device again, add it and aprox 1 sec after, remove it. It IS the same device adresse as the one I have already includedâŚ
I havn´t paied enough attention to this matter, as the âoriginalâ device seems to be running just fine, even though the coordinator seems to find it everytime it perform an discovery.
Amt. though none of my zigbee devices is repporting due to the problem from yesterday. I have not restartet the server yet (or the binding), which I think is needed this time to get it runningâŚ
THe Philips SML001 (Hue motion sensor) will add 4 channels when beeing discovered allright.
Occupancy
Illuimiance
Temperature
Battery Level
You cant, so keep the sticker I dont even think you can, if you use the Philips Hue gateway. But I have never tried. I have been focusing on getting the Zigbee binding to work with my Hue and Zigbee devicesâŚ
With the latest 2.5 binding and 1.1.8 lib, it seems to run pretty good. Just got my devices up running again, after restarting the binding. So I have the Philips Hue motion sensor running, a Philips Hue Dimmer Switch, a Osram Lightify plug, and a Trust Motion sensor. All running Zigbee binding.
(My problem/crash yesterday is/was caused by something else, still struggling trying to find the reason and cure).
Hmm, I did try when I first got the motion sensor. It has been almost two years ago. I could be wrong, but I think I recall that the led behaviour was the same back then. Perhaps things has changed since.
This is probably not the device - itâs probably the binding. The binding adds a temporary thing initially to indicate that a new device has been found - it may then update that later once it knows the device information. This used to work ok, and it might still work ok, but in the past few weeks ESH removed some of the functionality that bindings use to do this, so itâs also possible itâs not working as well any more.
I seem to recall we looked at this in the past, and it did not work with all devices (or it didnât work with mine at least). If I remember correctly, my device didnât support this attribute.
@chris
What determines which channels a device supports?
I use to have a batterylevel for the Trust motion sensor. But now it´s a switch for Battery Alarm, and it seems to work in opposite way, when the switch is ON, the value is OFF.
the binding looks for the services that the device reports - if these requests donât get a response, then the binding doesnât know the service exists. Maybe sometimes the device responds, and other times it doesnât - this results in different services being reported.
A new channel was recently added for the battery alarm - we didnât remove the old channels so these can still be available.
I was just wondering how to get the batterylevel channel back⌠Also the Tampering channel as well as the Motion Intrusion doesn´t really make sense cause they dont seem to work. So I wonder how/why they appear.
I have not removed and re-added the sensor, after I updated the binding the other day. I dont know if this is needed. But the binding has been restartet quite a few times since, (due to other issues I have on my system atm).
I believe its been stated a number of times that the binding simple adds the channels the device itself reports and that some of them might not work. Not sure if its something that can be easily changed in the bindings so my method has been to ignore them and also donât link any items to them
The only way to change this is to add static definitions for every device. This isnât something I want to do unless itâs really necessary as itâs quite a bind to have to maintain these every time anything changes - especially as the number grows (in ZWave for instance, we have around 850 devices and I had to write a large management system to maintain that, and it still takes me hours every week to look after!).
Sorry Chris, I almost added a note in my post that it probably wasnât necessary and does not seem to me to be necessary. I was actually trying to save you the trouble of having to reply to yet another post asking why there are channels that donât seem to do anything because thru 1779 posts and counting, you have worked so hard to support your binding.
Again⌠Thank you so much for you hard and tireless work
I know. ButâŚ
The device report two channels which it isn´t using (or they´re not working⌠How am I suppose to tell the difference). And the battery level channel seems to be missingâŚ
I would assume a device reports the same channels each time, and not depending on the binding. Thats why i asked!
I dont even think you can, if you use the Philips Hue gateway. But I have never tried. I have been focusing on getting the Zigbee binding to work with my Hue and Zigbee devicesâŚ