Today’s report. (not config file related, using paperUI only).
After stopping the bundle through the night, the gateway survived, but no remotes were updated when I checked this morning.
I then gathered my 9 remotes within 1m from the gateway, power cycled it and left for work.
(I also pulled the power on a HUE bridge 1m away ensuring it was not interfering on another channel).
Arriving home some 9hrs later, none of the remotes had received any update, all still pending.
Now, this is what did the trick. Remove and re-insert the battery on each remote.
Within 15-20min one by one (~15min each) they got updated until only 3 remained.
I measured the battery voltage on the ones that was still pending, and they were all just 2.9V. (they still controlled their lights OK)
After inserting fresh batteries (starting at 3.2V, but ended at 3.1/3.0 after being inserted in the remote), the 3 remaining ones was updated within 30min as well.
I then started the Ikea bundle and the Ikea items came Online at once, only to go Offline some minutes later.
I then power cycled the gateway (first power-cycle after it had updated the 9 remotes) and it looks good now after more than 1hr. Lets see what happens during the night…
Edit: still OK this morning …
Edit2: still OK in the evening.
This proves that coap communication during firmware update of remotes can kill the gateway.
I manage a second site with fever lamps and remotes, and the only thing I needed to do there was restart the bundle after the gateway updated and restarted. The new gateway firmware did not help with this issue. Still flaky.