I haven’t tried this yet, it’s on my to-do list, but if I’m reading the docs correctly, you don’t specify the args like that, you would use the args in your logic for the action:
I read that bit to mean that’s what HA receives from the telegram_bot, sort of like a JSON packet, then we can use the command as a trigger, but the other bits we have to use elsewhere. I may be wrong, but that’s how I understood it.
I feel bad about the lost time @masterkenobi, you’re right about the doc. I’ll try to fix it.
If you’re using the telegram_bot to trigger a lot of commands, I suggest you to use AppDaemon: you can make much more with much less code, but in python instead of yaml. Also, if you use inline_keyboards (which send a telegram_callback instead of a telegram_command), you can append buttons to messages to send commands with a press (I love it), like:
I do generic service calls, show HA logs, run shell commands, create or cancel timers… In most cases, the telegram_bot is my #1 interface for HA. If you need an example of a bot handled with an AppDaemon app, a simple example is included here, and here is my bot handler. Mine is a bit messed up (and the app also handles iOS notification actions and more), but there are a lot of examples there.
Nice idea with adding user_id to the event_data trigger. I tried adding two user ids if the following formats to indicate it can be any of the two users but it did not work. Any suggestions?