So, I'm seeing this message "Firmware update for null failed, the device doesn't support OTA" constantly in my logs. Is there a way to figure out what device this error pertains to? Wondering if this warning is responsible for my hub giving me a solid blue light. I just restored my database to two weeks ago but the error still appears.
I've asked about this before - the "null" makes this message completely useless. It seems like the system would know, at the point it's injecting that message into the Logs, exactly which device had failed to update.
I've only ever seen this message when manually pressing update on a zigbee device that didn't support being updated through Hubitat
@darlenetboggs is this occurring on a beta version of the hub firmware?
I was on 2.4.0.125. I have since rolled back.
it wont matter. there havent been any changes in how these messages are generated
1 Like
I rolled back because my hub had some responded twice in three days with a solid blue light.
You're saying your hub's LED went blue twice in three days?
If that's correct, what did you do when that happened?
1 Like
Unplug the device to get it back on line. The second time it happened I restored database from two weeks ago
If it happens again, you should try to use the hub diagnostic tool to access the hub and do a reboot from there. The hard restart by pulling power can cause problems with the hub's database.
The diagnostic tool is at:
HubIPAddress:8081
Diagnostic tool should be available even when the hub LED is blue.
1 Like
OK -- didn't realize the diagnostic would have been available -- I should have tried that.
1 Like
That's easy to miss unless you've read about it here or in the HE documentation on it. 
So...., any way to get stop messages in the log?
AFAIK you can safely ignore them... @mike.maxwell might have more info, but as he notes nothing changed on this recently so why they started showing up may be difficult to determine.
If you're willing, I would recommend you roll forward to the current beta release (.128) to see if the blue lights on it happen again. That needs to be troubleshooted if it's consistently happening.
I'd do a shut down/pull power/wait 30s/restore power, then do the update, and see if the blue light occurs again. If it does if you can post here and someone from HE may be able to look at your hub's engineering logs to see if anything unusual is occurring. If the issue reappears you can also check your Hub Events on the Logs tab to see if anything interesting appears there prior to the hub going blue.
1 Like
Unlikely unless the message was being spammed thousands of times per second and somehow overflowed the hubs storage system (which logs should never do).
For the blue LED, use diag tool as others suggested, reboot. Then once back online do a reboot with database rebuild. You already have effectively done the rebuild by doing the soft reset.
For the error message in the logs there are multiple thread about it already if you search.
@darlenetboggs - for a little more background...You restored a download of a previous backup a little while back. Doing a reboot w/a database rebuild is an automated version of that - during the reboot your hub will download your current database (which "cleans it" in the process), and then restore it. Probably won't help, but certainly won't hurt. Select the "Show advanced options" checkbox, and then select the "Rebuild database..." option, and then reboot.
1 Like
Will try if it happens again. I will say though that the hub wasn't processing any apps, etc. so I just thought it was dead in the water. I have a lot of apps monitoring sensors so when my lights didn't automatically come on and I saw the blue light, my first instinct was to just unplug. Anway, now I know to first. see if I can use the diagnostic tools.
For the errors in the log, do you know how long they will appear until the hub stops trying to processing the OTA?
The part of the hub that provides "higher-level" functions (devices, apps, etc.) is separate from the part that is the diagnostic tool, so you can have the former down while the latter is avaialble.
No idea on how much longer you may see the errors...I haven't had them in over a year or more, IIRC, for most users that issue has been solved. You might want to follow the link Jeff provided above to see what info may be available there. Mike (tagged him above) may reply w/more info.
Found the culprit and just re-added the device again (ThirdReality Multi-Function Night Light. Thanks everyone for your help
2 Likes
How did you find it?
