2022.2: Let's start streamlining!

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 :frowning: or maybe someone will fork this and turn into custom one?

2 Likes

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.

The HomeWizard Energy link is also broken. (A few entries down that list)

1 Like

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"

1 Like

Is anyone having trouble with the MQTT sensor entity values being pulled from OMG published topics.

Example value_template

value_template: '{{ value_json.hum | is_defined }}'

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.

1 Like

Welp. I dont see a way to configure the scan interval on androidtv anymore. Lovely. Hope I am wrong.

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.

Thanks for looking at this!

3 Likes

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.

My entire home alarm is based on MCP23017 / I2C / GPIO, everything by wire.

I believe in HA because it gives the freedom to our imagination… like GPIO does.

Make things from the root… we learn and grow… otherwise, it feels like fast food

Raspberry Pi foundation still give GPIO ports… so crazy people…

5 Likes

Anyone know if there is an entry I need to add without using ‘default_config:’ to enable diagnostics?

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:96
Integration: Home Assistant WebSocket API ([documentation](https://www.home-assistant.io/integrations/websocket_api), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+websocket_api%22))
First occurred: 6:44:08 PM (2 occurrences)
Last logged: 6:57:16 PM

[548383303904] Received invalid command: diagnostics/get

EDIT: I think its websocket_api:
EDIT2: Nope same error.

That’s a lot of update loving! This has to be the largest update to many integration I ever seen.

Thanks to all involved for the smoothest smart home server application one could ever want.

And Happy New Year.

Love the Aussie Broadband integration. Is there a way to report using in GB rather than MB though?

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?

Is that a light entity? If so, check the changelog, could be related to your use of “value_template”?

The MQTT lights no longer support, the previously deprecated, `value_template`;`state_value_template` should be used instead.

Well that’s all my legacy tosmota devices no longer working.

Why? I didn’t see Tasmota in the breaking changes.

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.

3 Likes

Anything in the logs