Skip to content
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

[BUG] Deprecated option used in mqtt publish action call #784

Open
acolod opened this issue Aug 5, 2024 · 5 comments
Open

[BUG] Deprecated option used in mqtt publish action call #784

acolod opened this issue Aug 5, 2024 · 5 comments

Comments

@acolod
Copy link

acolod commented Aug 5, 2024

Describe the bug
Updated HA and integrations, now receiving this warning:

Deprecated option used in mqtt publish action call
This stops working in version 2025.2.0. Please address before upgrading.
Deprecated payload_template option used in MQTT publish action call to topic layzspa/command from payload template {"CMD":15,"VALUE":27, "XTIME":0, "INTERVAL":0}. Use the payload option instead. In automations templates are supported natively. Update the automation or script to use the payload option instead and restart Home Assistant to fix this issue.

Warning - 8/3/2024

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

Screenshots
2024-08-05 11_30_23-Settings – Home Assistant

Hardware (please complete the following information):

  • S100105
  • 6 Wire
  • D1 Mini

Software (please complete the following information):

  • V4.4.5
@visualapproach
Copy link
Owner

I don't see anything about this in the docs. Thanks for reporting.

@n3xus1
Copy link

n3xus1 commented Aug 8, 2024

I also received this warning today after updating to the latest core version of home assistant 2024.8.0

@Skeletorjus
Copy link
Contributor

Just replace payload_template: with payload: in your automations/script to remove the warning.

@PaleFlyer
Copy link

Just replace payload_template: with payload: in your automations/script to remove the warning.

I tried that for when I push my local Tempest temperature into the ESP, and it had worse alarms.

@jamesonuk
Copy link
Contributor

Thank you for saving my sanity....
I had put this down to what was being published to MQTT but obviously (and had I read the actual warning) it is what I am sending to MQTT. It is setting the ambient temperature.

The docs on page 24 just need to be amended from payload_template to payload but not a bug in the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants