[dreamscreen.devices] couldn't get state of <IP_ADDRESS>

J3n50m4t / Home-Assistant-DreamScreen-Service

Home Assistant Service for sending commands to a Wifi enabled DreamScreen

MIT License

31 stars 15 forks source link

[dreamscreen.devices] couldn't get state of <IP_ADDRESS> #32

Open dabozz88 opened 4 years ago

dabozz88 commented 4 years ago

So I'm getting a lot of warnings and logs stating:

ERROR (MainThread) [pydreamscreen.devices] couldn't get_state of ERROR (MainThread) [pydreamscreen.devices] couldn't update state for device WARNING (MainThread) [homeassistant.helpers.entity] Updating state for dreamscreen.dream_screen (<class 'custom_components.dreamscreen.DreamScreenEntity'>) took 1.026 seconds. Please report it to the custom component author.

J3n50m4t commented 4 years ago

WARNING (MainThread) [homeassistant.helpers.entity] Updating state for dreamscreen.dream_screen (<class 'custom_components.dreamscreen.DreamScreenEntity'>) took 1.026 seconds. Please report it to the custom component author. I knew this already, but I don't have the time fixing noncritical stuff right now.

The Errors: So the DS does not work for you. Could you provide more infos?

Which Dreamscreen?
Component Version?
HA Version
Config

dabozz88 commented 4 years ago

Actually it works just fine. That's why I'm confused by these errors. I tried adding a timeout to try and reduce it but it did nothing.

Dreamscreen 4K firmware 1.6.5.7 Home Assistant 0.108.6 DreamScreen-Service 4c672c3

configuration.yaml

dreamscreen: devices:

dream_screen: address:

J3n50m4t commented 4 years ago

Thats pretty strange. I'm running a similar version with a DS HD. And I don't see any of this. What a system are you running on? Is it a pretty low end system?

dabozz88 commented 4 years ago

Raspberry Pi 3B+

Been messing around with my network though, and my router is saying my dreamscreen is "inactive" most of the time even though its on and running and I can connect in with the app.