YAML works out that anything starting with a number is a number, otherwise it must be a string - thus 40 ends up as a number but a40 ends up as a string, and hence YAML does not need quotes around strings (unless you actually want 40 to be a string)
That’s got it!
The array was the silly thing I’d missed.
I ran the demo code through the YAML to JSON converter and that showed where should have gone.
Thank you!
A different error, but I’m really struggling to make OpenEpaperLink work in Node-RED.
Example calls that I make via HA’s Developer Tools / Services work just as expected. But I’m getting some kind of strange error when using the same data and Call Service in Node-RED.
Looking into HA log files, it looks like the entity_id for the target tag is getting truncated somehow to only the first character. The same thing happens even when I externally populate the required fields in a function node and send that message to the Call Service node instead.
@skywise - would you be able to post a screenshot of how you populated the Call Service node for your project? I just want to make sure I’m not missing something obvious.
For entities, the target tag needs to be specified (something like “open_epaper_link.0000021f7dd43b16”). But you also need to specify a mystery entity that’s actually the AP display itself (similar format as the target tag).
I have no why it works this way in Node-RED. The AP display does not need to be specified in HA when using the Developer Tools / Services form. But it does in Node-RED. Like I said, really weird.