You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a "LastMessageText was updated to /something" rule, the script should be able to run something like sendTelegram(Long::parseLong(TelegramBot_ChatId.state.toString), …) and that should send the message to the chat where the command came from.
CHATID and REPLYID should be updated first with LASTMESSAGETEXT being second last, and LASTMESSAGEDATE being the very last. Reasoning is that the LASTMESSAGETEXT may be the same for multiple messages in a row (?) and some people may trigger rules based off when LASTMESSAGEDATE changes.
How does that sound as I am not yet sending two way messages on my system.
Expected Behavior
In a "LastMessageText was updated to /something" rule, the script should be able to run something like
sendTelegram(Long::parseLong(TelegramBot_ChatId.state.toString), …)
and that should send the message to the chat where the command came from.Current Behavior
ChatId is updated after LastMessageText:
openhab-addons/bundles/org.openhab.binding.telegram/src/main/java/org/openhab/binding/telegram/internal/TelegramHandler.java
Lines 327 to 340 in 487dc0e
So when the last chat changes, one message goes to the wrong chat.
Possible Solution
Reorder these lines of code?
The text was updated successfully, but these errors were encountered: