Home Automation - Smartkit

Tinuva said:
Damn, I never did all of these on my garage door SVs. Only PulseTime1 1 and that was all. Don't think I ever had ghost switching yet. That was previous house. Still need to reinstall them, but probably will only connect them up as is with no reconfig.
Click to expand...

It’s only really relevant to a reboot of Home Assistant retaining the status.

You didn’t run Home Assistant back then.
 
chickenbeef said:
Set up some actionable notifications today and they're super cool! Should have done it sooner.

668fac09b8277961939b3ef38d53b905.jpg
Click to expand...
Thats Android?
 
xrapidx said:
Thats Android?
Click to expand...
Yes. Can be done on iOS too.

companion.home-assistant.io

Introduction | Home Assistant Companion Docs

The mobileapp notify platform accepts the standard title, message and target parameters used by the notify platform. The mobile\app notify platform supports targets as services. As long as you granted notifications permissions during setup, you will find all your devices listed as targets for...
companion.home-assistant.io companion.home-assistant.io
 
chickenbeef said:
Yes. Can be done on iOS too.

companion.home-assistant.io

Introduction | Home Assistant Companion Docs

The mobileapp notify platform accepts the standard title, message and target parameters used by the notify platform. The mobile\app notify platform supports targets as services. As long as you granted notifications permissions during setup, you will find all your devices listed as targets for...
companion.home-assistant.io companion.home-assistant.io
Click to expand...

Wasnt aware it was available on Android yet - wil check it out.
 
SauRoNZA said:
You can clear it right inside Home Assistant these days.

There is an MQTT tool now.

But yes quite possibly an old configuration tested at some point with retain enabled in HA and that will remain there forever until manually cleared because HA/MQTT is stupid like that.
Click to expand...

Ok
So I setup a new SV, the only console command was PulseTime1 1 .
Flicking wifi hidden SSID on and off didn't cycle the relay. So I have the new Sonoff SV the MQTT topic of the old one. As soon as I did this, and cycled the SSID hidden state the new SV started to experience the same issue. So it is related to MQTT.
Ended up restarted the MQTT Docker container in Unraid and since then the issue has been resolved.

Its also working fine in Home Assistant with just PulseTime1 1
 
calypso said:
Ok
So I setup a new SV, the only console command was PulseTime1 1 .
Flicking wifi hidden SSID on and off didn't cycle the relay. So I have the new Sonoff SV the MQTT topic of the old one. As soon as I did this, and cycled the SSID hidden state the new SV started to experience the same issue. So it is related to MQTT.
Ended up restarted the MQTT Docker container in Unraid and since then the issue has been resolved.

Its also working fine in Home Assistant with just PulseTime1 1
Click to expand...

good stuff man
 
I take this back restarting the MQTT server only works for 1 wifi cycle. After that its back to firing the relay for each disconnection/reconnection.
 
calypso said:
Ok
So I setup a new SV, the only console command was PulseTime1 1 .
Flicking wifi hidden SSID on and off didn't cycle the relay. So I have the new Sonoff SV the MQTT topic of the old one. As soon as I did this, and cycled the SSID hidden state the new SV started to experience the same issue. So it is related to MQTT.
Ended up restarted the MQTT Docker container in Unraid and since then the issue has been resolved.

Its also working fine in Home Assistant with just PulseTime1 1
Click to expand...

Then you retained messages in HA at some point and those messages are retained in MQTT.

Likely you didn’t have persistent storage enabled in MQTT so the restart recreated the database.

Home Assistant will work without the other settings but If you restart it your status won’t be correct. Usually default state is off so if it was on before the reboot then it will be off upon a restart.

No problem for a switch with pulse time that goes off anyway, but a problem for a sensor if it says your door is open when it’s actually closed.

What’s the purpose of hiding the SSID? If it’s for security it’s utterly meaningless.
 
calypso said:
I take this back restarting the MQTT server only works for 1 wifi cycle. After that its back to firing the relay for each disconnection/reconnection.
Click to expand...

Then you need to...

Delete the MQTT database and restart it.

OR

Go blank the MQTT topic so it doesn’t store it’s retained status.

You can riddle with it in HA under the MQTT menu and if you read the topic you can usually see what’s stuck there. Then you write a “” or ‘’ to that topic to reset it to nothing.

Obviously assuming you’ve removed any “retain = true” from your HA configuration files.

****

Found a good link for both options.

Killing the DB is much easier and more reliable.

community.openhab.org

Clearing MQTT retained messages

Clearing retained messages in mosquitto Purpose The purpose of this tutorial is to present solutions to clear retained messages in the Eclipse Mosquitto MQTT Broker. Retained messages can be troublesome and/or unwanted. Many mosquitto tutorials included a retain option in the configuration and...
community.openhab.org community.openhab.org
 
SauRoNZA said:
Then you retained messages in HA at some point and those messages are retained in MQTT.

Likely you didn’t have persistent storage enabled in MQTT so the restart recreated the database.

Home Assistant will work without the other settings but If you restart it your status won’t be correct. Usually default state is off so if it was on before the reboot then it will be off upon a restart.

No problem for a switch with pulse time that goes off anyway, but a problem for a sensor if it says your door is open when it’s actually closed.

What’s the purpose of hiding the SSID? If it’s for security it’s utterly meaningless.
Click to expand...
Was hiding SSID as it was the quickest way to break the connection so as to test the SV.
Will check your links. Thanks
 
calypso said:
Was hiding SSID as it was the quickest way to break the connection so as to test the SV.
Will check your links. Thanks
Click to expand...

That shouldn’t do anything to the connection.

It’s already associated and talking to the AP using the BSSID regardless.

Unless you meant hiding to mean turning it off.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X