I was going to update my devices firmware and the Third Reality RGBW bult when I click the update firmware button it says that it is going to update to the newest firmware but then it gets canceled saying the device doesn't support OTA updates. Below is a screenshot of the logs.
Has anyone been able to do OTA updates on these devices. If so any tips on how to get this to work?
Edit:
Now I keep getting the in the logs. I have done a shutdown and a reboot and neither has stopped this. It comes sometimes a minute apart and sometimes three or four minutes apart. @mike.maxwell any ideas on how to stop this?
I also updated the hub to firmware 2.4.3.177 hoping it might reset something on startup. That didn't work either.
I went in and changed the driver to device, cleared everything out, applied a different driver and still getting the warn message. So went back to original Third Reality Driver.
I was trying to remove an unknown device that was showing attached to that bulb on the Zigbee Map App. In the past I have done a firmware update on other devices and it must clear their data table or something and the unknown device would go away. Now I wish I had never tried.
I still have not been able to get this entry to stop in the logs. Short of removing the device that I originally tried to update the firmware on I am out of ideas. I don't know if this would work or not since the log entry as the device name as "null" I don't know if that would work. I don't know if the HE hub is just stuck or if it is trying to actually send to the original device. If anyone has any ideas, please let me know.
I recall recent posts about another 3R device (vibration sensor maybe?) that was flooding the hub with unsolicited firmware-requests, so although this doesn't sound like the exact same, it does kinda seem to be in that neighborhood.
This one looks different though - as though the hub is trying to complete a previously-initiated OTA update.
Might want to try a shut down + power pull to clear the zigbee radio, just in case.
Another thing to try is to remove the bulb. If you want to preserve existing automations that link to this bulb, create a virtual RGBW light device, swap the TR bulb with it, remove the TR bulb from the hub completely, pair it again, swap back.
I tried the shutdown. I shut down and pulled the power for 15 seconds to clear the radios. I also done a reboot with and without the database rebuild. Maybe I should have waited 30 seconds on the power pull?
I am to the point of the last thing I could think of as well is removing the bulb. When I get back home tomorrow night I am going to try that.
The bulb has an "unknown" device showing attached to it in the zigbee map. I wonder if that unknown device is having something to do with this since the device is "null" in the log entry?
I finally got time to work on this some more. Removing the bulb completely out of Hubitat and then immediately joining it back to Hubitat appears to have fixed the issue with the "warn" log entry. As for not allowing the OTA update we won't know because I am not trying again. I have about 20 minutes of log entries with no warn message and before the longest was two minutes. I am going to mark this as solved.
