FR: Using Home Assistant Entities (select and number) for Room Configuration #412
Replies: 3 comments
-
Hey @Julien-Decoen, thanks for the FR! In fact the control switches were moved off the config into these switches with that in mind. I've opened a PR #415 to move those into the CONFIG category. Most of the remaining settings are required during load time, but I can look into the feasibility of converting into an entity. Which ones do you think are good candidates? Think of ones that would make sense to change the config during runtime. |
Beta Was this translation helpful? Give feedback.
-
Hi @jseidl, It's already great to use this category for the switches. In my case, I was mainly thinking about the new Illuminance threshold feature. It would allow changing the value without having to go through the multiple clicks of the config flow, making adjustments quicker and more flexible. |
Beta Was this translation helpful? Give feedback.
-
On my fork, I’m using something like this on my select.py file :
|
Beta Was this translation helpful? Give feedback.
-
Hi @jseidl,
Once again, thank you for your great work on
hass-magic_areas
! While working on the project, I had an idea regarding the room configuration method.Currently, you are using
config_flow
to configure devices, which works well. However, I was wondering what your thoughts would be on shifting to using Home Assistant entities like Select Entity or Number Entity for configuring rooms. This could offer more flexibility and allow users to configure rooms more dynamically through the Home Assistant UI, while seamlessly integrating with other features.Additionally, the
select
andnumber
entities could have a deviceentity_category
set toconfig
, as mentioned on this page.Thanks again for your great work, and I'd love to hear your thoughts on this!
Lou juicy
Beta Was this translation helpful? Give feedback.
All reactions