Originally posted by ksum
View Post
It's as simple as running (events) in Node-RED from HomeSeer but the the other way around of running events in HomeSeer.
- The HASS event all node does this but I don't use HASS
- When you have seen what the ioBroker has is even evil! so to put it
So you can see here am using MQTT and the one down is ioBroker's
You have the systems cross communicating without MQTT. Say you have the physical devices in HomeSeer example the motion sensors which if a HomeSeer event node is available all you do is you pick the sensor from the devices HomeSeer is sending and add a switch node and change nodes and to whatever. Those plugins which are failing to work in HS4 or don't have altogether.
No event creating in HomeSeer but it is the device status doing the talking.
As much as I want to I can't for the life of me get the MeiUniFi, UltraHSPIPioneer and Doorbird plugins to work in HS4. But being able to run other systems along side HomeSeer, it's like all is fine this end.
You have seen people complaining that Node-RED hangs from time to time but I have this bad feeling that it's MQTT causing it (there is simply too much traffic - I can hold my judgement on that one)
I can create as another example a Media remote with HStouch and you know that option of " Run a HomeSeer event" have play, pause, stop .....etc control a bunch of players without duplicating them but link them and provided you are not running them at the same time (I have already setup a players virtual device based on what's playing the Amp is switched accordingly) you have no conflicts. So I don't have to use the MQTT but the HomeSeer Event In Node.
Eman.
Comment