FYI, I have created a Node-RED contrib library to allow direct integration with Homey from within Node-RED flows.
It uses the standard homey-api calls.
It currenty supports:
see node-red-homey (node) - Node-RED for more info
Ooh, that’s great stuff. I already gave up on this ever happening.
I’ll give this a try tonight, thank you!
Seems to be working great, maybe in a future version you can include a dropdown list with the different capabilities?
And while on that subject, do you know how to get the data from a dummy “advanced capabilities” device? I thought measure_temperature would work but it does not…
Maybe if possible a new node that shows the capabilites of the selected device (not sure if thats possible though)
-=edit=-
Using the “homey-device-listen” seems to work but can be tricky since it only triggers if there is a change. The advanced capabilities device i’m looking for had the following ID : measure_devicecapabilities_number-custom_26.number1
FYI, an easy way to find the exact capability id’s for a device is via the devices on the homey developer site.
https://tools.developer.homey.app/tools/devices
Awesome, thanks!
Thank you for the development of the Homey integration — I really appreciate it. Could you please let me know whether any broader documentation is available, and if so, where I can find the logs? I’m having trouble using a node: I end up with an error saying the device cannot be found, and I’m using a local connection and the local API.
Hi,
you should use the device name instead of the id.
Thank you for the quick response! Using the device name instead of the ID works perfectly. That was my mistake — I should have tried that right away.
