Core: TypeError: 'uvloop.loop.TimerHandle' object is not callable

[maxandersen]

Home Assistant release with the issue:

0.93

Last working Home Assistant release (if known):
0.92 (last one i didn't notice the errors)

Operating environment (Hass.io/Docker/Windows/etc.):

hassio Pi3+

Component/platform:

deconz

Description of problem:

I'm seeing repeated errors of this form in logs:

2019-05-23 15:58:13 ERROR (MainThread) [homeassistant.core] Error executing service <ServiceCall light.turn_on (c:63e40f25bbed4427b0d871d305751503): entity_id=['group.hallway_lights'], color_temp=299, brightness=1
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1150, in _safe_execute
    await self._execute_service(handler, service_call)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1163, in _execute_service
    await handler.func(service_call)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/light/__init__.py", line 297, in async_handle_light_on_service
    await light.async_turn_on(**pars)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/deconz/light.py", line 143, in async_turn_on
    await self._device.async_set_state(data)
  File "/usr/local/lib/python3.7/site-packages/pydeconz/light.py", line 155, in async_set_state
    await self.async_set(field, data)
  File "/usr/local/lib/python3.7/site-packages/pydeconz/deconzdevice.py", line 128, in async_set
    self.cancel_retry()
  File "/usr/local/lib/python3.7/site-packages/pydeconz/deconzdevice.py", line 147, in cancel_retry
    self._cancel_retry()
TypeError: 'uvloop.loop.TimerHandle' object is not callable

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[ghost]

Hey there @kane610, mind taking a look at this issue as its been labeled with a integration (deconz) you are listed as a codeowner for? Thanks!

_This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people._

[Kane610]

Thanks for reporting this issue @maxandersen

I've seen this myself in my production environment. Haven't been able to reproduce it in my dev environment yet. Trying a few things out

[Kane610]

Hopefully this will be solved with https://github.com/home-assistant/home-assistant/pull/23725

[Hypfer]

I'm also experiencing this. light.turn_on is simply failing on one of my light entities.
Interestingly, the entity in question is in fact a deconz group.

A restart of HA seems to have fixed it (temporarily?)

[Kane610]

I introduced a method that would do a retry if the bridge was busy with previous actions. That doesn't happen too often. Only on many simultaneous requests. I missed a reset of a counter that would generate this issue. I haven't been able to reproduce it on my dev instance so can't be 100% sure I've solved it completely. It will come with the next major release of hass

[vandalon]

Exact same issue here, with deconz group and single light.

[m-e-h]

Just to add context, I've been experiencing this after I execute a turn off "all lights". A handful of bulbs will continue to give this uvloop error until I restart HA. I have about 30 or so bulbs.

[vandalon]

I've been testing with the "new" component as is available on github, as a custom component in 0.93.2. I've seen no issues for the last 2 days.

[Kane610]

Just to add context, I've been experiencing this after I execute a turn off "all lights". A handful of bulbs will continue to give this uvloop error until I restart HA. I have about 30 or so bulbs.

Yes, the issue is with a retry mechanism to resend messages that get a queue is full error from deconz

[Kane610]

@vandalon are you sure? You can't do custom components with config entries yet.

If its true it's awesome that you verified!

[vandalon]

I just added the deconz component from github in the custom components folder and I got the warning in the log about using this custom component so I presume it works :) 2 days is not enough to be sure if it works but it looks promising

[Kane610]

Ok, hmm, maybe it works like that. Would be great if you could try out the beta after tomorrow.

[vandalon]

I'm afraid I can't because i'm vacation for a little while from today :)

[carloscae]

Just to add context, I've been experiencing this after I execute a turn off "all lights". A handful of bulbs will continue to give this uvloop error until I restart HA. I have about 30 or so bulbs.

This was puzzling me as lights were always failing when I got back home from work. Now I changed my "Leaving Home" automation to turn off lights individually instead of using the group.all_lights. Let's see how it goes. Thanks for the tip.

[Kane610]

It would be great if someone who have experienced the issue upgrade to the beta and verify if it is fixed

[maxandersen]

What's the easiest way to try the beers on a hassio install?

[Kane610]

I think you can select beta track in the hassio configuration somewhere

[m-e-h]

What's the easiest way to try the beers on a hassio install?

If hassio could make beer, my life would be complete. :smile:

[Kane610]

@m-e-h someone has got to be the first 😂👍🏻

[maxandersen]

trying to install the :beer: now.

[Kane610]

@maxandersen how did it go?

[maxandersen]

Sorry. Beta never seemed to I nstall choosing dev channel. I'll have to try again over the weekend

[Kane610]

if you're running docker, try rc and not dev (too volatile for production)

[vandalon]

Still running with the custom component and I had no issues since then.

[carloscae]

I can verify that after removing the automation that turns off group.all_lights, I had for over a week no more issues.

Not running betas, sorry. Wife complains enough about stable releases. :D

[Kane610]

Well release is imminent so too late to change now :)

[maxandersen]

if you're running docker, try rc and not dev (too volatile for production)

i'm running hassio so not sure how to do that.

In any case, I only just today got the betas to show up but since too late anyway i'll wait for the final reelase to test (for the wife sanity :)

[Kane610]

Release is out 🎉

[m-e-h]

Still seeing the error with the group.all_lights trigger.

Log Details (ERROR)
Thu Jun 06 2019 00:18:51 GMT-0400 (Eastern Daylight Time)
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 1150, in async_call
    self._execute_service(handler, service_call))
  File "/usr/src/homeassistant/homeassistant/core.py", line 1172, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 194, in handle_service
    required_features
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 316, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/src/homeassistant/homeassistant/components/group/light.py", line 186, in async_turn_off
    light.DOMAIN, light.SERVICE_TURN_OFF, data, blocking=True)
  File "/usr/src/homeassistant/homeassistant/core.py", line 1150, in async_call
    self._execute_service(handler, service_call))
  File "/usr/src/homeassistant/homeassistant/core.py", line 1172, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 194, in handle_service
    required_features
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 316, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/src/homeassistant/homeassistant/components/deconz/light.py", line 161, in async_turn_off
    await self._device.async_set_state(data)
  File "/usr/local/lib/python3.7/site-packages/pydeconz/deconzdevice.py", line 41, in async_set_state
    await self.async_set(field, data)
  File "/usr/local/lib/python3.7/site-packages/pydeconz/deconzdevice.py", line 46, in async_set
    self.cancel_retry()
  File "/usr/local/lib/python3.7/site-packages/pydeconz/deconzdevice.py", line 66, in cancel_retry
    self._cancel_retry()
TypeError: 'uvloop.loop.TimerHandle' object is not callable

Haven't noticed any lights not working yet though. So that's good.

[Kane610]

I'm investigating this issue. I just need to verify it with all the lights in the house 😎

[m-e-h]

Thanks @Kane610 !
That seems to have fixed the error for me. 🎉

[Kane610]

Awesome! 🎉