0.104: Sentry, Signal Messenger, IntesisHome, Sure Petcare, KEF

[tom_l]

@system

Please note that, if an integration provides an unavailable entity, the providing integration needs to be removed first, or else, those entities can not be deleted.

I may be misunderstanding this but what’s the point of being able to remove entities if you have to remove the whole integration for it to work?

Aren’t you removing all entities associated with the integration when you remove it anyway?

[RikW (Rik)]

I have three WebOS TV’s - How do I now configure these?
I have swapped the config over, but I am getting error messages about duplicates like this:

2020-01-16 02:25:07 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/webostv.yaml contains duplicate key “host”. Check lines 1 and 17.
2020-01-16 02:25:07 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/webostv.yaml contains duplicate key “name”. Check lines 2 and 18.
2020-01-16 02:25:07 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/webostv.yaml contains duplicate key “turn_on_action”. Check lines 5 and 21.

Rik

[jwelter (John Welter)]

This works for me:

webostv:
  - host: 192.168.10.xxx
    name: "Family Room TV"
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: C8:08:E9:xx:xx:xx

  - host: 192.168.10.xxx
    name: "Master Bedroom TV"
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: 38:8c:50:xx:xx:xx

Note the first TV which used the default filename for the auth was automatically ported over. The second which had a custom file name needed to be re-added.

[RikW (Rik)]

@jwelter - looking at yours - I have missed the minus sign before host Doh!
I will give it a try - cheers
Rik

[dshokouhi]

@tom_l

I may be misunderstanding this but what’s the point of being able to remove entities if you have to remove the whole integration for it to work?

Aren’t you removing all entities associated with the integration when you remove it anyway?

Not all integrations are config entries but they still register entities to the registry so in some cases you need to do both.

[lmamakos (Louis Mamakos)]

@KennethLavrsen

To clean it up I had to delete all the original entities which you can do from the UI

I had a bulk renaming problem to solve unrelated to doing a Home Assistant upgrade, and found that using hass-cli in a shell script a good solution to bulk entity renaming. See the thread over here: What is the preferred way to rename z-wave entities? - #173 by lmamakos for some info that technique.

[hefal (Henrik)]

i threw myself over a “ctrl + f” yet again to be disappointed

there is still a bug affecting everyone using more than one philips hue bridge wanting to apply hue scenes. so close but still no cigar

Support for scenes over multiple hue bridges

[christian1986]

This update creates a mes with my deconz groups, hue platform did not work and a lot of my input_boolean got renamed to _2.

So stay away if you dont want a lot of work…

[tom_l]

Painless update for me. Well done folks.

Is there any plan to add the new input_*.reload services to the Configuration/Server Controls menu?

[olloe]

I get these errors after update:

2020-01-16 09:22:05 ERROR (MainThread) [aiounifi.api] Couldn't find key: 'None'
2020-01-16 09:22:05 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 284, in async_update_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
    state = self.state
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 588, in state
    return STATE_ON if self.is_on else STATE_OFF
  File "/usr/src/homeassistant/homeassistant/components/unifi/switch.py", line 219, in is_on
    return self.port.poe_mode != "off"
  File "/usr/src/homeassistant/homeassistant/components/unifi/switch.py", line 264, in port
    return self.device.ports[self.client.sw_port]
AttributeError: 'NoneType' object has no attribute 'ports'

[franf (Fran)]

Hi,
after update, my MPD media player is failing to init.
I’ve got this error:

mpd: Error on device update!
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py”, line 299, in _async_add_entity
await entity.async_device_update(warning=False)
File “/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity.py”, line 461, in async_device_update
await self.hass.async_add_executor_job(self.update)
File “/usr/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/mpd/media_player.py”, line 154, in update
self._fetch_status()
File “/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/mpd/media_player.py”, line 136, in _fetch_status
position = self._status[“time”]
KeyError: ‘time’

Any idea? I guess it’s related to @ndonegan changes.

[Idanit]

Hi, QNAP NAS after update, failing to start. I’ve got this error:

Failed to fetch QNAP stats from the NAS
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/qnap/sensor.py", line 191, in update
    self.data["system_stats"] = self._api.get_system_stats()
  File "/usr/local/lib/python3.7/site-packages/qnapstats/qnap_stats.py", line 207, in get_system_stats
    force_list=("DNS_LIST")
  File "/usr/local/lib/python3.7/site-packages/qnapstats/qnap_stats.py", line 67, in _get_url
    self._init_session()
  File "/usr/local/lib/python3.7/site-packages/qnapstats/qnap_stats.py", line 49, in _init_session
    if self._login() is False:
  File "/usr/local/lib/python3.7/site-packages/qnapstats/qnap_stats.py", line 57, in _login
    result = self._execute_post_url("authLogin.cgi", data, False)
  File "/usr/local/lib/python3.7/site-packages/qnapstats/qnap_stats.py", line 98, in _execute_post_url
    return self._handle_response(resp, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/qnapstats/qnap_stats.py", line 110, in _handle_response
    data = xmltodict.parse(resp.content, force_list=force_list)['QDocRoot']
  File "/usr/local/lib/python3.7/site-packages/xmltodict.py", line 173, in parse
    handler = _DictSAXHandler(*args, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'force_list'

Checked config, restarted couple of times, even rebooted hassio. Nothing helped.

[Cadish]

The HEOS integration doesn’t work anymore. My devices were unavailable → I removed the integration and wanted to re-add it via Lovelace, but HEOS is not available as an option…

[Idanit]

Working fine for me

[Vasco]

I’m concerned about upgrading and having to do all that work to get deCONZ to work properly again + all automations and scripts around it.

@Robban @frenck do you have any tips or things to check before upgrading to ensure a smooth(er) upgrade?

[Cadish]

Working for me now too. I was using the custom component from @tormagj. The built-in integration works indeed.

[devastator]

Is there a way to get the all_lights group back ? I use it in node-red (together with some function node) to turn off all lights EXCEPT a couple …

Also the locks group was quite handy to lock all my doors at night, or to check if all the doors were locked. How should this be done now ? Do I have to create (and maintain …) these groups manually now ?

Removing all these groups is quite a big change. Is there a way to get them back ?

[robbinjanssen (Robbin)]

Seems like the new “light buttons” do not respect defined groups in groups.yaml?

I have the generated lovelace view. Instead of my previously organised groups with light switches, I now have a bunch of unorganised big buttons , any way to go back to switches without customizing the lovelace view?

[tom_l]

@devastator there’s this:

PSA: Turn on/off all lights in Home Assistant 0.104+ (group.all_* changes)

Seeing that group.all_* was removed from states, here are some useful canned items that will get you the same result as before. Using Services to perform an action on all entities Using all inside the entity_id field will allow you to use turn everything on or off inside a domain. You just need to pair it with the correct command. This should work for pretty much every service that has entity_id. Replaces # Do not use, this is out of date. - service: homeassistant.turn_on entity_id: grou…

[devastator]

This is way too cumbersome. Do I need to create a new binary_sensor too to check if all doors are locked ?

But disappointed by this drop without a simple replacement or way to turn it back on.