#Climate MQTT

1 messages · Page 1 of 1 (latest)

errant portal
#

Hello and thank you for your attention.
What is the best practice regarding retain attribute of MQTT config and update messages?
If not here, where could I ask?

limber escarp
#

@errant portal MQTT discovery messages should be retained. You might want other messages to be retained, but it kind of depends

#

Retaining messages for commands that control devices can result in unexpected behavior (such as "ghost switching" with Tasmota devices where power commands are retained, the device disconnects and reconnects from wi-fi and therefore MQTT, and it turns on or off unexpectedly)

errant portal
#

Is your message based on some sort of code standard or golden rule?
IMHO, config messages might be retained, but I plan to repeat them over time... so retaining could be actually useless...
Any doc to read about that?

#

Or just common sense?

limber escarp
#

If you don't retain MQTT discovery messages, you will need them to be re-sent whenever HA reconnects to the MQTT broker

errant portal
#

That's clear, but I also think that if I retain them and the disabled the addon that sends them... who's gonna tell HA that the "device" no longer works/exists?

limber escarp
#

If the availability options are set, the device would become unavailable in HA

#

But yeah, if you don't want to retain the discovery messages, you'll just have to handle resending them to HA when needed

errant portal
#

Ok, thanks!
Have a good day!!

errant portal
#

Is there a way to signal HA that a setpoint is null?

limber escarp
#

None possibly. What's the use case?

errant portal
#

My installation (rehau nea smart) is a strange thing.
It works in a way that resembles a mix of ON/OFF + PRESETS
(technically, they're all presets: OFF, COMFORT, AWAY...)
When OFF, the setpoints are -17.9 c degrees.
Comfort has own setpoint, away has own setpoint.

My integration, right now, when off, simply bridges the -17.9 value.

HA allows to set the setpoint even when OFF and that really trips the installation, because you're not allowed to change setpoint when preset is OFF

I thought I'd rather tell HA that setpoint is unavailable when preset is off...

#

What do you think?

#

I tried publishing "null", "off", ""... they did not work...

#

I think I also tried to publish "unavailable"

#

Let me try "none"...

#

Oh! "None" works ...

#

Intresting... I need to understand how 🙂

limber escarp
#

None is a python keyword (the equivalent of null in other languages) which is likely why it works

errant portal
#

Much cleaner...
I need to update my add-on 😄