Core: ZHA lights offline after restart
Home Assistant release with the issue:
0.88.1
Last working Home Assistant release (if known):
0.87
Operating environment (Hass.io/Docker/Windows/etc.):
ubuntu docker
Component/platform:
https://www.home-assistant.io/components/zha/
Description of problem:
After a restart some lights stay in an offline state. Power cycling the lights seems to get them to come back online. Different lights with each reboot, and I have seen it with different brands of lights.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
zha:
Traceback (if applicable):
Additional information:
w1ll1am23
All 59 comments
@dmulcahey any ideas whats going on here? With all the work going on around ZHA I expect bugs, but wanted to make sure this was known and/or to see if there was a fix? Should I have re-paired all might lights after the 0.88 upgrade?
w1ll1am23
on 25 Feb 2019
they will remain unavailable until they report in. It seems like some aren't reporting at all even though they are configured to do so. I have a branch under development to remediate it. I'll link it if you want to try it.
dmulcahey
on 25 Feb 2019
@dmulcahey sure I'll try to test it out tomorrow of you want to link it.
w1ll1am23
on 25 Feb 2019
dmulcahey
on 25 Feb 2019
@w1ll1am23 what are the make/model of the lights... trying to keep track of the offending bulbs
dmulcahey
on 25 Feb 2019
They are GE link bulbs but I have probably 15 and only a few have the issue. After I first installed 0.88 I also had the issue with some Ikea bulbs but I re-paired them and they didn't go offline during the last reboot.
w1ll1am23
on 25 Feb 2019
This is the only bulb people are complaining about 🤦🏻‍♂️ You’re the 3rd person I think so far with these having an issue. We’ll get em stable though.
dmulcahey
on 25 Feb 2019
I have the same problem with nearly every zigbee device, bulb, switch, temperature sensor and window/door sensors. After a while some devices switch to not available. My bulbs are all the ikea ones, the switches are from philips and ikea and the rest are xiaomi devices
hobbypunk90
on 25 Feb 2019
My "Unavailable" issue are for IKEA bulbs. (I commented in the closed ticket https://github.com/home-assistant/home-assistant/issues/21243). It sounds like this is related.
~It's always the same two. I have more of the same kind that works perfectly.~
The faulting ones got into "Unavailable" state after 120minutes.
Reconfigure from ZHA panel brings them back.
I'll try your working branch later tonight.
Keep up the good work :)
perosb
on 25 Feb 2019
@perosb that branch should fix the 120 minute thing.
dmulcahey
on 25 Feb 2019
@hobbypunk90 Can you elaborate on this?
I have the same problem with nearly every zigbee device, bulb, switch, temperature sensor and window/door sensors. After a while some devices switch to not available
What problem do you have with every device? If it is Xiaomi devices that are going unavailable it is a known issue with Xiaomi devices in general and isn't the same as what was outlined in this issue. You can help prevent the issues with Xiaomi devices dropping off by adding routers to the mesh that they like. See here for details:
Unfortunately there isn't much we can do to prevent this for the time being. There is a change in the version of zigpy that will be in .89 that may make this a little better but it isn't perfect.
Now, if it is bulbs that are going unavailable after ~2 hours try this branch (keep in mind it is experimental at this point): https://github.com/dmulcahey/home-assistant/tree/dm/zha-forgive-missing-basic
dmulcahey
on 25 Feb 2019
Since I did a reconfigure, the bulb's been online for about 5h now.
perosb
on 25 Feb 2019
Since I did a reconfigure, the bulb's been online for about 5h now.
I mean without using the different branch above ;)
perosb
on 25 Feb 2019
I figured as much. Seems like lights may need to be reconfigured in general. They weren’t configured to report originally in ZHA until very recently.
dmulcahey
on 25 Feb 2019
@w1ll1am23 https://community.smartthings.com/t/ge-link-bulbs-constantly-losing-connection/49440/2
Unfortunately, there is no fix.
GE links have a firmware problem which causes what you are seeing. It’s well-known, you will find much discussion in the forums and in fact on pretty much every other home automation forum. It’s the reason that the GE links are not on the official “works with smartthings” compatibility list. People used to buy the GE links anyway because they were much cheaper than other smart bulbs, but now that the hue whites are down to $15 at Best Buy, most people have moved away from the GE’s. If they are new bulbs and you can still return them, I would do so.
Meanwhile, the good news is that you generally don’t have to go through the whole remove and re-add process that you’ve been trying. You may be able to get them to figure out on their own that the network is still there with a few simpler steps. See the following FAQ. It won’t solve the problem, but it may give you an easier solution when it does happen.
@bigrob8181 pointed me towards this resource. It looks like the GE Link bulbs may be flaky in general.
I am still working on correctly detecting the power profile for devices. I have a pretty good POC working. This branch has the details: https://github.com/dmulcahey/home-assistant/tree/dm/zha-node-power-descriptors/homeassistant It isn't ready for prime time yet but I'm working on it :)
dmulcahey
on 26 Feb 2019
@perosb everything still good on your end?
dmulcahey
on 26 Feb 2019
@hobbypunk90 Are you able to provide the details requested above?
dmulcahey
on 26 Feb 2019
@perosb everything still good on your end?
Was just about to post an update.
Most bulbs went offline some hours ago after being online since last update.
Guess I need to try your patches. Thanks for reaching out.
Not able to reconfigure them either to make them available.
2019-02-26 13:48:10 DEBUG (MainThread) [homeassistant.components.zha.api] Reconfiguring node with ieee_address: 00:0b:57:ff:fe:11:78:16
2019-02-26 13:48:10 DEBUG (MainThread) [homeassistant.components.zha.core.device] IKEA of Sweden TRADFRI bulb E27 WS opal 980lm: started configuration
2019-02-26 13:48:10 DEBUG (MainThread) [homeassistant.components.zha.core.device] IKEA of Sweden TRADFRI bulb E27 WS opal 980lm: channel: zdo-IKEA of Sweden TRADFRI bulb E27 WS opal 980lm_ZDO async_configure stage succeeded
2019-02-26 13:48:10 DEBUG (MainThread) [homeassistant.components.zha.core.channels] 0x55e5:1:0x0005: finished channel configuration
2019-02-26 13:48:10 DEBUG (MainThread) [homeassistant.components.zha.core.device] IKEA of Sweden TRADFRI bulb E27 WS opal 980lm: channel: channel_5-0x55e5:1:0x0005 async_configure stage succeeded
2019-02-26 13:48:10 DEBUG (MainThread) [homeassistant.components.zha.core.channels] 0x55e5:1:0x0000: finished channel configuration
2019-02-26 13:48:10 DEBUG (MainThread) [homeassistant.components.zha.core.channels] 0x55e5:1:0x0004: finished channel configuration
2019-02-26 13:48:10 DEBUG (MainThread) [homeassistant.components.zha.core.device] IKEA of Sweden TRADFRI bulb E27 WS opal 980lm: channel: channel_4-0x55e5:1:0x0004 async_configure stage succeeded
perosb
on 26 Feb 2019
Please try the changes and let me know how you make out.
dmulcahey
on 26 Feb 2019
@dmulcahey thanks for the update. So I didn't get a chance to test out your branch yet, but I did downgrade to 0.87.1 which was the most stable build I have used with ZHA. I never had issues with my GE lights or Ikea lights on that build. I know that release didn't have the online/offline functionality. Is it possible to have both? Meaning if the bulb supports it don't but if not don't? Maybe some setting that could be applied to the zha device manually by the user? Another thing to mention is that I had no issues with these bulbs on Wink and they reported online and offline when on/off so not sure what they were doing differently.
w1ll1am23
on 26 Feb 2019
@w1ll1am23 Please try that branch. I am reluctant to PR the changes in w/o people reporting that it works because I can't reproduce this with the sengled bulbs that I have.
dmulcahey
on 26 Feb 2019
Sure thing, I'll test it out later tonight. I am in docker, I assume I'd need to run it as a custom component?
w1ll1am23
on 26 Feb 2019
if that makes it easier sure... you can drop the entire zha folder into custom components to try it. There should be notes on this in the release notes for .88
dmulcahey
on 26 Feb 2019
Please try the changes and let me know how you make out.
Running your zha changes now. Will let you know tomorrow.
perosb
on 26 Feb 2019
@dmulcahey I am running your branch now, and after the first startup 7 out of the 10 GE lights I am using are showing offline. I tried to "reconfigure" each of them in the ZHA control panel and that didn't fix it. Is there someone else you want me to check out?
w1ll1am23
on 26 Feb 2019
Reconfigure all of them... give it a couple mins and the. Restart. After you restart wait about 3 minutes and tell me where things stand. Set the logs to debug for Zigpy, bellows and zha and put the log on pastebin.
dmulcahey
on 26 Feb 2019
@dmulcahey https://pastebin.com/wg2Gr6Ma
I wouldn't say things are better or worse. Follow your instructions and after the restart and about 5 minutes some of the lights that I reconfigured before the reboot are back, but some aren't and others that worked before the reboot now don't.
w1ll1am23
on 26 Feb 2019
@dmulcahey I'm having similar issues. I grabbed the latest dev branch and put your zha component in custom_components. I'm having trouble with a OSRAM Lightify bulb. It went unavailable today and is stuck there. Tried reconfigure a bunch a times, didn't do anything. Several reboots, etc. Here's my log: https://pastebin.com/mFuvfwxZ. Thanks for your hard work and if you need any more info, let me know.
edit: Is this line interesting?
2019-02-27 02:00:26 DEBUG (MainThread) [bellows.zigbee.application] No such device 47538
KenCote
on 27 Feb 2019
I started noticing some zha devices (IKEA lights and others) going offline with v0.86 - v0.87, and have been trying multiple ways to debug and resolve. What finally resolved the issue for me was Yoda-x update to zigpy (see below).
When I moved to v0.88, I initially tried without the zigpy patch and immediately was disappointed when I saw all the devices are "Unavailable" initially. Since then, I learned that this is a newly expected behavior. If possible, I suggest to rename it to "Pending" or "Initializing" similar to zwave devices. Also, explaining this change in the Release Notes could probably help with the confusion.
After a few days of trial and error, I've been finally running with mostly no issues since v0.88.1 came out.
Here's what I'm running now:
1) I switched from hass.io to docker on raspbian, in order to easily apply Yoda-x patch as described here:
https://github.com/zigpy/bellows/issues/124#issuecomment-464219199
I modified that script to have v0.88.1 instead of 0.87.1 and python3.7 instead of python3.6
2) After loading home assistant, I need to wait a few minutes (not seconds) for zha devices to be online. I have some sensors that take 5+ minutes.
3) For IKEA lights I definitely had to hit Reconfigure Node in the Zha configuration screen to make it work the first time. Also, one motion sensor I had to physically wake up and remove and include in order to make it work again.
I hope this helps @hobbypunk90, @perosb and others to get things to work and helps @dmulcahey figure out a permanent solution.
Socalix
on 27 Feb 2019
@socalix we can’t rename “unavailable” because it’s built in HA functionality that isn’t part of ZHA itself. This is how ZHA should have worked from the beginning. We used to just pretend that everything was good and show old state from cache which was the cause of most of the issues.
I definitely should have had like a blog post to explain all of the changes because there seems to be a lot of confusion around what is expected and what isn't.
Also, thanks a ton for clarifying that it started before the rewrite went in (.86 or .87) that helps to differentiate network issues (or potentially bellows issues) from code issues in ZHA in HA.
2. After loading home assistant, I need to wait a few minutes (not seconds) for zha devices to be online. I have some sensors that take 5+ minutes.
This is normal... devices will not be available until they connect in for the first time after a restart.
3. For IKEA lights I definitely had to hit Reconfigure Node in the Zha configuration screen to make it work the first time. Also, one motion sensor I had to physically wake up and remove and include in order to make it work again.
It looks like we weren't setting up reporting for lights several versions back. I am working on a way to handle this transparently behind the scenes so users don't have to deal with it in the future when we add new functionality that requires reporting to be configured on nodes that we don't have it already configured on.
dmulcahey
on 27 Feb 2019
@w1ll1am23
2019-02-26 17:49:35 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=129 command=32769 args=[<Status.DEVICE_NOT_FOUND: 129>, 7c:e5:24:00:00:01:10:c5, 32709, 0, 0, []]
2019-02-26 17:49:35 DEBUG (MainThread) [zigpy.zdo] [0xa189:zdo] Unexpected ZDO reply 0x8001: [<Status.DEVICE_NOT_FOUND: 129>, 7c:e5:24:00:00:01:10:c5, 32709, 0, 0, []]
these are very suspect and I am not sure what I can do here... the network is saying these devices don't exist.
dmulcahey
on 27 Feb 2019
Please try the changes and let me know how you make out.
Running your
zhachanges now. Will let you know tomorrow.
So far so good.
I'm seeing this communication every 15 (not 90 minutes) minutes. So they seem to be reporting something.
Not sure if its your patches or if it just works.
```2019-02-27 14:02:42 DEBUG (MainThread) [bellows.uart] Data frame: b'568fb1ed542e14ba59954b65ab5592db638bc2fe12316083eacc6389dc72e50d7e'
2019-02-27 14:02:42 DEBUG (MainThread) [bellows.uart] Sending: b'8610be7e'
2019-02-27 14:02:42 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2019-02-27 14:02:42 DEBUG (MainThread) [zigpy.zcl] [0x55e5:1:0x0008] ZCL request 0x000a: [[
2019-02-27 14:02:42 DEBUG (MainThread) [zigpy.zcl] [0x55e5:1:0x0008] Attribute report received: 0=12
2019-02-27 14:02:42 DEBUG (MainThread) [homeassistant.components.zha.core.channels.general] 0x55e5:1:0x0008: received attribute: 0 update with value: 12
perosb
on 27 Feb 2019
@KenCote can you figure out what device this is: 2019-02-27 01:45:26 DEBUG (MainThread) [bellows.zigbee.application] No such device 47538 It looks like you have a device that is on the network but not in the db so zigpy doesn't know what to do w/ it
dmulcahey
on 27 Feb 2019
@perosb that's exactly what SHOULD be happening... the 90 minute thing will only kick in for bulbs that AREN't doing that. This is why I have been confused. the on/off cluster and level control cluster should report their state every 15 minutes no matter what. It looks like we never configured that originally (for lights) so a lot of people have bulbs paired that aren't reporting and it is causing a lot of confusion. Thanks for adding this information it is EXTREMELY helpful!!
dmulcahey
on 27 Feb 2019
@w1ll1am23
2019-02-26 17:49:35 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=129 command=32769 args=[<Status.DEVICE_NOT_FOUND: 129>, 7c:e5:24:00:00:01:10:c5, 32709, 0, 0, []] 2019-02-26 17:49:35 DEBUG (MainThread) [zigpy.zdo] [0xa189:zdo] Unexpected ZDO reply 0x8001: [<Status.DEVICE_NOT_FOUND: 129>, 7c:e5:24:00:00:01:10:c5, 32709, 0, 0, []]these are very suspect and I am not sure what I can do here... the network is saying these devices don't exist.
What is strange is that when running 0.87.1 less than a minute after a reboot I can control all of my lights without issue. I am not sure what that means, but I think providing users the ability to "configure" devices for reporting verse loading the cached state would allow users to get around these older bulbs.
On a side note, as the expert when it comes to ZHA do you have a list of devices you would recommend? Which ones behave best?
w1ll1am23
on 27 Feb 2019
I experience the same with SOME Sengled bulbs needing a power cycle to be recognized after an Hass.io restart. This is not new to 88.1.
Perhaps in the wrong thread.... very green at GitHub, just sharing info.
New to 88.1 is my inability to add any Philips (Hue) bulbs. Resetting the bulbs after HA version change has worked in the past but not with 88.1. They are ignored by [permit] routine.
Phrede
on 28 Feb 2019
I'm having the same issue with the 3A Smart Home Dimmer Switches.
I've never been able to get reporting working for them, and since 0.88.1 they go offline every 90 minutes and need to be re-configured.
- Is there a temporary work-around to keep them online?
- Is there a solution coming in next update so the entities aren't booted from home assistant as a result of not reporting?
- Any clues about how to get reporting working for them? (my post here)
simonwood0609
on 2 Mar 2019
Try removing them and rejoining them. There is a solution coming but probably not until .90
David F. Mulcahey
Sent from my iPhone
On Mar 1, 2019, at 10:06 PM, simonwood0609 notifications@github.com wrote:
I'm having the same issue with the 3A Smart Home Dimmer Switches.
I've never been able to get reporting working for them, and since 0.88.1 they go offline every 90 minutes and need to be re-configured.
Is there a temporary work-around to keep them online?
Is there a solution coming in next update so the entities aren't booted from home assistant as a result of not reporting?
Any clues about how to get reporting working for them? (my post here)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
dmulcahey
on 2 Mar 2019
Thanks, will try.
Is removing & re-joining them effectively the same as using the re-configure function HERE? Currently I have to press re-configured once every 90 minutes to keep them online.
simonwood0609
on 2 Mar 2019
It should be.
David F. Mulcahey
Sent from my iPhone
On Mar 1, 2019, at 10:15 PM, simonwood0609 notifications@github.com wrote:
Thanks, will try.
Is removing & re-joining them effectively the same as using the re-configure function HERE? Currently I have to press re-configured once every 90 minutes to keep them online.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
dmulcahey
on 2 Mar 2019
I have the same issue. Bulbs are available for like 2 hours, then are unavailable untill i physically switch them off and on again.
I tried to remove and repair them as sugessted, but this only made the issue worse. Now the bulbs do not even have any entities anyore. Log looks like this
2019-03-02 11:17:33 INFO (MainThread) [homeassistant.components.zha.api] Permitting joins for 60s
2019-03-02 11:17:36 INFO (MainThread) [homeassistant.components.switch.flux] Lights updated to mired:286 brightness:None, 51% of day cycle complete at 2019-03-02 12:17:36.000139+01:00
2019-03-02 11:17:41 INFO (MainThread) [zigpy.application] Device 0xd942 (00:0b:57:ff:fe:e4:55:3f) joined the network
2019-03-02 11:17:41 INFO (MainThread) [zigpy.device] [0xd942] Discovering endpoints
2019-03-02 11:17:41 INFO (MainThread) [zigpy.application] Device 0xa2bd (00:0b:57:ff:fe:c2:03:25) joined the network
2019-03-02 11:17:41 INFO (MainThread) [zigpy.device] [0xa2bd] Discovering endpoints
2019-03-02 11:17:41 INFO (MainThread) [zigpy.application] Device 0x6c90 (00:0b:57:ff:fe:c3:01:bb) joined the network
2019-03-02 11:17:41 INFO (MainThread) [zigpy.device] [0x6c90] Discovering endpoints
2019-03-02 11:17:47 INFO (MainThread) [zigpy.application] Device 0xd942 (00:0b:57:ff:fe:e4:55:3f) joined the network
2019-03-02 11:17:47 INFO (MainThread) [zigpy.application] Device 0xa2bd (00:0b:57:ff:fe:c2:03:25) joined the network
2019-03-02 11:17:47 INFO (MainThread) [zigpy.application] Device 0x6c90 (00:0b:57:ff:fe:c3:01:bb) joined the network
2019-03-02 11:17:47 INFO (MainThread) [zigpy.device] [0xd942] Discovered endpoints: [1]
2019-03-02 11:17:47 INFO (MainThread) [zigpy.endpoint] [0xd942:1] Discovering endpoint information
2019-03-02 11:17:47 INFO (MainThread) [zigpy.device] [0xa2bd] Discovered endpoints: [1]
2019-03-02 11:17:47 INFO (MainThread) [zigpy.endpoint] [0xa2bd:1] Discovering endpoint information
2019-03-02 11:17:47 INFO (MainThread) [zigpy.endpoint] [0xd942:1] Discovered endpoint information: <SimpleDescriptor endpoint=1 profile=49246 device_type=544 device_version=2 input_clusters=[0, 3, 4, 5, 6, 8, 768, 2821, 4096] output_clusters=[5, 25, 32, 4096]>
2019-03-02 11:17:47 INFO (MainThread) [zigpy.endpoint] [0xa2bd:1] Discovered endpoint information: <SimpleDescriptor endpoint=1 profile=49246 device_type=544 device_version=2 input_clusters=[0, 3, 4, 5, 6, 8, 768, 2821, 4096] output_clusters=[5, 25, 32, 4096]>
2019-03-02 11:17:48 INFO (MainThread) [zigpy.device] [0x6c90] Discovered endpoints: [1]
2019-03-02 11:17:48 INFO (MainThread) [zigpy.endpoint] [0x6c90:1] Discovering endpoint information
2019-03-02 11:17:48 ERROR (MainThread) [zigpy.zcl] [0xa2bd:1:0x1000] 0 is not a valid attribute id
2019-03-02 11:17:48 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 157, in async_device_initialized
await asyncio.gather(*endpoint_tasks)
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 231, in _async_process_endpoint
component, device_key, is_new_join)
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 297, in _handle_profile_match
await asyncio.gather(*cluster_tasks)
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 252, in _create_cluster_channel
await channel.async_configure()
File "/usr/src/app/homeassistant/components/zha/core/channels/__init__.py", line 131, in async_configure
manufacturer=manufacturer
File "/usr/src/app/homeassistant/components/zha/core/helpers.py", line 114, in bind_configure_reporting
manufacturer=manufacturer)
File "/usr/src/app/homeassistant/components/zha/core/helpers.py", line 84, in configure_reporting
**kwargs)
TypeError: object NoneType can't be used in 'await' expression
2019-03-02 11:17:48 INFO (MainThread) [zigpy.endpoint] [0x6c90:1] Discovered endpoint information: <SimpleDescriptor endpoint=1 profile=49246 device_type=544 device_version=2 input_clusters=[0, 3, 4, 5, 6, 8, 768, 2821, 4096] output_clusters=[5, 25, 32, 4096]>
2019-03-02 11:17:48 ERROR (MainThread) [zigpy.zcl] [0x6c90:1:0x1000] 0 is not a valid attribute id
2019-03-02 11:17:48 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 157, in async_device_initialized
await asyncio.gather(*endpoint_tasks)
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 231, in _async_process_endpoint
component, device_key, is_new_join)
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 297, in _handle_profile_match
await asyncio.gather(*cluster_tasks)
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 252, in _create_cluster_channel
await channel.async_configure()
File "/usr/src/app/homeassistant/components/zha/core/channels/__init__.py", line 131, in async_configure
manufacturer=manufacturer
File "/usr/src/app/homeassistant/components/zha/core/helpers.py", line 114, in bind_configure_reporting
manufacturer=manufacturer)
File "/usr/src/app/homeassistant/components/zha/core/helpers.py", line 84, in configure_reporting
**kwargs)
TypeError: object NoneType can't be used in 'await' expression
2019-03-02 11:17:49 ERROR (MainThread) [zigpy.zcl] [0xd942:1:0x1000] 0 is not a valid attribute id
2019-03-02 11:17:49 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 157, in async_device_initialized
await asyncio.gather(*endpoint_tasks)
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 231, in _async_process_endpoint
component, device_key, is_new_join)
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 297, in _handle_profile_match
await asyncio.gather(*cluster_tasks)
File "/usr/src/app/homeassistant/components/zha/core/gateway.py", line 252, in _create_cluster_channel
await channel.async_configure()
File "/usr/src/app/homeassistant/components/zha/core/channels/__init__.py", line 131, in async_configure
manufacturer=manufacturer
File "/usr/src/app/homeassistant/components/zha/core/helpers.py", line 114, in bind_configure_reporting
manufacturer=manufacturer)
File "/usr/src/app/homeassistant/components/zha/core/helpers.py", line 84, in configure_reporting
**kwargs)
TypeError: object NoneType can't be used in 'await' expression
I guess i will be stuck at 0.87 for a while, because with this, it is totally unusable
speedmann
on 2 Mar 2019
@speedmann https://github.com/home-assistant/home-assistant/pull/21592 will fix that traceback. I am still working out the issue w/ lights that aren't reporting. Should have a solution soon.
dmulcahey
on 2 Mar 2019
@simonwood0609 I hope to have a solution for this soon
dmulcahey
on 2 Mar 2019
@dmulcahey thank you :) that's fantastic. Appreciate your work.
Are you able to offer any insight into how I can make these switches (https://community.home-assistant.io/t/nue-home-bridge-zigbee-3-0-support/53537/30) report status back to Hass?
simonwood0609
on 2 Mar 2019
@simonwood0609 @speedmann https://github.com/home-assistant/home-assistant/pull/21592 should fix lights that go offline after 120 minutes.
dmulcahey
on 2 Mar 2019
@Phrede try https://github.com/home-assistant/home-assistant/pull/21592 and let me know if hue pairs now.
dmulcahey
on 2 Mar 2019
@dmulcahey Thanks. I apologize as I am not familiar, and am struggling up the curve, with the general procedures and communication here. Is it possible to provide a link that I can study how to implement breaking changes?
Phrede
on 2 Mar 2019
Not sure if I understand what you’re asking... are you trying to use the branch I linked above? If so, it’s merged to dev. If you’re unfamiliar with taking changes in you may want to wait until it’s released.
dmulcahey
on 2 Mar 2019
OK, I suppose since I do not have an understand how to implement the files I've downloaded nor a clue where to find and learn how I will remain in the dark. Both figuratively and literally.
Sorry I can't answer your question.
Phrede
on 3 Mar 2019
The directory that has your configuration.yaml. Create a folder called custom_components and place the entire zha folder in it then restart HA
dmulcahey
on 3 Mar 2019
@dmulcahey I can confirm i can pair my lights again.
I will keep you updated about the lights beeing unavailable issue after tonight. They are online for 1 1/2 hour now and i should be able to report latest tomorrow
speedmann
on 3 Mar 2019
12 hours later i can confirm the lights stay available.
Great work @dmulcahey thank you very much. can't wait for this to be available as regular release
speedmann
on 4 Mar 2019
I can confirm Hue/Philips bulbs as Zigbee are able to be found. Some required factory resets and appeared as light.zha(xxxxxxxx) which is different than prior light.philips(xxxxx). Not an issue at all for me, just FYI
Some of my Sengled bulbs also required a reset or power cycle. Probably due to the troubleshooting prior to the change.
Thanks
Phrede
on 5 Mar 2019
I can also confirm this has solved the issue with Zigbee and Philips Hue bulbs. 12+ hours since I applied the patch and they are still available.
Thank you!
maty0609
on 5 Mar 2019
Was this fix #21592 packaged with Home Assistant 0.89.0? I updated from 0.88.2 > 0.89.0 and my lights are still dropping out every 90 minutes.
simonwood0609
on 8 Mar 2019
As far as i remember correctly dmulcahey told me it was not included in 0.89 but will be in 0.90
speedmann
on 8 Mar 2019
Thanks @speedmann - noob question here, how can I pull this update manually now?
simonwood0609
on 8 Mar 2019
You could add the updated zha component to your custom_components folder.
This would mean you download the home-assistant repository and copy the complete folder components/zha/ to your components/zha/ (Path depends on how you installed hass)
But remember to remove it as soon as the update has been published as a home-assistant version.
speedmann
on 8 Mar 2019
Thanks @speedmann - I managed with a little help. Won't know if it worked until tomorrow, if lights are still online.
simonwood0609
on 8 Mar 2019
Related issues
bdraco
·
3Comments
coolriku
·
3Comments
piitaya
·
3Comments
Elmardus
·
3Comments
sibbl
·
3Comments
Most helpful comment
You could add the updated zha component to your custom_components folder.
This would mean you download the home-assistant repository and copy the complete folder
components/zha/to yourcomponents/zha/(Path depends on how you installed hass)But remember to remove it as soon as the update has been published as a home-assistant version.