Need guidance on local MQTT capabilities
-
I'm trying to replicate this
into a MQTT entity where I could set a number with a min and max value.
I can't find a standard capability that fits or any documentation on local MQTT capabilities and the only post on the forum mentioning local MQTT capabilities is this post, is it even possible in current release?
My trial and error work in local_mqtt_capabilities.yaml isn't much to show as it's just a copy of mqtt_capabilities.yaml with changed names and then I got stuck.Any guidance, examples, documentation, future feature request or denial would be much appreciated, thanks!
Reactor 24057-e9add9f5 bare metal
MQTTController 24050 -
I'm trying to replicate this
into a MQTT entity where I could set a number with a min and max value.
I can't find a standard capability that fits or any documentation on local MQTT capabilities and the only post on the forum mentioning local MQTT capabilities is this post, is it even possible in current release?
My trial and error work in local_mqtt_capabilities.yaml isn't much to show as it's just a copy of mqtt_capabilities.yaml with changed names and then I got stuck.Any guidance, examples, documentation, future feature request or denial would be much appreciated, thanks!
Reactor 24057-e9add9f5 bare metal
MQTTController 24050@Crille said in Need guidance on local MQTT capabilities:
I'm trying to replicate this
into a MQTT entity where I could set a number with a min and max value.Why? Up front, I don't understand why you would replicate something that exists, or why you'd want to add min/max values to it. This sounds like an X-Y Problem. Can you give some background on what problem you are trying to solve, and why you think doing what you are trying to do seems like a path to solving it?
-
I've rooted my Wallbox and installed a MQTT bridge on it and would like to minimize the points of failure/number of hops, i.e bypass Home Assistant in case of unexpected outage. I sure could just publish set commands in a rule but thought it would be nice to have it in one entity along with other capabilities, and learn something on the way.
The charger won't accept lower than 6 amps or higher than what the physical current switch inside it is set to, so to rule out mistakes a min/max value is preferred.If it's not possible, it's not possible. There are as said other ways and Home Assistant only gave up on me once so far and that was kind of my own fault anyway (but it initiated my quest to a backup plan).
-
I've rooted my Wallbox and installed a MQTT bridge on it and would like to minimize the points of failure/number of hops, i.e bypass Home Assistant in case of unexpected outage. I sure could just publish set commands in a rule but thought it would be nice to have it in one entity along with other capabilities, and learn something on the way.
The charger won't accept lower than 6 amps or higher than what the physical current switch inside it is set to, so to rule out mistakes a min/max value is preferred.If it's not possible, it's not possible. There are as said other ways and Home Assistant only gave up on me once so far and that was kind of my own fault anyway (but it initiated my quest to a backup plan).
@Crille look at the template in my signature and feel free to modify it. I have one for my wallbox/ev charger that will simply ignore out of range values, so no need to set min/max.
I'm controlling the solar excess via msr since day 1 with great results. -
Ah, if I only known what to search for or had a really good memory I would have found
ev_charger
announced here but not listed in Standard CapabilitiesMy charger seems to ignore out of range values as well so
ev_charger
was the missing piece in my quest, thank you @therealdb. -
T toggledbits locked this topic on