I’m seeing 5 days in desktop and mobile. I did see 3 at one point, but some reboots and it stays at 5.
Since 0.109 I see this in my error log :
Log Details (ERROR)
Logger: homeassistant.components.websocket_api.http.connection.2958861232
Source: components/websocket_api/connection.py:97
Integration: Home Asssitant WebSocket API (documentation, issues)
First occurred: 6:56:47 AM (1 occurrences)
Last logged: 6:56:47 AM
Error handling message: required key not provided @ data['category']. Got None
I don’t have websocket_api: in my configuration.yaml. Do I need to add it ?
Was the problem with Z-Wave switches (sliders go back and not switching (coming in 108)) solved meanwhile?
If yes, I would try this update, otherwise I will wait for some more days/weeks as my system is running pretty stable on 108.3 in the moment.
Besides this nasty thing I can only praise the work of the team! Great job!
I realize they are not supported, but the custom ISY994 is forked.
I downloaded 109 and rebooted, and said it couldn’t setup ISY994. No update for custom component in HACS.
Previously when I did the custom integration I had nothing in my configuration.yaml. I removed it from HACS. Removed it from Integrations. I then tried to add it back in. It loads fine from HACS, but once you go to Integrations and try to add it. You click on it, and it just goes back to the menu of available Integrations.
For now I added it via the standard method and it’s back in my yaml, but I am missing some things. Some of my devices are missing attributes. Specifically for me my battery states of my locks is gone. I saw the developer of the custom component has .109 revision in pre-release.
This is a heads up for all those using the custom component for ISY994 is all.
I have some covers integrated with tuya. After the update only 1 (out 5) of my covers although HA can find it, it is not working. It’s working ok with tuya app although. I already delete configuration in HA and reinstall it, I logged off from tuya app and reconnected but it is still unavailable.
No problem in log files. I also tried with incognito mode in but again the same.
Any ideas whats wrong?
Others with tuya have any problems?
It’s the first one below with the grayed arrows
The new weather card can’t be called an improvement
2 Likes
I agree! It even does not match the rest of the UI… there is no UI standards for dev? Like Apple Human Interface Guidelines?
2 Likes
Mine shows “Sunny” - I am sure it never used to do that at night!
1 Like
in this update I think there is a problem in entities card.
I have the following setup which worked ok up to 0.108.9
entities:
- entity: cover.50758014840d8e918614
- entity: cover.50758014840d8e91f036
- entity: cover.50758014840d8e91f4fd
- entity: cover.50758014840d8e91eaa2
- entity: cover.50758014840d8e918632
state_color: true
title: Cover
type: entities
with 0.109 update when my covers are half opened (state unknown) the up and down arrows are grayed and I can not handle them through HA. If the are totally opened or closed I can.
Can someone tell me how I can roll back in 0.108.9?
I have home assistant (hassio) in a NUC.
After upgrade, Onkyo platform failed to start. Anybody having the same issue?
homeassistant.components.media_player
Source: components/onkyo/media_player.py:207
Integration: Media player ([documentation](https://www.home-assistant.io/integrations/media_player), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+media_player%22))
First occurred: 8:14:32 AM (1 occurrences)
Last logged: 8:14:32 AM
Error while setting up onkyo platform for media_player
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 178, in _async_setup_platform await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT) File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for return fut.result() File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/homeassistant/homeassistant/components/onkyo/media_player.py", line 207, in setup_platform for receiver in eISCP.discover(): File "/usr/local/lib/python3.7/site-packages/eiscp/core.py", line 318, in discover ifaddrs=netifaces.ifaddresses(interface) ValueError: You must specify a valid interface name.
I‘ve noticed the same warning in the logs. It does not seem to have an effect on any functionality, though.
More significantly I have had a HA Hell day. Updated to 0.109 (docker core on 64 bit ubuntu).
Just wouldn’t start, I mean it was generating logs, but no UI. Lots of weird errors in log. Usually I am posting “perfect update once again” - but not this time!
I know I should have followed my own advice and saved the logs for reporting errors, but I restarted so many times…
I went back and forward between 0.108.x and 0.109.
In the end I commented out most of configuration.yaml. An awful lot of it was kinda legacy and had been overtaken by UI configuration. Then it started. Pleased, as I like to keep up. I’ll uncomment stuff that is still relevant bit by bit and see where the error lies.
Very grateful for the flexibilty of docker!
But that weather card? Nah!
1 Like
I’m realy sorry to say this, but for me the new integration site has become quite confusing, at least on mobile devices. Due to the new card reprentation it wastes imho a lot of space. This seems more like a decision for “design over functionality” to me
1 Like
Ok … One of the things I really dislike about pushing everything towards the integrations and away from the config; is the fact that I have to open and edit the core.config_entries whenever I need to update a setting …
For example; when you add an integration you get settings like this:
… there is absolutely no way to change any of these settings in the interface after they have been created.
11 Likes
having the same message, but also everything seems to be working till now.
I believe the “officially” supported answer is to delete the integration using the UI and re-add it from scratch. 
Not a good solution in my mind.
2 Likes
The devs are aware that not all of the ui integrations are editable after creation. Many are though.
I run hassio in NUC. can someone help by telling me how to downgrade to 0.108.9 version with ssh?
ha core update --version=0.108.9
1 Like