I have zwave and zigbee devices on the same controller with 105.2 and have not had any issues. What kind of issues are you seeing?
Darn. I have taken all my hue lights off my hue hub and put them on a zigbee/zha controller and been very happy. But still miss a few things. Recently set up some zha groups with my hue lights. The cool part was that the lights seemed to operate exactly as you’d expect. they turned on/off dimmed at the exact same time as far as i could see. but apparently hue does not report status, so HA did not know if they were on/off. I was hoping the lights being available/unavailble would be fixed too.
The change that makes it possible to serve the icons was done in core, so Home Assistant Core 105 is correct 
It needed a change in the hassio integration, which is a part of the core.
https://github.com/home-assistant/home-assistant/pull/30910
well, I am not sure. The lights have been very solid for me the last few iterations. Up to 104.3 I havent seen any true issues anymore, other the when refreshing some intense Lovelace cards.
I do hope the issue now comes from some new integrations (eg I have a Nederlandse spoorwegen sensor that is acting up like crazy)
But, we ve read in the release notes, internal Hue operationfor fetching data has been changed to mitigate issues. I hope just as fervently, that doesn’t backfire, and is the cause of the issue I am re-experiencing now…
I don’t know if you’re serious or just pulling my leg. I’ll assume the latter.
Given that Home Assistant (formerly hass.io) is a hollow shell without Core, indeed, the desired new feature required a change in Core.
Supervisor’s new appearance (which is the central issue) is not visible in Core alone, you need to use Home Assistant 0.105 (which includes Core 0.105 by default).
If the re-branding’s goal is to clarify and simplify the user experience (UX), let’s do that by telling users they need Home Assistant 0.105 to see Supervisor’s new appearance. Because they won’t see it with Core 0.105 alone.
1 Like
You can’t but when you update… it automatically restarts HA… you have no choice about that.
You can access them via ssh
docker logs -f homeassistant
that’s for home assistant…
docker logs -f hassio_supervisor
That’s for supervisor
1 Like
Having some issues with Spotify.
I removed the old item and attempted to add via integrations.
Should there be a new entity appearing in states and should Spotify appear as a configured item on the integrations page?
Also, just had a look at the map in edit mode, does anyone else have “stationary” in the north pole?
Is this some sort of default or is there a potential issue in my config?
thanks.
@erikkt
Do you know if the Vera issue has been solved with the patch releases? Would really like to do the update but won’t until Im sure that my Vera controller will still work. Thanks!
kartcon
You do realise the fixes are listed in the release notes? https://www.home-assistant.io/blog/2020/02/05/release-105/#release-01051---february-5
I wouldn’t know. Can’t see anything reassuring in the release notes. I’m sticking to 104 for a long time, I am completely dependent on Vera integration working.
Prob moot but will ask anyway 
, what do you mean by “you can’t”…you can check config using hassio ha check.
I know when updating here that it restarts automatically but it doesn’t negate the fact you can check config 
not important obv so just curiousity… 
You can check config for the current configuration but you cant update to new release and run check config before restarting with the new update. You could use the custom component to check before you update but when you update it will restart immediately.
1 Like
Yeah that make sense and is my understanding of the situation/options …cheers 
Since upgrading HA now thinks i’m in the Netherlands, maps now no longer show my Zones and apparently I’ve moved country as it’s ignoring my Home location set in Zone: Home. Does this no longer override configuration.yaml?
Yes I get this too.
I have the same error along with
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 479, in _check_closed
raise RuntimeError('Event loop is closed')
Zoom out. This is in the release notes. The map no longer shows all zones and your device trackers in the default zoom position. It now defaults to only zoomed on your people.
Zones are now configured in the UI.
Log is not helpful.
I started fresh with new instqllation and copied over the old CONFIG.
Now is working, go figure.
Perhaps deleting the DB file?