node-red-contrib-telegrambot-home icon indicating copy to clipboard operation
node-red-contrib-telegrambot-home copied to clipboard

0.8.0 - Switch reply does not work anymore

Open Boss-man opened this issue 1 year ago • 2 comments

After upgrading from 0.7.2 to 0.8.0 the switch node does not receive replys. I get the message on my phone with the buttons to answer. But nothing happens when I press the buttons and the switch nodes eventually times out.

To fix it, I changed the two switch files - switch.html and switch.js - out with the files from the 0.7.2 version, and all is working again. So basically a downgrade to 0.7.2

Boss-man avatar Nov 02 '23 08:11 Boss-man

Hello, Maybe a mix of #39 and this one. I figured out that the switch reply is:

  • working properly when the chat.id field is fulfilled
  • not working when the chat.id field is empty as using the msg.telegram.chat.id Is it normal ? Any way to make it work with msg.telegram.chat.id ? I hope my message is clear enough, thank you.

Vagabon666 avatar May 04 '24 22:05 Vagabon666

Hello, Maybe a mix of #39 and this one. I figured out that the switch reply is:

  • working properly when the chat.id field is fulfilled
  • not working when the chat.id field is empty as using the msg.telegram.chat.id Is it normal ? Any way to make it work with msg.telegram.chat.id ? I hope my message is clear enough, thank you.

Hello, Sorry, I figured out that "msg.telegram.chat.id" isn't working because the switch is waiting for number value. As I was trying to send message to several chatID in the same time (e.g : xxxxxxx, yyyyyyy), I assume it is the reason why it failed. I found a workaround by using a group chatID, but it is not the same user experience. Is there any chance that the switch could allow several chatID ? Thank you.

Vagabon666 avatar May 05 '24 13:05 Vagabon666