I don't use HASS.io so I'm not sure how it differs. But any config change you need to restart HA, and any time there is a config change in HA you'll need to restart NR to see the changes.Finally got around to installing Node-RED on my HASS and spent a while spinning my wheels. Turns out often you need to ssh in to issue a "hassio homeassistant restart" for it to actually properly restart.
Do you have any real Hue stuff? I found this custom component that allows you to create automations using the Hue remote to trigger events - they report as a sensor and you trigger based on the state change of things like "1_click_up" for "On".
Ahh yes I see. Can you give me a very simple automation example (which are the 8 states, I guess each button short and long press, so 4x2=8 states, yes?) Like this? - alias: 'Long Press ON Corridor switch' trigger: - platform: state entity_id: sensor.corridor_switch...community.home-assistant.io
I managed to tie in SmartThings and Hue into my HASS and finally have "full" usage of the motion sensors and remotes on each system.
I've created a samba share of my HA folder. So I can edit all the configs w/ Notepad++. Then I've setup HA so I can reset my services through the UI easily.
An easy way to do this, is to create command line switches in HA. You can even control other machines over ssh if you setup ssh keys between the two machines. The command line switches are ugly in the UI tho, so I setup input booleans to use instead. The input booleans are just so I can toggle the automation in nodered, but through the HA UI.
Never used Hass.io so I'm not sure how easy it is to just restart the docker containers. So maybe all this isn't helpful.
And I use a few Hue's where I couldn't install my own switches, strips. Don't use a remote tho. I control everything w/ either complete automation or voice. So the default integration works fine.