Well that is not horrible. Try fully unpowering them for 10 minutes and plugging them back in.
For device handlers, I think they will automatically go back to the best one. If not you can select it in the IDE once refound. It will not remove the device handler.
Will I have to set my rules and stuff back up for anything that has those 3 bulbs?
Currently just turned those bulbs off power cycled the hub and as soon as it comes back up Iāll turn the lights back on.
Guess Iām going to have to reset these 4 bulbs. Just waiting to know if Iām going to have to recreate my rules and etc.
Also isnāt there a way to refresh the network through the St app? I thought I had done that once before. But Iām not finding it in the app?
I think you will need to reset your rules. Or at least re-add the bulbs to them.
There is a zwave repair, but not zigbee
Ok so I reset the bulbs. Off/on 5 times. After a reset I did a scan and they added themselves back. I am now able to control them on and off from my phone however brightness and temp are not responding? Why would that be?
So the plot thickens. So @sticks18 put together a custom device handler for the two bulbs in my bed room. This was done to allow auto sunrise in the morning.
So here is where it gets weird. After testing these two bulbs they will now cone on and off but color temperature isnāt working. So I switched back over to the original device handler and the color temp works. If I switch back to the custom one the color temp no longer works, however, they were working before the outage today.
Zigbee bulbs really donāt like power outages. Can you try running Live Logging in the IDE and then change color temp on one of those bulbs using the custom devicetype? If it isnāt working, there should be an error that pops up because the underlying zigbee command is the same.
@sticks18 I will do that 4 sure man. You guys in this community rock. Can you leave info on the steps to do this? Iāve got to get to bed, Iāve been up since 3am today and canāt keep my head up any more but I will do this tomorrow at work and we can see what it gives me.
Am I supposed to do anything in the IDE other than going to the LIVE LOGGING page? Do I have to start something? I am currently there and turned the bulb on and am moving the slider but its not showing anything. Guess I will have to wait until I get home to see if its now working properly?
You shouldnāt have to do anything else. I donāt know the technical term for why, but Live Logging will often run into firewall restrictions, especially on work networks. If you have a mobile device besides your phone, you could try opening Live Logging on one of them and use the other to move the slider.
(Itās also entirely possible that Live Logging is currently not working. That happens semi-occasionally and thereās usually no indication other than nothing popping up.)
Ok, thanks man. I will check it out when I get home this evening and report back.
@sticks18 this is what I am getting in live events when moving the slider.
cb5aa264-876b-49ed-8a9d-54616e309208 6:15:49 PM: debug [raw:0104 0300 03 01 0040 00 3B40 00 00 0000 0B 01 0A87, profileId:0104, clusterId:0300, clusterInt:768, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:3B40, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[0A, 87]]
cb5aa264-876b-49ed-8a9d-54616e309208 6:15:49 PM: warn DID NOT PARSE MESSAGE for description : catchall: 0104 0300 03 01 0040 00 3B40 00 00 0000 0B 01 0A87
cb5aa264-876b-49ed-8a9d-54616e309208 6:15:49 PM: debug color cluster updated successfully
cb5aa264-876b-49ed-8a9d-54616e309208 6:15:49 PM: debug description is catchall: 0104 0300 03 01 0040 00 3B40 00 00 0000 0B 01 0A87
cb5aa264-876b-49ed-8a9d-54616e309208 6:15:48 PM: debug [raw:0104 0300 03 01 0040 00 3B40 00 00 0000 0B 01 0A87, profileId:0104, clusterId:0300, clusterInt:768, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:3B40, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[0A, 87]]
cb5aa264-876b-49ed-8a9d-54616e309208 6:15:48 PM: warn DID NOT PARSE MESSAGE for description : catchall: 0104 0300 03 01 0040 00 3B40 00 00 0000 0B 01 0A87
cb5aa264-876b-49ed-8a9d-54616e309208 6:15:48 PM: debug color cluster updated successfully
cb5aa264-876b-49ed-8a9d-54616e309208 6:15:47 PM: debug description is catchall: 0104 0300 03 01 0040 00 3B40 00 00 0000 0B 01 0A87
6:15:02 PM: info Waiting on eventsā¦
That message is saying that the we were sending an āInvalid Valueā. My devicetype had an error in it. It probably wasnāt working before, but maybe you didnāt have a reason to change the color temp. I forgot to convert the color temp value into Little Endian format. I updated the code on Github for that devicetype. Real easy fix on line 122.
Sorry about thatā¦
Ok sweet man. Thatās really odd because the setting was def working before the power outage. I appreciate you taking so much time and effort to look at all this.
That did the trick! Thanks again for your time.