asbril Posted May 18, 2022 Posted May 18, 2022 As mentioned before, I have a large Zwave setup (some 80 Zwave devices) and I am waiting for the migration tool to move the whole stup to ISY on Polisy. However I already manually moved some 12 devices. As such my home is divided in 2 separate ISY's. In a few instances I'd like one to "communicate" with the other. I resolved this by installing the Kasa Node server on both and use Kasa plugs. If the status changes of one of these plugs then this is also reflected on the other ISY and this can then be used in programs. I was wondering whether there was another, more logical solution. I noticed the Virtual Node server and hoped that this could be used creating virtual nodes, but I saw that this Node server serves another purpose. Does anyone has an idea or suggestion ?
lilyoyo1 Posted May 18, 2022 Posted May 18, 2022 28 minutes ago, asbril said: As mentioned before, I have a large Zwave setup (some 80 Zwave devices) and I am waiting for the migration tool to move the whole stup to ISY on Polisy. However I already manually moved some 12 devices. As such my home is divided in 2 separate ISY's. In a few instances I'd like one to "communicate" with the other. I resolved this by installing the Kasa Node server on both and use Kasa plugs. If the status changes of one of these plugs then this is also reflected on the other ISY and this can then be used in programs. I was wondering whether there was another, more logical solution. I noticed the Virtual Node server and hoped that this could be used creating virtual nodes, but I saw that this Node server serves another purpose. Does anyone has an idea or suggestion ? To keep things from getting complicated, I split my system up with devices that work together that way my zwave routing was minimally effected. With you having the amount of devices that you have, the likelihood of poor routing killing either unit is small
asbril Posted May 18, 2022 Author Posted May 18, 2022 1 hour ago, lilyoyo1 said: To keep things from getting complicated, I split my system up with devices that work together that way my zwave routing was minimally effected. With you having the amount of devices that you have, the likelihood of poor routing killing either unit is small Thanks @lilyoyo1 but my question is how can I have a program in ISY whereby light X goes ON when sensor Y is activated in ISY on Polisy. As mentioned I have this working using the Kasa Node server on both, but I wonder whether there is a better /cleaner solution.
lilyoyo1 Posted May 18, 2022 Posted May 18, 2022 7 minutes ago, asbril said: Thanks @lilyoyo1 but my question is how can I have a program in ISY whereby light X goes ON when sensor Y is activated in ISY on Polisy. As mentioned I have this working using the Kasa Node server on both, but I wonder whether there is a better /cleaner solution. With your zwave devices, there really isn't a clean way that i know of since both devices are already set up. You may be able to with network resources but i don't know how I would make that work. That's why I was saying it may be better to split things according to what works with each other. 1
asbril Posted May 18, 2022 Author Posted May 18, 2022 18 minutes ago, lilyoyo1 said: With your zwave devices, there really isn't a clean way that i know of since both devices are already set up. You may be able to with network resources but i don't know how I would make that work. That's why I was saying it may be better to split things according to what works with each other. For the time being I have split the devices by rooms and moved 2 rooms to IoP. My query is really "philosophical" as I have it working with Kasa. Eventually I will have everything on IoP. I have seen others on this forum that have ISY's set up in different homes (lake house...) and I was wondering whether they had those ISY's "talking" to eachother. As said, it was mostly intellectual curiosity.
larryllix Posted May 18, 2022 Posted May 18, 2022 (edited) Since I run most of my lighting groups off state variable triggers it became an easy task to clone those variables on IoP. When a variable changed value, instead of a program triggering on ISY, a program ran a NR that used the IoP's REST interface and cloned that value in a duplicate State variable on my IoP. On IoP all my programs were cloned and the same thing happened over there, instead of ISY. ISY's programs that responded to that same variable inside ISY, had to be disabled so that I didn't get duplicate commands going out. When I had problems with my IoP upgrade I just unplugged my IoP and enabled the lighting programs again on my ISY and I was back in 20 minutes. Yes it takes a bank of programs and variables for each scene or lighting control but they just get hidden in a folder that I never see again. It just works on it's own. Inside ISY you would never even know anything has changed. Fan speeds do exactly the same thing as well as colour variables for RGBCW bulbs and strips. One variable controls dozens of scenes containing different colours and brightness levels in each case. Edited May 18, 2022 by larryllix
sjenkins Posted June 5, 2022 Posted June 5, 2022 @larryllix's version is pretty respectable as a hard core all-in-isy version. As an alternative I have been using MQTT for a while with the ISY MQTT node server. Mostly for my homemade IOT sensors well before the cheap off the shelf versions available now. In your application you could have a very simple program which updated an MQTT node off a sensor. This is sent to a common MQTT server (I run off an extra rPI3). Then on the other ISY or IOP you could have the mirror node and fire your program based on that. This allows easy two way communications if you have sensors on either unit. Its been pretty solid for me now for a few years. Hope this helps @asbril 1
asbril Posted June 5, 2022 Author Posted June 5, 2022 42 minutes ago, sjenkins said: @larryllix's version is pretty respectable as a hard core all-in-isy version. As an alternative I have been using MQTT for a while with the ISY MQTT node server. Mostly for my homemade IOT sensors well before the cheap off the shelf versions available now. In your application you could have a very simple program which updated an MQTT node off a sensor. This is sent to a common MQTT server (I run off an extra rPI3). Then on the other ISY or IOP you could have the mirror node and fire your program based on that. This allows easy two way communications if you have sensors on either unit. Its been pretty solid for me now for a few years. Hope this helps @asbril Many thanks for your suggestion. I am not familiar with MQTT, but I think that your solution is not that different from what I do with Kasa switches which, while not "elegant" does do the job. The new board/dongle is expected by September and Michel mentioned that there is a 90% chance that there will be an easy migration from the 500 board to the new Zwave/Matter board. Then I can migrate everything to IoP.
Recommended Posts