@Gav_in is correct, the docs were just updated to reflect the fact that we currently only support the v3 API. I will be working on v4 support soon.
1 Like
I had the same try going into manage sensors and disabling then enabling in fact just going into manage sensors then tapping the unavailable sensor seems to work.
Developers please add one simple function, let’s name it GOOD BYE or MAKE ME ZOMBIE or what ever.
This simple function should make my homeassistant totally cut off from being updated. No more Supervisor auto updates, no OH MY nothing is working anymore. Big disclaimer on screen and simple GOOD BYE button.
Some users of homeassistant project just want stable, closed, cut off from any component auto-updating.
I have no time to read release notes, i dont want to spend my life watching progress of this development i just want to use it.
If i have ever need to do some new projects or test new hardware/integrations then i will make new ha project, test it, play with it.
I really cant understand why we cant close our home ha solution from developer influence forever.
4 Likes
In Climacell I didn’t select the version of API that I wanted. I don’t see where I can generate a version 3 key in the Climacell ui.
That’s an old version of ZwaveJS2mqtt docker. Update to ‘latest’ tag and that’ll be compatible with 2021.3.0 HA. If tyhat still doesn’t work I’d question which IP/port HA is pointing to for the ZwaveJS server.
thanks for the ultra-quick response and link to the changes. Excellent, looks like everything can now be overwritten. I use it for a Sonos and a KEF LS50W system and both benefit from being able to handle some of the commands slightly different then in the default implementation.
Re the multiple actions/commands/services, just though it would sort of resemble what you do in scripts and automation with the sequencs. I agree, you can do it with scripts (and you guessed right, I already use scripts for this).
The passwords themselves are stored in cleartext in the HA installations, so password security is a bit of a joke in HA anyway. But that’s ok (for now, not for ever) since it really is mostly irrelevant in most house network installs. While I appreciate the facility, there should be a simple way to turn these nags off. It is mostly security theatre here.
OMG! Agree with @tom_l Ihope we get it back! I could have used this a thousand times if I’d have known it as possible :-).
Just done that cheers, I’ll see how it goes
Yes, we want one 5 minute switch coded in the software to avoid hundreds of thousands of hours wasted changing and maintaining irrelevant passwords for the users. What don’t you understand?
It’s in the docs for the integration…if you dont have a V3 key you can’t get one anymore…ClimaCell API now at V4 so that’s all they are issuing now.
Reading past comments here seems the integration will work with V4 soon.
1 Like
besides all good stuff, and it is plenty in this update, there’s 1 huge letdown unfortunately: the system is very much less responsive, and (at least on Safari>Mac) keeps forcing me to reload the page, when a simple navigation via a button won’t do anything after a short time in a view.
(clicking the navigation does reveal the view in the address bar, the browser wont go there though, refreshing the page and then clicking works as supposed to)
Also, Ive have now restarted core a couple of times because it need to load something which cant be loaded via the menu, and 2 of the 4 times, the Ikea integration hasn’t come up. Has anyone else seen issues with Ikea?
Only change I made was the ZwaveJS integration on the system, which gets its data served from another instance, using core ZwaveJS Add-on. That seems to work very responsive though, so I guess that isn’t it.
Haven’t checked the change in the Rest platform the Release Party Gang mentioned yesterday last the end of the Party, (and didn’t mention in the release notes, so I updated without checking whether that would cause any issues…)
or, could it be the new Apex charts card, I’ve now taken an experimental card out and have more responsiveness…
1 Like
Firstly…
Do you realise how rude you sound?
Secondly…
Just block the URL to the version checker in your firewall.
Thirdly… This will likely mean not updating docker or your host os also
Fourthly… hopefully no api’s to services change also as you won’t get the updates to keep them working.
5 Likes
If it will take five minutes, make a commit
2 Likes
Anyone else getting this:
Logger: homeassistant.components.cloud.google_config
Source: components/cloud/google_config.py:146
Integration: Home Assistant Cloud (documentation, issues)
First occurred: 11:18:47 AM (13 occurrences)
Last logged: 11:47:59 AM
Error reporting state - 5: Requested entity was not found.
sync your devices, you probably had an entity ID get renamed that is no longer there
Part of the issue, syncs aren’t getting to Google. Only locks showing in Google ignoring the other 80ish exposed items.
Yes same here.
Edit: enabling 5 extra sensors updates all the rest again… 
I knew someone was going to make that, frankly, stupid comment. But I’ll explain. I am not an HA dev and this would be my first PR. I don’t yet know the style and culture around the code and the development, I don’t have a test environment for it, I don’t have the “tribal knowledge” of what “shortcuts” exist that break stuff or are no no’s. So for me to make this trivial change is not trivial but is rather a many tens of hours project. Get it now?
Hello everyone, the Air Visual feature that gives me the pollution situation in the city where I live no longer works after I have upgraded Home Assistant 2021.3.0 practically the data is indefinable and I see NaNs on the graph.