Mike,
I have been doing some experimenting this morning, and thought Iâd pass along my findings. I appreciate the fact that youâve ordered some of these bulbs, and I am patient. No rush. Just wanted to provide as much information as possible.
Using the GE Link Bulb, with the Hubitat âGE Link Bulbâ Driver, I am able to get the driver to properly update the âswitchâ attribute after I pressed the âCONFIGUREâ button in the Device Page. So, now the bulb properly reflects the âswitchâ attribute status in most cases.
- Press the âCONFIGUREâ button
- Press the âONâ button, âswitchâ attribute changes to âonâ
- Press the âOFFâ button, âswitchâ attribute changes to âoffâ
- with the bulb âoffâ, pressing the âSET LEVELâ button with value greater than 0, causes the bulb to turn on, and the âswitchâ attribute changes to âonâ correctly.
- with the bulb 'on, pressing the âSET LEVELâ button with value = 0, causes no change. (Not sure what the correct behavior is in this case. I would hope setting the âlevelâ to zero would simply turn âoffâ the bulb, but not sure what the spec says.)
In all cases above, there is NEVER a âlevelâ attribute displayed on the device page.
Using the Cree Bulb, with the Hubitat âCree Bulbâ Driver, I am not able to get the driver to properly update the âswitchâ attribute, even after I pressed the âCONFIGUREâ button in the Device Page, in all cases. See below:
- Press the âCONFIGUREâ button
- Press the âONâ button, âswitchâ attribute changes to âonâ
- Press the âOFFâ button, âswitchâ attribute changes to âoffâ
- with the bulb âoffâ, pressing the âSET LEVELâ button with value greater than 0, causes the bulb to turn on, BUT the âswitchâ attribute remains showing âoffâ
- with the bulb 'on, pressing the âSET LEVELâ button with value = 0, causes no change. (Not sure what the correct behavior is in this case. I would hope setting the âlevelâ to zero would simply turn âoffâ the bulb, but not sure what the spec says.)
In all cases above, there is NEVER a âlevelâ attribute displayed on the device page.
I tried using the Hubitat âGE Link Bulbâ & the âZigbee Dimmerâ Driver on the Cree Bulb with the same results.
When I press âCONFIGUREâ using the Cree Bulb (with the native Cree Bulb Driver), I get the following in the new Zigbee Logs and the normal Logs:
In new Zigbee Logs
[Upstairs Hallway](http://192.168.1.144/hub/zigbeeLogs#zigbeeRx10881)2018-02-25 12:22:05.942 profileId:0x104, clusterId:0x8, sourceEndpoint:0, destinationEndpoint:1 , groupId:0, lastHopLqi:177, lastHopRssi:-52
[Upstairs Hallway](http://192.168.1.144/hub/zigbeeLogs#zigbeeRx10881)2018-02-25 12:22:03.928 profileId:0x0, clusterId:0x8021, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:183, lastHopRssi:-52
[Upstairs Hallway](http://192.168.1.144/hub/zigbeeLogs#zigbeeRx10881)2018-02-25 12:22:02.013 profileId:0x104, clusterId:0x6, sourceEndpoint:0, destinationEndpoint:1 , groupId:0, lastHopLqi:159, lastHopRssi:-52
[Upstairs Hallway](http://192.168.1.144/hub/zigbeeLogs#zigbeeRx10881)2018-02-25 12:21:59.995 profileId:0x0, clusterId:0x8021, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:196, lastHopRssi:-52
In the normal Logs
[dev:1](http://192.168.1.144/logs#dev1)2018-02-25 12:22:05.922:debug[raw:catchall: 0104 0008 00 01 0040 00 2A81 00 00 0000 07 01 85000000, profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:00, destinationEndpoint:01, options:0040, messageType:00, dni:2A81, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[85, 00, 00, 00]]
[dev:1](http://192.168.1.144/logs#dev1)2018-02-25 12:22:05.920:debugDID NOT PARSE MESSAGE for description : catchall: 0104 0008 00 01 0040 00 2A81 00 00 0000 07 01 85000000
[dev:1](http://192.168.1.144/logs#dev1)2018-02-25 12:22:01.926:debug[raw:catchall: 0104 0006 00 01 0040 00 2A81 00 00 0000 07 01 00000000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:01, options:0040, messageType:00, dni:2A81, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00, 00, 00, 00]]
[dev:1](http://192.168.1.144/logs#dev1)2018-02-25 12:22:01.925:debugDID NOT PARSE MESSAGE for description : catchall: 0104 0006 00 01 0040 00 2A81 00 00 0000 07 01 00000000
[dev:1](http://192.168.1.144/logs#dev1)2018-02-25 12:21:59.828:debugConfiguring Reporting and Bindings.
I am sure once you get the bulbs you will be able to sort this out. Thanks again for your hard work making this platform a great one!