custom_buttons not working, missing 'data'
See original GitHub issueWhen adding a custom button as follows:
type: custom:valetudo-map-card
entity: camera.map_data
vacuum_entity: vacuum.valetudo
custom_buttons:
- service: mqtt.publish
- service_data:
topic: /valetudo/robot/GoToLocationCapability/go/set
payload: ae0ccd4b-b077-4a94-8c54-511441da18aa
I get the error:
Failed to call service mqtt/publish. required key not provided @ data['topic']
I also tried data
instead of service_data
am I doing something wrong?
Also it doesn’t matter what kind of icon I use it will always use: mdi:radiobox-blank
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
CustomButton in Full Calendar is not displayed - Stack Overflow
I am having a problem in FullCalendar, I ...
Read more >Custom Buttons not showing in Lightning but shows up in ...
I recently hid a custom button from Lightning and enabled it back again in the page layouts. But it does not show in...
Read more >Custom buttons not showing — DataTables forums
I'm keen to ditch my non-datatables buttons and use yours instead. I'm using the cdn with javascript: buttons and buttons.print.
Read more >Custom buttons not working? : r/twinegames - Reddit
I'm trying to make a simple rpg where you can create your character. I was able to get it to work with the...
Read more >Custom buttons in ArcGIS Hub pages no longer working
Solved: Hi, We have created custom collapsible buttons within a text card on several hub pages. They were working fine until today, so...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You’re probably best of waiting for or helping with #108.
Works fine for me: