On Windows, Windows Remote Shell IS the simple approach. Windows does not support ssh the way Linux/Unix does out of the box. I don’t know much about psexec but it looks promising.
There is nothing built into Windows though that lets you easily remotely issue commands on a remote Windows unless there is some capability in PowerShell I don’t know about.
Seems a bit complex. You can connect them directly with each other using the MQTT Event Bus and cut out the need for a third service to connect the two. You have to use MQTT anyway to connect to NodeRed unless I’m mistaken so why not cut out the middle man?
Hi, Rich, you can use OH directly with the OH2 nodes:
It uses the Rest API. Only problem with these is that as Node-Red starts much faster than OH on reboot, it will generate errors on the OH logs before the items are defined as the rest API start before.
I have tried to get rid of it by delaying node-red start (I haven’t found a solution) OR delaying the rest api start (Not looked for it yet)
what is this MQTT event bus?
can you please show me an example if you have such? for two windows PC?
I looked at docs but I am kind of a noob, there is not allot to go by
You set up an MQTT broker, which is what would be required for NodeRed, though maybe not given Vincent’s response above. Then you use the instructions and that link to set up the event bus. Then set up items with the same name in both oh instances and the event bus will keep them in sync.
If you are referring to sensorReporter, I suggest you go to the GitHub page and read the README and look at the code. How it works is it runs as a service that you can send messages to over MQTT or receive messages over MQTT and do something in response.