Just updated from 0.103.6 to 0.104.2, was fully prepared for the LG WebOS TV config changes and re-authorization. That was no problem whatsoever. But now a notification says
The following integrations and platforms could not be set up:
* xiaomi_aqara
Please check your config.
Did I miss an announcement somewhere? Iāve been following things reasonably closely and donāt recall anything about it.
Hi. Iām a dumb&ss. Deleted a wifi SSID this morning, and that was the remaining item that was still referencing it. I just knew Iād find something today.
reading about the many HUE integration issues, is it anywhere near safe to upgrade to 104 at all at the moment. I mean, can anyone confirm they had an update without HUE issues?
Updated 2 of my systems flawlessly, but they donāt use the integrationā¦ fearing my main system would be useless without the Hue integration, please let anyone report a working system with 104.2 and Hueā¦
and
thought the latter isnāt specifically 104 related, but still there apparently
hope these are incidents and not general 104 issues?
@nickrout
gotta thank you for taking away the fear for Hue issues: updated and everything went very smoothly indeed, no Hue issues at all as far as I can see now. Although I do see this:
while my hubs are already listed in the integrationsā¦
I do have endless amounts of this though:
2020-01-20 16:16:52 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 314, in _async_write_ha_state
attr = self.capability_attributes
File "/usr/src/homeassistant/homeassistant/components/media_player/__init__.py", line 791, in capability_attributes
if supported_features & SUPPORT_SELECT_SOURCE:
TypeError: unsupported operand type(s) for &: 'NoneType' and 'int'
On previous version 0.103 everything worked like a charm via media_player, platform: webostv.
I have WebOS 2.0 LG TV and was able to control it via HA. Now logs show next error:
Error during setup of component webostv
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 170, in _async_setup_component
hass, processed_config
File "/usr/src/homeassistant/homeassistant/components/webostv/__init__.py", line 93, in async_setup
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/components/webostv/__init__.py", line 109, in async_setup_tv
await async_setup_tv_finalize(hass, config, conf, client)
File "/usr/src/homeassistant/homeassistant/components/webostv/__init__.py", line 141, in async_setup_tv_finalize
await async_connect(client)
File "/usr/src/homeassistant/homeassistant/components/webostv/__init__.py", line 118, in async_connect
await client.connect()
File "/usr/local/lib/python3.7/site-packages/aiopylgtv/webos_client.py", line 126, in connect
return await self.connect_result
File "/usr/local/lib/python3.7/site-packages/aiopylgtv/webos_client.py", line 156, in connect_handler
close_timeout=self.timeout_connect),
File "/usr/local/lib/python3.7/site-packages/websockets/client.py", line 385, in __init__
factory, host, port, **kwds)
TypeError: create_connection() got an unexpected keyword argument 'ping_interval'
Connection lost. Reconnectingā¦
Restarts of HA and any changes to config has no affect.
Did I miss something in the release notes that changes (or removes) the ability to delete entities from the āentitiesā section of āconfigurationā?
When I click on an entity to modify itās settings the ādeleteā button is there but itās now inactive for all of the entities.
Hi
I buy today Odroid N2 and test Hassos 4.0 But It no boot on Odroid N2 also no boot from Micro SD Card and also from USB SSD Disk. Support for this is not working.
Actually I just now figured out what is happening.
You have to select the entity from the check box to the left. Then you go all the way to the top and you have the options to enable, disable or remove the selected entities.
But that brings up another issueā¦
when I try to select the entity from the unifi integration and then try to āremove selectedā it doesnāt allow me to remove it unless I delete the integration that provided the entity in the first place (unifi).
Obviously I canāt (donāt want toā¦) do that.
Even if I did delete the integration which will then remove the entity (along with every other entity from the unifi integration) as soon as I add the integration back in then that and every other entity I have deleted in the past from the unifi integration will return and then Iāll still be in exactly the same boat only worse.
I donāt understand why the ability to remove each individual entity was removed without forcing you to remove the entire integration.
especially for something like the the unifi integration where itās possible that devices will come & go from the network. I donāt want to track those devices and I donāt want them cluttering up my (already ridiculously bloated) disabled entity lists.
It would be way more convenient to be able to just delete them and not have to mess with them any more.
In this particular case I had a new device show up and Iām not sure who it belongs to since the default behavior is to create a device tracker based on the mac address of the device. So I donāt know if the device belonged to a grandchild or a friend of theirs or if someone got a new phone or who it was. So I donāt know if I want to track it or not. So I figured iād just delete it (like I have done many times in the past) and see if it gets added back in later or if it was just a one-off connection.
Now my option is to hide it by disabling it or allow it stay being tracked on my system but itās not even in my unifi controller anymore to be able to be tracked so it will forever show as away.
If I select to add new devices then it adds everything and I have to disable new devices that I donāt want to track. Since the integration adds the device by the MAC address then how do I know that I want to track the new device until I figure out what device the mac address is connected to? With a large family and grandkids getting and removing new devices regularly it becomes a chore to keep texting everyone all the time asking what the mac address is for their device when I notice a new device tracker has been added to HA. Up until now my standard way to handle it has been to delete the device tracker and if it shows back up then I know it is one I might care about. I can no longer do that.
If I select to not automatically add new devices then how do I manually add the devices to HA that I want to track?
It seems that the newer updates keep making things (specifically the unifi integration in my case) harder to maintain than easier.
there seems to be more hoops to have to jump thru to keep similar functionality in a many cases.
Yes, but they will be in the entity list as disabled along with the 75 other unifi entities that I have to keep disabled because they are on the network all the time and will keep coming back if I donāt have them disabled. the when I āshow disabled entitiesā I then have to wade thru that long list to figure out the one that I want to re-enable.
I fail to see why I canāt delete a single entity if i want without deleting the entire integration when we were able to do that before this update?
Iām getting the same thing on HASS.OS rpi4 and trying to delete groups causes my zigbee devices to lag like 5 minute delay lag that a restart wonāt fix only a snapshot restore.
But now a notification says
