Well, yes, provided I don’t do it absentmindedly tomorrow when I open HA.
It’s happening with both Supervisor and Core, but Core is so far the only one annoying me on the Supervisor Dashboard; they’re just annoying me in my sensor alerts. IN case it doesn’t show, screenshot of my System page where both Core and Supervisor desperately want to downgrade.
I think I saw somewhere that this bug is fixed in the April release, so should be here on Wednesday.
I wonder if there aren’t a lot of people making new automations. For what it’s worth I’m having this issue too.
Why wouldn’t you? You sound opposed to it but not sure why.
Because to use device automations you have to use the UI. Which I don’t. For multiple reasons.
And if I did use the UI I still don’t see the benefit of device automations/services when using entities in services works just as well and the resulting yaml is way less complicated.
And areas never really seemed to be very useful.
Unless you have a very large “McMansion” sized house then targeting an area to turn on or off lights is not much harder than turning on/off the few or the couple of lights that are typically in that area individually or in a multiple entity list in a service call.
Unless I’m missing something basic in the “area” concept that is a “game changer” I never saw any real reason to get excited about it or even start looking into using it. None of my devices are assigned to areas either. I never saw the point.
Not to take away anything from others who use them but it’s simpler for me to not use those things and it’s never been a limitation at all as far as I’m aware.
Would Konnected Switchable Output is Marked UnAvailable be considered a breaking change to share or document in release notes? Have added values in external_url and internal_url to address.
Setting internal & external url values was covered in a release months ago.
To you and the others complaining about this, yes HA is open source and yes HA offers freedom in many ways however like any other software the maintainer has a reputation (and so does the software) to keep. Security is a serious issue and they need to cover their back so they don’t appear on the media later on with a story saying “Home Assistant Allows Hackers to control someone’s house and spook their kids”. That’s a huge reputational damage and can seriously affect the whole project, potentially kill it. If you’re all so lazy to update your passwords then fork the project and make the change for yourselves!? That’s what the freedom is about. You accept the product “as-is”. If the high-level maintainers made a business decision to handle the security this way, then you and the others at the very least must respect it, after all you get this for free. A lot of you don’t seem to think about the reputational issues that removing this security feature would cause. Just Google data leaks etcetera. And yes there’s ways of infiltrating a local network, if your machine is connected to the internet then there’s a way. And to those claiming that their machine isn’t connected to the internet, then how exactly would HA send the hashed passwords to the pwn service? Yeah, didn’t think of that either you guys, right? Lying isn’t pretty. I depend on this project a lot and I spend hours every week keeping everything up to date, it’s your responsibility to maintain your network, you can always stop using HA if you’re not happy with their business decisions. You may be angry about that but that’s your issue.
Sure, but Konnected was working without these values being set until 2021.3. Letting it go…
Have problem with my philips air purifier. Before it was worked good. Now I see the purifier state but can’t control it. Always get error message like: “…list index out of range”
When I want to turn off get this message:
Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/philips_airpurifier/fan.py:347
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 10:33:23 (1 occurrences)
Last logged: 10:33:23
[139649848765552] list index out of range
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 141, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1488, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1523, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 642, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 681, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 679, in _handle_entity_call
await result
File "/config/custom_components/philips_airpurifier/fan.py", line 347, in async_turn_off
await self._client.set_control_value(PHILIPS_POWER, "0")
File "/usr/local/lib/python3.8/site-packages/aioairctrl/coap/client.py", line 91, in set_control_value
return await self.set_control_values(
File "/usr/local/lib/python3.8/site-packages/aioairctrl/coap/client.py", line 115, in set_control_values
response = await self._client_context.request(request).response
File "/usr/local/lib/python3.8/site-packages/aiocoap/protocol.py", line 731, in _run_outer
await cls._run(app_request, response, weak_observation, protocol, log)
File "/usr/local/lib/python3.8/site-packages/aiocoap/protocol.py", line 756, in _run
await protocol.find_remote_and_interface(app_request)
File "/usr/local/lib/python3.8/site-packages/aiocoap/protocol.py", line 299, in find_remote_and_interface
if await ri.fill_or_recognize_remote(message):
File "/usr/local/lib/python3.8/site-packages/aiocoap/tokenmanager.py", line 192, in fill_or_recognize_remote
return await self.token_interface.fill_or_recognize_remote(message)
File "/usr/local/lib/python3.8/site-packages/aiocoap/messagemanager.py", line 330, in fill_or_recognize_remote
remote = await self.message_interface.determine_remote(message)
File "/usr/local/lib/python3.8/site-packages/aiocoap/transports/udp6.py", line 328, in determine_remote
return UDP6EndpointAddress(addrinfo[0][-1], self)
IndexError: list index out of range
aiocoap is trying to get some data from a list, but for some reason either addrinfo is an empty list, or the first list in addrinfo is empty.
Notify the owner of the philips_airpurifier custom integration. Custom integrations are outside the control of Home Assistant.
Been seeing this a bit of late as well… Had auto discovery but also moved to fixed server and it happens there as well - if i move it to another fixed it will all light back up (for a day or so only)…
Well the nice thing about targeting an area is that you can add additional devices to it in the future and not have to update all of your automations (as opposed to using a list of entities).
Also, the latest release lets you use areas and devices without using the GUI. You just need to know the area ID (I think that’s what it’s called).
Lastly, areas are nice if you’re using the auto generated UI as they keep your devices on area specific cards.
I’d have to see examples to see the advantages.
Like I said, the average person is typically only going to have a very limited number of devices in any area to be controlled by any single automation. normally users don’t add large numbers of lights or switches (or whatever) to an “area” (in the non-HA based sense of the word).
Take my livingroom as an example.
I have two sets of wall lights to control. and maybe a floor/table lamp.
that’s it.
I don’t see me needing (or being able) to add to many devices to that area that I would need to control in a single targeted automation. Again, maybe another lamp.
Even if I might later add another lamp to the mix I would likely not want all of my lights to be controlled all the time by the same automation. I mean, you can only add so many lights to a single room/area.
And if I did add another light or two (or whatever domain we could talk about) it’s trivial to add the occasional entity to the automation after I decide if I want the same automation to control everything in the area.
Maybe my use case is way different than a normal user. But it’s not like I live in an apartment and have only a few devices. I live in a big two story house.
I just can’t see myself needing to add more devices that I would like to add to existing automations by default.
I’m not sure what that means. use “areas” & “devices” for what without the UI?
Don’t you still have to use the UI to add the devices to an area?
I typically don’t use any “auto generated UI” stuff.
But, again, to each their own. If you find a use for it then great, I just don’t see the need (without concrete examples to the contrary) and I can see potential downsides to it.
Yes, you use the GUI to create and manage the area but then once it’s created you can use the area in an automation. If you don’t like them then don’t use them but they are effectively just a form of groups and I’ve never seen a Home Automation platform that didn’t allow for grouping of devices.
You could use them in any way that makes sense to you. It’s not limited to a “room”.
I could see the advantage of the Area, if we had the area as an attribute to the devices and its entities. I dont think we should ‘turn off everything’ in an Area, but I do want to be able to turn_off all motion sensors in an Area. Or all lights in an (nested) Area.
Example: Alarm system is on, all motion sensors and other motion triggers are on. Now, a guest enters the home, and I want to selectively dis-able the automation for the guest Area.
As it stands, I have several (not too complex) conditions in the trigger automations, but it would be way easier, if we could simple control that by turning off the motion sensors in the Area?
If had FR about the attributes, but that seems to have gotten no attention here, so guess nobody agrees with me on the subject 
About the GUI: I don’t use that, because it cant handle my automations (or kills the annotations) so it should be manually doable. Havent seen a way to handle Areas in automations at all tbh.
Btw, the fact we can’t have nested Areas hampers the functionality hugely. Right now I would have to create either 1 Area for my living room, but then this would act on my dining corner, audio setup, Den and ceiling spots… to name but a few smart devices in the Living.
If I’d go the other way, and create Areas for these selected smaller groups in the Living, Id be back where we are now, not being able to act upon them in a grouped way and only target several devices in that larger Area…
I wonder what ‘they’ were thinking when Architecting the Area concept in HA. 1 room Home’s? 4 light rooms?
Must confess I have been searching the docs, but this is the only thing I could find: https://www.home-assistant.io/integrations/config/#areas ?
“groups” already exist so then just use them. 
Why re-invent the wheel?
I don’t believe you can build groups in the GUI