The `target` parameter for Telegram Bot is being removed -- template issue?

[mmiller7 (Matt Miller)]

Just updated and now have some warnings that the suggested repairs don’t work for…not sure how to “fix” it.

I thought I’d got thru all these but apparently previously I had only done ones where the target was using a ‘notify’ and not dynamic.

The problem is I have no “notify.something” to change it to - I am replying dynamically to the user who sent the message. I really hope I don’t now have to do separate automations for every possible user???

  - alias: 'Telegram bot that reply pong to Sensor Low Battery Alerts'
    trigger:
      - platform: event
        event_type: telegram_command
        event_data:
          command: '/check_low_sensor_battery'
    action:
      - service: telegram_bot.send_message
        data_template:
          target: '{{ trigger.event.data.user_id }}'
          message: |
            Check blah

I’m further confused it somehow only complains about 2 of the numerous automations I have that follow this same pattern…for example this one it seems to think is fine:

  # On Demand Status

  - alias: 'Telegram Network Status Query'
    trigger:
      - platform: event
        event_type: telegram_command
        event_data:
          command: '/netstat'
    action:
      - service: telegram_bot.send_message
        data_template:
          target: '{{ trigger.event.data.user_id }}'
          message: |
            Network Status:

[tom_l]

Change this:

  - alias: 'Telegram bot that reply pong to Sensor Low Battery Alerts'
    trigger:
      - platform: event
        event_type: telegram_command
        event_data:
          command: '/check_low_sensor_battery'
    action:
      - service: telegram_bot.send_message
        data_template:
          target: '{{ trigger.event.data.user_id }}'
          message: |
            Check blah

To this:

  - alias: 'Telegram bot that reply pong to Sensor Low Battery Alerts'
    triggers: # changed
      - trigger: event  # changed
        event_type: telegram_command
        event_data:
          command: '/check_low_sensor_battery'
    actions:  # changed
      - action: telegram_bot.send_message  # changed
        data:  # changed
          chat_id: '{{ trigger.event.data.user_id }}'  # changed
          message: |
            Check blah

The repair is only about the target part but I also corrected some other legacy format you are using. e.g. data_template has not been used since forever.

[duceduc]

Trying to fix this but I still get the warning popup even after fixing it.

I did a search for telegram_bot.send_message in my config folder and only one search comes up. Changed from target: to chat_id. Restarted HA, but the warning still pops up.

Any suggestions on how to further refine the search? What other search perimeters should I be targeting?

update: so I think the issue is that I still have the old telegram bot integration as suggested here.

Telegram bot changes - Target parameter removed

Nevermind, I fixed myself…the issue is that this is deprecated: notify: - platform: telegram name: "myname" chat_id: 123456789 You need to set up telegram bot integration, first add service (API) key and next add allowed chat id. Next: remove the whole deprecated notify section in your configuration.yaml - next: you need to adjust every automation using the notify function! You now need to use the Notifications: Send a notification message action from now. The target is your added te…

I see the new telegram bot has been added. Do I just comment out these old lines and nothing else?? My existing automation should use the new telegram bot integration???

  - name: amberthebot
    platform: telegram
    chat_id: !secret telegram_chatid

[tom_l]

@duceduc

I did a search for telegram_bot.send_message

This repair is also coming up if you are using the old method anywhere too.

Don’t forget to check Alarmo notifications if you use it.

[duceduc]

ok. I think I have idea of what I need to do. Has this been address with a fix to migrate over the new telegram bot integration??

.
.
.
  actions:
    - choose:
        - conditions:
            - condition: trigger
              id: mail
          sequence:
            - action: notify.amberthebot 
              data:
                message: "You've got mail!"
                data:
                  inline_keyboard:
                  - 'Received:/received, Mute:/donothing' 

[Caswell1000]

hI @tom_l , any idea why this still results in the persistent notification about target

    - action: notify.home_telegram

      data:
        title: '*Garage Presence*'
        message: Triggered due to presence

[tom_l]

That is the depreciated format. Use the new format.

    - action: telegram_bot.send_message
      data:
        chat_id: # your chat id here
        title: '*Garage Presence*'
        message: Triggered due to presence

[Caswell1000]

Thank you, I have changed it to the code below, it works:

 - action: telegram_bot.send_message

    data:
      chat_id: !secret casabot_chatid
      title: '*Garage Warning*'
      message: Garage just opened

[Caswell1000]

Hi @tom_l , I have a new bot but with the same chatID as the usual bot I use, but it does not send messages , when I comment out api_key: !secret snifferzbot_api it works but send to the old bot, when it is not commented out, I get no messages, what am I doing wrong?

actions:
    - repeat:
        while:
          - condition: state
            entity_id: device_tracker.galaxy_s24_ultra
            state: "not_home"
        sequence:    
          - action: telegram_bot.send_message

            data:
              chat_id: !secret casabot_chatid
              api_key: !secret snifferzbot_api
              title: '*TwoHourAlertPops*'
              message: This is a two hour check-in alert pops
          - delay: 
              minutes: 1

thanks for your assistance, the previous changes removed the warning and work perfectly.