I’m trying to get a pico to work with my fireplace.
I have other picos working with lights in my kitchen with no problem.
I do it all in node-red.
I can’t seem to get the correct button name in node-red.
It won’t show up on it’s own. (in autocomplete)
I am able to find that the button events are received when I do a debug on all events:
I now see that the PICO shows up as a device and not an entitiy. I was able to make an Automation with that in Configuration. However, I would prefer everything to be in Node-red so that I can configure it there.
I have found that this blueprint to set up buttons but it does work either.
This blueprint and the one from me listed by @biver is for the Lutron Core Integration that was recently released. What Lutron Integration are you using? If you are not sure how to tell, then bring up one of your Pico’s. It will be under Devices or Entities depending on the integration you are using…let us know which you see…and also what is says exactly under the Integration column. A screenshot would be helpful.
I no longer use Node Red but you should be able to use the All Events node (or something similarly names) and listen for the event type lutron_caseta_button_event.
That should output all the lutron button events and you can then extract what you need. Below is an example of the event generated by a pico button press. Should be pretty simple to get what you need if you are comfortable in NR.
Yes, unfortunately the core integration does not expose the Pico remotes as entities. I believe there is a feature request for that, but in the meantime we can only add them to automations by listening for the events.
As I mentioned I no longer use NR so it would be difficult to assist. Hopefully the OP is comfortable in NR and can use what I’ve provided and can help direct you.
Curious…Why are you trying to integrate the Pico in NR if you aren’t comfortable using it? Why not just use HA and the many blueprints that have already been created for you?
Honestly, I’m just trying to learn Node Red by trying to duplicate all the automations I already have working in HA. I figured it was good way to learn to see what it’s good for and not so good for… Guess I’m finding out!
Yeah, NR is pretty awesome once you get the hang of it. I try to keep everything native where possible, but outside of that preference, NR is my favorite automation platform. Very powerful with added visual benefit.
The guy who made that crazy one on that link, uses the sensor.pico_x… but since the way I have it now, using your blueprint, I can’t refer to them like that, so I’m just lost. I know you can’t help… @jeffnielson ?