Home Automation - Smartkit

Why do you guys use retain on a SV used on a garage door / gate? I don't get it.

There should be no retain in Home Assistant of any kind ever when it comes to Tasmota devices.

HOWEVER

You want SwitchRetain and/or PowerRetain on the Tasmota device itself so that when Home Assistant restarts or power is lost to Tasmota you have the actual status reported back to HA.

Otherwise you'll door/gate will say it's open when it's closed or the other way round which is not great especially when you are remote.

Ghosting would only happen if you put Retain:True into your Yaml for Home Assistant...even once then it's all ****ed until you clean it up.

*****

This video explains it well.

 
There should be no retain in Home Assistant of any kind ever when it comes to Tasmota devices.

HOWEVER

You want SwitchRetain and/or PowerRetain on the Tasmota device itself so that when Home Assistant restarts or power is lost to Tasmota you have the actual status reported back to HA.

Otherwise you'll door/gate will say it's open when it's closed or the other way round which is not great especially when you are remote.

Ghosting would only happen if you put Retain:True into your Yaml for Home Assistant...even once then it's all ****ed until you clean it up.

*****

This video explains it well.

Look the retain is awesome for lights.
Door state is not from the sv in my case though, I get it from the alarm door sensor.
So OK it make sense if you need it for a sensor on the sv if it only send updates on state change.
 
Look the retain is awesome for lights.
Door state is not from the sv in my case though, I get it from the alarm door sensor.
So OK it make sense if you need it for a sensor on the sv if it only send updates on state change.

I can only assume the sensor isn’t linked to the SV then?

Very few people use a setup like that.
 
There should be no retain in Home Assistant of any kind ever when it comes to Tasmota devices.

HOWEVER

You want SwitchRetain and/or PowerRetain on the Tasmota device itself so that when Home Assistant restarts or power is lost to Tasmota you have the actual status reported back to HA.

Otherwise you'll door/gate will say it's open when it's closed or the other way round which is not great especially when you are remote.

Ghosting would only happen if you put Retain:True into your Yaml for Home Assistant...even once then it's all ****ed until you clean it up.

*****

This video explains it well.

HA is only confused until the next state message is sent via MQTT from the device and then it updates status accordingly. Those messages are every 1 min by default if I remember correctly.

But yeah definitely agree that MQTT retention is a bad idea on something like a gate or garage door!!
 
I can only assume the sensor isn’t linked to the SV then?

Very few people use a setup like that.
Correct, the sensor is part of the alarm system. So if the alarm is armed, and the garage door is opened, the alarm goes off. You know, the same as a PIR on a alarm system.

Most of the outside of the house door/windows have magnetic sensors, including the garage doors.

Yes I also have beams around the house, but they are wireless so if they fail the next line of defense needs to be there. I want to know a criminal is entering before he is inside, so PIRs inside the house I only put in there for the minimum insurance requirements, my goal is not to need them at all.
 
HA is only confused until the next state message is sent via MQTT from the device and then it updates status accordingly. Those messages are every 1 min by default if I remember correctly.

But yeah definitely agree that MQTT retention is a bad idea on something like a gate or garage door!!

It has not been my experience.

It never updates the state again until it’s physically changed from one to another.

Things may have changed however with the many firmware updates over time I think I first did this on Tasmota 5.

Based on that video though, and him really knowing his **** I’m pretty sure it’s required still.
 
Any idea why it throws and error intergration cover not found.

It relates to line 28. Is this supposed to be under a sub heading?
92baba96e99bf5f09b46cda81356fe1b.jpg
 
Any idea why it throws and error intergration cover not found.

It relates to line 28. Is this supposed to be under a sub heading?
92baba96e99bf5f09b46cda81356fe1b.jpg

this is mine:

- platform: mqtt
name: "Garage"
state_topic: "cmnd/garagestate/POWER2"
command_topic: "cmnd/garage/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
device_class: garage

but that is in the cover.yaml file and i have

cover: !include cover.yaml

in my configuration.yaml
 
what a first post
cover needs to be lower case
this is mine:

- platform: mqtt
name: "Garage"
state_topic: "cmnd/garagestate/POWER2"
command_topic: "cmnd/garage/POWER"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
device_class: garage

but that is in the cover.yaml file and i have

cover: !include cover.yaml

in my configuration.yaml
Changed to lower case. Should the car automatically popup?


I'm struggling with the Hass integration. Figured out mqtt had no username password fixed the config file and the Hass config file. Realised mqtt wasn't setup on the sonoff so did that. Now I can discover the device in hass.

Need to get the card to give a switch for the garage and to say open/close for the sensor, I thought this code should do it but I think I'm wrong
 
Changed to lower case. Should the car automatically popup?


I'm struggling with the Hass integration. Figured out mqtt had no username password fixed the config file and the Hass config file. Realised mqtt wasn't setup on the sonoff so did that. Now I can discover the device in hass.

Need to get the card to give a switch for the garage and to say open/close for the sensor, I thought this code should do it but I think I'm wrong

you have mosquito installed and configured?
 
Top
Sign up to the MyBroadband newsletter
X