#Where should I bring up the general
1 messages · Page 1 of 1 (latest)
I'm not sure what you mean?
So cover has the door device class
Meaning that yes. We can create a door that's a cover
But the question here was more like, we also don't want fridges to be a climate entity
Because while it has all the attributes, is it a climate entity?
only if the door is open
Lmao yes
I mean, a door that has open/close commands is not necessarily a cover. How to represent such a door in HA?
Well like said, we have a door device class in HA
So if you have a normal door that can open and close, it'd be perfectly fine to use a cover
Not semantically
Which a controllable door fridge hardly does
I mean it covers my fridge
Any door covers something too, then. I think the "cover" term isn't a specialization of the "door" term that adds the nuance of being controllable.
Yes but we don't want a million domains
Hence we have device classes to tell HA what kind of cover something is
Blind, damper, door, etc
I get that. We also want new users to immediately understand the terms. I think this one requires specific explanation and derives from natural semantics.
For old-timers it's OK. I wouldn't bother personally. But new users will be confused.
Sure, but in a way we also need to look at what we have today
It's not that we have 10 integrations that expose controllable doors
True. Maybe find a more fitting term for cover? 🤔
So like, of course we can push back and improve stuff. But that'd take time, so for us it's fine to have such solution in between
Yes for short term it does the job. But it would be good to keep that question in mind somewhere.
Yep
Like at this point I'd rather look at device types and being able to give more context to for example fridges
Low urgency, but it aligns with current effort of making HA less of an expert tool.
So how can we make sure HA knows that the fridge temperature is the fridge temperature and shouldn't be included in the average of the room
Oh. Nice.
So yea, hence more my question, do we consider a door a cover, or not
Because if you made your fridge a climate entity, imagine telling your voice assistant to set the temperature in the kitchen to 21°C
Now most of the fridges don't have a range that high
But just imagine when it does
Yup. I wouldn't consider a fridge thermometer a climate entity because it doesn't control a "climate". Or maybe the climate of a very small room.
I mean it does have a thermostat in there
So in theory it'd fit
But we decided it wouldn't be correct
Hence the question about the door
Maybe the real topic is to decide a room can have different separate temperatures? Imagine a spa with a warm area and a cold area.
Maybe it's related with the missing capacity of splitting rooms into sub-rooms
For the fridge example, wouldn't device classes for climate entities solve that?
- fridge
- sauna
- oven
- soldering iron / iron
- pool
- 3d printer
are examples of thermostats that should generally be excluded of room climate actions.
I guess it could
But I think device types in the end might carry more value as we can define context in an even greater detail
Haven't thought about it like this tho
Same probably for cover. If it had a device-door device class that isn't targeted by "open all doors"... otoh is this even a command that's used anywhere? (Except for USS Enterprise on vacuum robot day)
In theory you can make an automation targeting a whole area
I think device door would be a slippery slope in a way
What if Ikea came with smart cupboard
Would that be a door or a device door
(and yes i realize I'm now finding examples that don't exist)
Join the Home Assistant team and guests for the 2025 State of the Open Home live stream! It's been a full year since the Open Home Foundation was founded and...
(not trying to be dismissive btw, I haven't thought about the idea and in a way it probably would make sense, but i also want to kinda show the direction we could/might be heading as well)