Since Sept 6 I have been getting a bunch of "warn" log messages regarding a failed firmware update.
Does anyone have ideas on what could be causing this? I have not tried to update any firmware (either HE or device). Hub is C-5, FW is 2.2.8.147. The hub has rebooted (on its own) yesterday, but I have not shut it down and restarted.
@gopher.ny or any other HE staff - I did send in a support request (ticket 23448), but thought I would reach out here to see if anyone knew what was going on.
A reboot should stop this.
Thanks. It's been rebooted (HE Reboot) but that did not fix this.
Do I need to do a shut down and then restart from there?
Try a full shut down, pull the plug for 10+ seconds, then power it back up. This seems to solve problems that a regular reboot does not.
Also, just curious, are you sending your logs to a third party system? That would be nice to setup for when the Hubitat buffer runs over and I want to see back further.
Yes - I'm using Node-RED to keep all logs for about 4 weeks. It then exports the previous weeks logs to a text file and deletes those records from the database.
Done - hopefully that fixes it 
Do you use (or are planning to use) Node-RED? If you do, let me know and I would be happy to share my setup.
Aargh - shutdown/restart did not help. Still getting the failed update messages.
Shutdown/Restart at 9:36 AM:
Failed update log messages at 9:42 AM:
@mike.maxwell @jtp10181 - any other ideas?
Wait - did you mean to literally disconnect HE from the power source? I did the shutdown from the settings menu and then flipped the switch to get it to restart...
Yes, using Node-RED already to send events to InfluxDB for Grafana. But thats just the events, not the actual log.
Yes, but you must have cut the power to restart it, just most people don't have it on a switch. Typical advise is to leave it unplugged for 10+ seconds so it can fully power down.
Also, I just noticed you are not running the newest firmware, so maybe if you update to the current it will stop complaining? 2.2.8.156 is what I am running right now on a C7.
Yeah - I do the same for events to a mySQL database. I just tagged on the logs to the same database using the websocket node and pointing it to the HE logsocket connection. There is one little trick to this - if HE is restarted (and NR is not), the websocket node thinks it is connected but it is not receiving any data. I use the NR API to force NR to "redeploy" a flow when it sees a systemStart event from HE and that fixes it.
OK - will disconnect HE from power and see if that fixes it. Thanks for your help.
Well - pulling the power did not fix it either 
Hub was restarted (after pulling the power connection) at 10:08 AM and there are a bunch of entries at 11:03 AM and then again at 11:49 AM
Going to update HE firmware to the latest and see what happens.
Please do, I've had this on my todo list for some time!
Well - upgrading to the latest firmware did not fix the issue. I'm still getting the "Firmware update for [:] failed" message in the logs 
. Updated the firmware at 1:37 PM and got the warning log entries at 3:47PM and again at 5:03PM.
I also got the following in response to the ticket that I opened. Does this mean that the ticket is closed? I got an acknowledgement and right after I got the second message saying that the system will not accept replies, so it looks like there is no way to update support on the steps that I have taken. Please let me know if I am not understanding the process!
I will do that - probably add it to the Node-RED samples thread and link it here. Will take me a few days to get it all organized.
theres a zigbee device out there that insists on trying a firmware update and isn't giving up, how many zigbee devices do you have setup?
Mike - I have 25 zigbee devices. I have not intentionally started an update. The last devices that I added were the IRIS motion sensors. Below is the list of the devices, the drivers being used and the manufacturer. Any help would be really appreciated.
see if you can figure out which device is doing this, if you enable debug logging one by one, you may see some debug data that matches the Hub log timing for these events.
Thanks - will try this, starting with the IRIS motion sensors that were added last..
Mike - I don't know if this is going to work. There is no pattern (timing etc.) to the warning messages. I turned debug on for one of the IRIS motion sensors but by the time the warning message happened, the debug had turned itself off. I am using the generic motion/temp driver and I think that it automatically turns debug off after some time. Any other suggestions?
It’s sort of a hackish way to do it, but if you enable the debug logging, switch the driver to “device” then use the clear schedules command it will remove the timer that turns off the logging. Then switch back to the normal driver. Do not save preferences on the normal driver Again or it will start the timer again. Debug logging should stay on indefinitely until you turn it off at that point.
Download the Hubitat app
