Added StatusRetain command

[jeroenst]

Description:

Added statusretain #11067

Checklist:

• The pull request is done against the latest development branch
• Only relevant files were touched
• Only one feature/fix was added per PR and the code change compiles without warnings
• The code change is tested and works on Tasmota core ESP8266 V.2.7.4.9
• The code change is tested and works on Tasmota core ESP32 V.1.0.5-rc6
• I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

[ascillato]

Hi, your change to the release notes is conflicting with the actual codebase. Please, delete it.

[jeroenst]

I changed the conflicting release notes instead, is that ok?

[arendst]

On hold for now as these "retain" changes are just marginal requests while I was able to keep Tasmota away of the HASS policy for many years. It adds code not used by any decent user except the famous MQTT retain afficionados...

I also wonder if the retain stop code works for all status messages.

[jeroenst]

Retain stop works for all messages, retain stop is applied juist before sending to mqtt broker.

[jeroenst]

I would like to see this option to be merged so I can display status info on my dashboard.

There is no way at this moment to send status 0 retrained.

[Jason2866]

Why using "retain" in general? Just query the devices and you get the actual real state.
I do not see any need for retain functions for Tasmota. Any status can be "asked"
A example https://tasmota.github.io/docs/Home-Assistant/#useful-automations
IMHO retain does generate more problems than it maybe solves

[jeroenst]

1. Because it generates less traffic. When there are many clients (my dashboard in javascript i.e.) connecting and leaving the mqtt server it generates a huge amount of traffic which is prevented by retaining the messages
2. Because just subscribing to the topic is enough to get the data, otherwise every client who is interested has first to send an additional request to get the data. In nodered this means additional nodes to be configured.

[jziolkowski]

And what's wrong with having a lot of MQTT traffic? It was designed exactly for that.

[Jason2866]

@jeroenst The beauty of open source. You have made the changes you want/like.
As the project owner already wrote he does not like adding code for this.

[jeroenst]

@jeroenst The beauty of open source. You have made the changes you want/like.
As the project owner already wrote he does not like adding code for this.

I can do that but than I need to merge it over and over with upstream development branch. And I think this would be a good thing if it's added.

At this moment I use my own firmware, but if Tasmota is a good alternative for me I'm willing to make effort in developing Tasmota instead of my own project.

[github-actions]

This PR has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This PR was automatically closed because of being stale.

[jeroenst]

@arendst any chance this can be implemented?

Again I try to make a status page, but again I bump into non retained messages of the tasmota, forcing me to create a kind of retain bridge which is not very nice and clean...

[jeroenst]

@arendst the status was changed to on-hold a while ago. What can I do to get this change into the main branch?

[jeroenst]

Statusretain is working correctly in 12.1.1.2 development branch commit e3c7733

I tested with shelly 1, shelly dimmer 2, shelly 2.5, sonoff zbridge, athom power plug and Athom RGBWW bulb.

Everything seems to work fine. Thank you @arendst

This status page is created by: https://github.com/jeroenst/espweb/