-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe have a option to rename /TELEMETRY? Or option to rebroadcast /POWER during TELEPERIOD #10
Labels
enhancement
Type - Enhancement that will be worked on
Comments
See #15 |
ascillato
added a commit
that referenced
this issue
Jun 5, 2018
Update Tasmota to v5.12.0g - Add hardware serial mqtt bridge
arendst
pushed a commit
that referenced
this issue
Oct 6, 2019
s-hadinger
added a commit
to s-hadinger/Tasmota
that referenced
this issue
Jul 5, 2021
mepunit
added a commit
to shivankittech/smart-home-base-firmware
that referenced
this issue
Aug 19, 2021
s-hadinger
added a commit
that referenced
this issue
Sep 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently I had TELEMETRY topic rename to RESULT, reason being is that my current program are coded in such a way that I use the same topic name for both feedback and periodically cross checking the status.
We could do that previously with Legacy Mode MessageFormat as the topic are rebroadcasted as /POWER. Would be nice if we have some options available so that people who uses the TELEMETRY the same way as me can have a easier time porting from MQTT-Arduino to Tasmota.
Alternatively, we can just abuse the single level wildcard of MQTT on the application side, but it might not be ideal for busy environment with many devices pumping to the same topic.
The text was updated successfully, but these errors were encountered: