exactly… nest thermostat was a gateway drug for finding home assistant in my case… I have lots of automations based on home/away status and also those which turns the status away or home after some conditions…
I really hope the integration will stay or maybe someone will fork this and turn into custom one?
Me to. Another tracking option plus automation’s based on number of persons by zone. I think it was pulled as it did not work for additional zones, only the default zone. I’m sure it’s just a temporary set back.
Anyone having issues with nested !include in their secrets.yaml? After trying to update I’m getting this in supervisor logs:
ERROR (SyncWorker_2) [supervisor.utils.yaml] Can't read YAML file /data/homeassistant/secrets.yaml - could not determine a constructor for the tag '!include' in "/data/homeassistant/secrets.yaml"
The entity is being set correctly when a message is published to the MQTT topic that contains the required value_json. If the MQTT message does not contain the json attribute (hum in this example) then the entity state is being set to the entire json string.
is_defined should cause it to be ignored and was doing in previous core versions.
HA in Docker.
Since “version” integration is moved to UI from yaml, I am getting “unavailable” for the latest HA docker version.
Deleted the integration, re-added it - first the sensor was correct, a bit later it is again “unavailble”.
I’m still using the deprecated Zwave integration. After upgrading, my Zwave thermostats work, but my light switches do not. I’m seeing this in the log:
2022-02-02 17:14:39 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback ZWaveBaseEntity._schedule_update.<locals>.do_update() at /usr/src/homeassistant/homeassistant/components/zwave/node_entity.py:90
Traceback (most recent call last):
File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/components/zwave/node_entity.py", line 93, in do_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 526, in async_write_ha_state
raise NoEntitySpecifiedError(
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity Jasco Products 45602 Lamp Dimmer Module Level
2022-02-02 17:15:28 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback ZWaveBaseEntity._schedule_update.<locals>.do_update() at /usr/src/homeassistant/homeassistant/components/zwave/node_entity.py:90
Traceback (most recent call last):
File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/components/zwave/node_entity.py", line 93, in do_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 526, in async_write_ha_state
raise NoEntitySpecifiedError(
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity Linear (Nortek Security Control LLC) WD500Z-1 Wall Dimmer Switch Level
2022-02-02 17:16:05 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback ZWaveBaseEntity._schedule_update.<locals>.do_update() at /usr/src/homeassistant/homeassistant/components/zwave/node_entity.py:90
Traceback (most recent call last):
File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/components/zwave/node_entity.py", line 93, in do_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 526, in async_write_ha_state
raise NoEntitySpecifiedError(
Any idea what might be wrong? The entities do have entity ids assigned.
Where should I ask for help on issues after the upgrade to 2022.2.0?
Post-upgrade the History page won’t load, it stays just the spinning loading icon. Rebooted already.
Getting the same error, and I also believe I had this once before but I can’t recall whether I threw caution to the wind and proceeded with the install. Given the nature of this update and number of breaking changes, I think I’ll hold off for a day or so. Did you go ahead with the install?
I have not fully dug into it, but I suspect the Mqtt changes are the culprit.
All my mqtt discovered devices are offline. A quick restore, and it’s all up and running again.