Currently, I have a motorized valve, which will be controlled by a “Cover” controller from HomeMatic IP (HmIP-BROLL or HmIP-FROLL).
These controllers are just powering a Motor and giving back position information.
Therefore, they can be used perfectly fine and work with a motorized valve just as fine as with a cover-motor.
I would like to have a way to change the device type from COVER to VALVE, just in the way as it is currently possible for SWITCH device types - but the device should keep the functionality (move to position, position reporting, open / close).
Hm…
Unfortunately, that’s nearly Impossible…
From the Integration the device IS a shutter Controller and nothing else.
But since I do have the Option to Switch between the other Options weithin HomeAssistant - which means, I could use the device for other things in theory, I think it should also allow me to setup the device as valve.
I will ask there Integration devs If there’s a way to get Something implemented or If they have any Idea…
Yes, and I’m saying that you should be requesting for the integration to provide a valve instead of requesting that covers add a device_class: valve. Unless you’re saying that the device truly is a shutter device that you’ve rigged up to use on a valve.
sorry, maybe my wording was not quite clear…
The device is in fact a Shutter controller.
But instead of controlling the motor of a shutter / cover - it should controll the motor of a valve.
Technically, this is working without any issues, you have just to adapt the “Open” / “Close” position within the device correctly.
The Device is a HomeMaticIP Hardware - so, while I am using a custom component for my Homematic (IP) setup, this would also be the case with either the HomematicIP Cloud or the Homematic Integration that comes with the Core, since these are in fact Cover / Shutter controllers. (HmIP-BROLL, HmIP-FROLL)
and for someone, who’s already using Homematic, this would be a simple setup rather than searching for any other integration or using other technologies such as Zigbee, Wifi or even do just the same with an ESP… when it’s perfectly fine to use an existing controller
I know that a sensor would work… but it would just be a “sensor”…
The thing is:
I can change a switch to be a valve (open / close) or even a shutter / cover (open / close)
I can change a shutter to be a door, window, cover, gate, or several other types…
It’s just that I can’t change the device itself to be the control type “valve”.
that’s just about changing the name and ID… and isn’t what I am looking for.
Sorry
btw:
wasn’t “valve” once introduced, because people have used “shutter & cover” devices for this instead?
At least, they are comparing it with “cover” in the release notes, so I would have expected this to be available already
I think the misunderstanding here is that there’s a special integration that allows changing device type of switch into something else, including valve:
But what you screenshotted in the first post is NOT the same thing. It’s not about changing device type, which would change the entity as it does with switches
(for example from switch.whatever to light.whatever).
To be honest, I have no clue what is this option for changing device class really useful for. But it does not change the entity type.
So I think what OP is really requesting with the FR is to create a new integration to allow changing cover entities into valve entities (and maybe other things). Or to add this functionality to the integration that does that for switches. This actually does make sense to me.
thanks
this was indeed the first place I looked for - but since I could not add a “cover.” device there, I was just looking into the options of the entitiy itself, where I saw the different options the entitiy could be shown as…
Probably, I was confused about this - or I couldn’t really find the right words to describe what I wanted.
I would edit the request then. It is the first thing a potential helper will see and your most effective place to argue your point to someone to help you…
OP, when you say device type, I’m assuming you actually mean device class, right?
Even if you could change the device class (and you can, as pointed out already, through customisation), the integration won’t be able to understand it. So, even if the entities are now valve.*, the integration will only understand cover.* services.
So, what I think you are actually asking for is for HA to be a kind of proxy, either acting like the “switch as light” integration (call it “cover as valve”, for example) or having a template valve integration (like we have template cover and all of that).
I think that there is some misunderstand of requested feature. There will be no request to rename cover or shutter if Valve device will have more types. Current implementation of valve is using only ON/OFF states. There should be added secondary implementation which will have position value and on/off value in state information. For example this values could be determinated by comparison of position with open_value and close_value.
yes - and no.
The issue here is, that the device, I want to use to crontrol the device, is in fact a controller for a cover - and therefore, recognized by the integration as such.
and, this is the correct behave.
I would like to have the ability, to change the device_class, just like I can do it for switch → light; switch → plug, etc.
this would be a great benefit for DIY projects, in my opinion
and isn’t what I am looking for.