Closed syepes closed 1 year ago
Is that happening for all device events, or just for certain devices?
Just for a specific virtual device that is using OWM (OpenWeatherMap), I have added another error.
I could this the driver but I don't know what is causing the issue. What field that is None or empty is causing the issue? I have looked at the code but cant seam to find it.
What kind of entity is that virtual device being mapped to in the integration?
hass
should be set on entities during the entity registration process. Each platform (e.g., alarm_control_panel) exposes an async_setup_entry
function. HA calls that, passing it an entity registration function async_add_entities
, to setup the integration's entities. That function, if you trace through it, eventually calls add_to_platform_start
in core/homeassistant/helpers/entity.py
, which sets the hass
property on the entity.
This is the device in HA, it's curious that some values like the illuminated is giving the error but we can see it in the HA
Hmmm...there doesn't appear to be an issue with the basic sensor entities. I setup a virtual illumination sensor, and it updates without throwing any errors.
What driver are you using in Hubitat for that device? I could try setting it up locally and see if I can reproduce the issue.
No worries, I'll give this a try also later.
This is the driver used, its the last version: https://raw.githubusercontent.com/HubitatCommunity/OpenWeatherMap-Alerts-Weather-Driver/master/OpenWeatherMap-Alerts%2520Weather%2520Driver.groovy
I do get update errors with that weather driver. I think the issue may be with either or both of the wind sensors. If I disable them, hitting "refresh" in the weather device in Hubitat works without error. If I have the Windspeed
sensor in HA, hitting "refresh" in the Hubitat weather device will generate the "hass is None" error in the HA log.
This should be fixed in v0.9.4.
I have started to observe the following exceptions from the post events received from HE:
Below is the full logs:
Running under v0.9.1