Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Innr bulbs & plugs not available after homey 5.0 fw update #28

Open
tom9865 opened this issue Mar 11, 2021 · 12 comments
Open

Innr bulbs & plugs not available after homey 5.0 fw update #28

tom9865 opened this issue Mar 11, 2021 · 12 comments

Comments

@tom9865
Copy link

tom9865 commented Mar 11, 2021

Since homey fw 5.0 update the problem is persitantly existing. I have around 20 Innr devices. Bulbs and plugs.
They all are unavailable after a restart of homey. Red triangle, message: Zigbee device could not be initialized". Restarting the Innr App or disable/enable the app does not solve it for all devices. Healing the zigbee network (ptp homey, wait 10 min, plug back in, wait 30min before doing anything) seems to help. But only until the next reboot of homey.

Any idea how this can be fixed?
Diagnostocs report: 2389d625-5049-440d-a6b4-a942bb11931f

Best regards,
Tom

@kasteleman
Copy link
Owner

kasteleman commented Mar 11, 2021 via email

@tom9865
Copy link
Author

tom9865 commented Mar 11, 2021

Hi, Thanks for the super quick reply!
I am happy to do so.
I have one zigbee network, all devices are connected directly to Homey.
On Homey I use the following Zigbee brands:

  • Innr (plugs sp120&sp220, different bulbs -~15 devices)
  • Tint/Müller Licht (bulbs - 2 devices)
  • Ikea/Tradfri (remotes and lights - 4 devices)
  • Aqara & Xiaomi (door and temperatur sensors, switches, power plugs, motion sensors ~30 devices)
  • Osram Lightify (plugs -5 devices)

The problem only occurs with Innr devices, sometimes with all 15 devices, sometimes just with a few. Mainly the problem occurs after regular restart of homey.

What helped me today to get the Innr devices working is:

  • Pull the power plug of homey
  • Wait 15min
  • Plug Homey back in
  • Wait 30min before doing anything
  • Restart/enable/disable Innr app on homey 3-5 times

Hope that helps with figuring out?

Thanks in advance and best regards,
Tom

@kasteleman
Copy link
Owner

kasteleman commented Mar 11, 2021 via email

@liams239
Copy link

Hi, I have the same problem...

I have only Innr lights, aqara and frient devices in my zigbee network. I only have issues with the innr lights.

They don't respons or bad, or they don't switch off anymore.
Restart Homey helps a little bit, restarting innr app doesn't help. The last time it was helping for a little week to plug the power on the Innr lights for a night.

Best regards,

Liam

@kasteleman
Copy link
Owner

kasteleman commented Mar 11, 2021 via email

@tom9865
Copy link
Author

tom9865 commented Mar 11, 2021

Thanks!
Yes, e14 and RGB bulbs are the devices I am having most trouble with.
You need a screenshot of the zigbee page from dev homey? Or another report?
I deleted the troublesome devices today from homey and readded them. Since 30 min it is working. Let's see what's happening after regular homey restart (scheduled every night).

br,
Tom

The have to look into the diagnostic reports more in detail. I noticed some items about e14 and Z3 rgbw bulbs. Is it correct, if so, can you give me the exact INNR models? Op do 11 mrt. 2021 om 12:39 schreef tom9865 @.***>

Hi, Thanks for the super quick reply! I am happy to do so. I have one zigbee network, all devices are connected directly to Homey. On Homey I use the following Zigbee brands: - Innr (plugs sp120&sp220, different bulbs -~15 devices) - Tint/Müller Licht (bulbs - 2 devices) - Ikea/Tradfri (remotes and lights - 4 devices) - Aqara & Xiaomi (door and temperatur sensors, switches, power plugs, motion sensors ~30 devices) - Osram Lightify (plugs -5 devices) The problem only occurs with Innr devices, sometimes with all 15 devices, sometimes just with a few. Mainly the problem occurs after regular restart of homey. What helped me today to get the Innr devices working is: - Pull the power plug of homey - Wait 15min - Plug Homey back in - Wait 30min before doing anything - Restart/enable/disable Innr app on homey 3-5 times Hope that helps with figuring out? Thanks in advance and best regards, Tom — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNGEKGZS4CMCTAOL3JGMETTDCTVTANCNFSM4Y7YC5QQ .

@kasteleman
Copy link
Owner

kasteleman commented Mar 11, 2021 via email

@tom9865
Copy link
Author

tom9865 commented Mar 11, 2021

Actually Athom told me to do so to ensure Homey Pro RAM get's cleaned from time to time as I am using quiete a lot of apps.
But I will switch it to weekly restart now and see if it works with good performance too...
Why are you asking?

@tom9865
Copy link
Author

tom9865 commented Mar 11, 2021

In addition one sp120 plug is having always trouble too, showing the red triangle.

@kasteleman
Copy link
Owner

kasteleman commented Mar 12, 2021 via email

@tom9865
Copy link
Author

tom9865 commented Mar 12, 2021

The have to look into the diagnostic reports more in detail. I noticed some items about e14 and Z3 rgbw bulbs. Is it correct, if so, can you give me the exact INNR models? Op do 11 mrt. 2021 om 12:39 schreef tom9865 @.***>

Sure!

  • Innr RB 285 C (RGB e27)
  • Innr SP120 (plug)

@tom9865
Copy link
Author

tom9865 commented Mar 12, 2021

I ask because INNR he past I had to do that as well, but it gave me more troubles instead of benefits. Did you try to re-include that specific SP 120? Op do 11 mrt. 2021 om 23:07 schreef tom9865 @.***>

I re-included now all Innr devices. Resetted them twice manually before re-inclusion. Still after a while some (two RGB bulbs) and one SP120 plug get the red triangle. Solving tempory possible with app disable/enable/restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants