Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Fire trigger on Tasmesh broker when a node disconnects #20369

Closed
5 of 14 tasks
pipe01 opened this issue Jan 2, 2024 · 0 comments · Fixed by #20392
Closed
5 of 14 tasks

Fire trigger on Tasmesh broker when a node disconnects #20369

pipe01 opened this issue Jan 2, 2024 · 0 comments · Fixed by #20392

Comments

@pipe01
Copy link
Contributor

pipe01 commented Jan 2, 2024

PROBLEM DESCRIPTION

When using Tasmesh, nodes won't send any MQTT Online or Offline messages, meaning that tools like Home Assistant won't be able to use these nodes as they will permanently appear offline. Sending the Online message is easy enough through the use of a rule on the node, e.g. ON system#init DO Backlog MeshNode 00:11:22:33:44:55; Publish tele/tasmota_XXXXX/LWT Online ENDON, however sending the Offline message is currently impossible: the node won't be able to send it as it's now powered off, and the broker never realizes that the node is gone and doesn't fire any triggers.

The best solution would be to somehow implement LWT messages on the broker, but in the meantime a nice workaround would be for the broker to detect when a node has gone offline and print a message which can then be used as a trigger to run a Publish command with the LWT Offline message.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

  • Read the Contributing Guide and Policy and the Code of Conduct
  • Searched the problem in issues
  • Searched the problem in discussions. Related discussions: #
  • Searched the problem in the docs
  • Searched the problem in the chat
  • Device used (e.g., Sonoff Basic): _____
  • Tasmota binary firmware version number used: _____
    • Pre-compiled
    • Self-compiled
  • Flashing tools used: _____
  • Provide the output of command: Backlog Template; Module; GPIO 255:
  Configuration output here:

  • If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:
  Rules output here:

  • Provide the output of this command: Status 0:
  STATUS 0 output here:

  • Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:
  Console output here:

TO REPRODUCE

Steps to reproduce the behavior:

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

Repository owner locked and limited conversation to collaborators Jan 2, 2024
@Jason2866 Jason2866 converted this issue into discussion #20375 Jan 2, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant