# INNR SP240's in error state after Homey update 10.2.0 **URL:** \ **Category:** Questions & Help\ **Tags:** homey-pro\ **Created:** [December 19, 2023, 10:15am UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341 "2023-12-19T10:15:39Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Jack\_Russell](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jack_russell/32/79349_2.png) [@Jack\_Russell](https://community.homey.app/u/Jack_Russell)\ **Post date:** [December 19, 2023, 10:15am UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341/1 "2023-12-19T10:15:39Z")
Annoying - Homey Pro updated to 10.2.0 last night. Since then, 4 out of 4 INNR SP240’s were in an error state: “ **Device unavailable. Zigbee is starting. Try again later.** ” Un-/replugging the devices did not help. Repairing the devices failed. Restarting Homey did not resolve the issue. Restarting the app somehow did… ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [December 19, 2023, 10:48am UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341/2 "2023-12-19T10:48:09Z")
This sort of thing happens all the time after updates. Ideally, an update should be followed by an actual unplugging of Homey instead of a plain reboot (which means that ideally, you shouldn’t let Homey autoupdate but perform the updates manually). ---
**Author:** ![Jack\_Russell](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jack_russell/32/79349_2.png) [@Jack\_Russell](https://community.homey.app/u/Jack_Russell)\ **Post date:** [December 19, 2023, 1:21pm UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341/3 "2023-12-19T13:21:31Z")
Ok, not what I hoped to hear :-), but at least good to know, thanks! Meanwhile I have also reported the issue to the INNR app guys - they tell me INNR is investigating binding/connection issues. ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [December 19, 2023, 1:24pm UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341/4 "2023-12-19T13:24:43Z")
This is almost certainly a Homey issue, nothing much they will be able to do. ---
**Author:** ![Jumpingtrees](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jumpingtrees/32/79538_2.png) [@Jumpingtrees](https://community.homey.app/u/Jumpingtrees)\ **Post date:** [December 19, 2023, 2:41pm UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341/5 "2023-12-19T14:41:04Z")
I have the same issue here. ☹ > an update should be followed by an actual unplugging of Homey instead of a plain reboot I find that hard to accept and it also didn’t worked for me. I had the same issue with the previous firmware version when I was playing around with the SP240. Only resetting the Zigbee network helped. That is not a real option for me now as I am using my SP240 in various flows. I can ping the devices in the Homey dev tools, so let’s keep our fingers crossed thaty Athom will improve on the Zigbee reliability front in near future. ---
**Author:** ![Jo\_San](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jo_san/32/3732_2.png) [@Jo\_San](https://community.homey.app/u/Jo_San)\ **Post date:** [December 19, 2023, 4:25pm UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341/6 "2023-12-19T16:25:56Z")
Same here, only with the SP240. Restart of the Innr app fixed it. ---
**Author:** ![Jack\_Russell](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jack_russell/32/79349_2.png) [@Jack\_Russell](https://community.homey.app/u/Jack_Russell)\ **Post date:** [December 19, 2023, 6:56pm UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341/7 "2023-12-19T18:56:37Z")
A new finding to add: after everything was working again, I physically moved my Homey Pro to another room (the one where I have the INNRs). Unplugged Homey, moved it, plugged it in again. To my surprise, the exact same issue occurred: all 4 SP240’s were in an error state “waiting for zigbee…” and did not recover. Meanwhile, another Aqara plug and a couple robbsmart dimmers continued working just fine. As before, only restarting the INNR app fixed the issue. (Note this is a very, very simple setup - the description above mentions all there is to it 🙂 ) ---
**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\ **Post date:** [December 19, 2023, 7:45pm UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341/8 "2023-12-19T19:45:03Z")
I experience the same thing with my SP240. Restarting the app does indeed work. I’ll also flag it to the app developer, might be interesting to look into and possibly fix! 😁 👍 ---
**Author:** ![Jack\_Russell](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jack_russell/32/79349_2.png) [@Jack\_Russell](https://community.homey.app/u/Jack_Russell)\ **Post date:** [January 8, 2024, 11:03am UTC](https://community.homey.app/t/innr-sp240s-in-error-state-after-homey-update-10-2-0/98341/9 "2024-01-08T11:03:35Z")
Just to share this issue is still being investigated by INNR. They have multiple reports of the issue and suspect a problem in the SP240 firmware.