cosyn

That worked! Thanks so much. I wouldn't have figured that out from the Tasmota command list. And thanks for taking over developing this NS from xKing! It's really a boon after many Insteon-based manufacturers have fallen.

I'm new to MQTT. I have a Sonoff 4CH Pro (4 relays) that I have been controlling using the eISY network resources. Time to grow up and transition over to using MQTT as I swap out hardware that is no longer manufactured. Following xKing and @TriLife's instructions on various threads, I was able to set up eisy's Mosquitto as broker and a .yadl file to define the device. Wasn't sure whether I should create one device and somehow the broker would let MQTT know there are 4 devices, or if I should create 4 devices. I tried it both ways and am stuck with only one controllable relay of the 4. In the Sonoff Tasmota web interface, it shows a few topics I've tried using (tasmota_%6X, tasmotas, and tasmotas_725533). Only tasmotas_725533 produces a node that allows me to send on/off commands, and only to the 1st channel/relay in the 4CH Pro. Here's the device list in my .yaml file below. I'm guessing I need a different topic path for each channel but can't figure out how to find them. I searched through the Tasmota documentation for this device and various forums but didn't turn anything up. devices: - id: "SO1_DesVenOpen" name: "Sonoff4CH1_DesVent_open" type: "switch" status_topic: "stat/tasmota_725533/POWER" cmd_topic: "cmnd/tasmota_725533/POWER" - id: "SO2_DesVenClos" name: "Sonoff4CH2_DesVent_close" type: "switch" status_topic: "stat/tasmota_725533/POWER" cmd_topic: "cmnd/tasmota_725533/POWER" - id: "SO3_LoRoofOpen" name: "Sonoff4CH3_LoRoof_open" type: "switch" status_topic: "stat/tasmota_725533/POWER" cmd_topic: "cmnd/tasmota_725533/POWER" - id: "SO4_LoRoofClos" name: "Sonoff4CH4_LoRoof_close" type: "switch" status_topic: "stat/tasmota_725533/POWER" cmd_topic: "cmnd/tasmota_725533/POWER" Any help is appreciated.

UD was able to help repair the problem, which appears to be due to a change in the node names. From Chris: "In your case, I just changed all ZWxxxxxx nodes to ZYxxxxxx, all n004_timedata to n04_controller". I'm waiting to hear from him what tool he used to change the XML code, as Notepad++ with the various XML plugins couldn't produce a file that I could readily view. And I'm still puzzled as to whether the underlying issue was on the timedata NS coding side or the eisy side. If anyone else has this issue, sending a note to the UD team will get it resolved the quickest.

Interesting idea, @EWhite. The program export from the 994i looks really different from how they look in eisy. See below. Lol, I'm no programmer but I don't think the two will import/export readily across platforms very readily. The 994i program doesn't seem to show the underlying editable code the way eisy does. Also, what program are people using to edit the eisy .iox program export files? I tried Notepad++ but it doesn't want to indent nicely even though the file seems to be xml. 994i: Sched-Highland Fan On High - [ID 01CA][Parent 008D][Not Enabled] If ( '_NodeServers / ISY Time Data' Minute is 0 minute Or '_NodeServers / ISY Time Data' Minute is 7 minute Or '_NodeServers / ISY Time Data' Minute is 15 minute Or '_NodeServers / ISY Time Data' Minute is 22 minute Or '_NodeServers / ISY Time Data' Minute is 30 minute Or '_NodeServers / ISY Time Data' Minute is 37 minute Or '_NodeServers / ISY Time Data' Minute is 45 minute Or '_NodeServers / ISY Time Data' Minute is 52 minute ) And 'Cons_1_Highland / Plugs / High_Plug_1.1_Top: Cooler' Status is Off And ( 'Cons_1_Highland / 1_Highland Thermostat' Temperature < 62.0° Or 'Cons_1_Highland / 1_Highland Thermostat' Humidity < 80% Or '_NodeServers / WeatherPoly / Temperatures' Temperature < 50.0°F Or 'Cons_2_Lowland / Plugs / Low_Plug_1.1_Top: AC' Status is On ) Then Run Program 'Response-Hi Fan On High' (Then Path) Else - No Actions - (To add one, press 'Action') eisy: </d2d><d2d><trigger><id>458</id><name>Sched-Highland Fan On High</name><parent>141</parent><if><and /><paren><or /><comment> Warning: Unrecognized Condition (program may not run)&#x0A;&lt;status OP=&quot;IS&quot; NODE=&quot;n004_timedata&quot; ID=&quot;GV1&quot;&gt; &#x0A; &lt;val UOM=&quot;44&quot; PREC=&quot;0&quot;&gt;0&lt;/val&gt; &#x0A;&lt;/status&gt; &#x0A;</comment><or /><comment> Warning: Unrecognized Condition (program may not run)&#x0A;&lt;status OP=&quot;IS&quot; NODE=&quot;n004_timedata&quot; ID=&quot;GV1&quot;&gt; &#x0A; &lt;val UOM=&quot;44&quot; PREC=&quot;0&quot;&gt;7&lt;/val&gt; &#x0A;&lt;/status&gt; &#x0A;</comment><or /><comment> Warning: Unrecognized Condition (program may not run)&#x0A;&lt;status OP=&quot;IS&quot; NODE=&quot;n004_timedata&quot; ID=&quot;GV1&quot;&gt; &#x0A; &lt;val UOM=&quot;44&quot; PREC=&quot;0&quot;&gt;15&lt;/val&gt; &#x0A;&lt;/status&gt; &#x0A;</comment><or /><comment> Warning: Unrecognized Condition (program may not run)&#x0A;&lt;status OP=&quot;IS&quot; NODE=&quot;n004_timedata&quot; ID=&quot;GV1&quot;&gt; &#x0A; &lt;val UOM=&quot;44&quot; PREC=&quot;0&quot;&gt;22&lt;/val&gt; &#x0A;&lt;/status&gt; &#x0A;</comment><or /><comment> Warning: Unrecognized Condition (program may not run)&#x0A;&lt;status OP=&quot;IS&quot; NODE=&quot;n004_timedata&quot; ID=&quot;GV1&quot;&gt; &#x0A; &lt;val UOM=&quot;44&quot; PREC=&quot;0&quot;&gt;30&lt;/val&gt; &#x0A;&lt;/status&gt; &#x0A;</comment><or /><comment> Warning: Unrecognized Condition (program may not run)&#x0A;&lt;status OP=&quot;IS&quot; NODE=&quot;n004_timedata&quot; ID=&quot;GV1&quot;&gt; &#x0A; &lt;val UOM=&quot;44&quot; PREC=&quot;0&quot;&gt;37&lt;/val&gt; &#x0A;&lt;/status&gt; &#x0A;</comment><or /><comment> Warning: Unrecognized Condition (program may not run)&#x0A;&lt;status OP=&quot;IS&quot; NODE=&quot;n004_timedata&quot; ID=&quot;GV1&quot;&gt; &#x0A; &lt;val UOM=&quot;44&quot; PREC=&quot;0&quot;&gt;45&lt;/val&gt; &#x0A;&lt;/status&gt; &#x0A;</comment><or /><comment> Warning: Unrecognized Condition (program may not run)&#x0A;&lt;status OP=&quot;IS&quot; NODE=&quot;n004_timedata&quot; ID=&quot;GV1&quot;&gt; &#x0A; &lt;val UOM=&quot;44&quot; PREC=&quot;0&quot;&gt;52&lt;/val&gt; &#x0A;&lt;/status&gt; &#x0A;</comment></paren><and /><status id="ST" node="38 F3 AA 1" op="IS"><val uom="51" prec="0">0</val></status><and /><paren><or /><status id="ST" node="2C 45 C7 1" op="LT"><val uom="14" prec="1">620</val></status><or /><status id="CLIHUM" node="2C 45 C7 1" op="LT"><val uom="51" prec="0">80</val></status><or /><status id="ST" node="n006_temperature" op="LT"><val uom="17" prec="1">500</val></status><or /><status id="ST" node="34 68 1F 1" op="IS"><val uom="51" prec="0">100</val></status></paren></if><then><runthen>268</runthen></then><else></else><comment></comment></trigger></d2d>

No worries. As far as I'm aware the eisy interface in admin console only allows programming through the GUI. Hoping @glarsen who wrote the nodeserver can chime in based on the screenshots provided above as it does seem that there is a difference in the PG2 and PG3x variable names as @tlightne pointed out. I have a ticket open with @Michel Kohanim so am drawing his attention to this thread.

Thanks for the tip, @tlightne. Sounds like I would need to change all of the eisy programs. How would you recommend changing the scripts apart from doing it one program at a time?

Happy new year, and thanks for the response, @glarsen. Here you can see screenshots of the old mapping under PG2 and the current mapping under PG3x. Not sure if it helps but also adding a screenshot of the timedata NS tab. PG2 PG3x PG3x timedata NS tab

Happy new year, Bob. I noticed after a reboot, the nodes are now seen by the eisy programs. So all is good with this nodeserver. Thank you!

I finally got around to installing and migrating to eisy/PG3x from my 994i and polisy (PG2). I had restored PG2 to PG3 on the polisy and attempted to migrate from PG3 to PG3x in eisy but received errors and instructions to install all of the NS's manually, so I did that. I installed them into the same slot numbers as before. There are two issues I'm experiencing: 1. Data is sent from CumulusMX to PG3x. The PG3x weatherpoly NS in eisy shows as online. The humidity and temperature show up correctly in eisy. I mapped incoming data to NS keys as shown. However, several nodes (illumination, wind, precipitation) display the humidity or temperature instead of the corresponding data. In the PG3x Nodes tab, I see that all of them have data matching CumulusMX except for illumination. [edit: figured this one out. "Fixed it" by closing and reopening admin console] 2. I have hundreds of programs with weatherpoly written into them. However, the programs that have timedata show the following error. I take it that eisy can't "see" the new PG3x NS as being the same. Any advice on how to point the eisy programs to the new weatherpoly NS without going through and manually updating each program? Any tips appreciated, Bob @bpwwer

I finally got around to installing and migrating to eisy/PG3x from my 994i and polisy (PG2). I had restored PG2 to PG3 on the polisy and attempted to migrate from PG3 to PG3x in eisy but received errors and instructions to install all of the NS's manually, so I did that. I installed them into the same slot numbers as before. I have hundreds of programs with timedata written into them. The PG3x timedata NS in eisy shows as online. However, the programs that have timedata show the following error. I take it that eisy can't "see" the new PG3x NS as being the same. Any advice on how to point the eisy programs to the new timedata server without going through and manually updating each program?

Happy holidays! I took a few days off anticipating that the eisy migration with Z-wave would be time-consuming based on others' posts. Did you hear back from Michel? Hoping there's an easier way.

LOL, me too. I'm a bit behind on updates and my Polisy doesn't seem to let me buy stuff from the store. Time to upgrade to the eisy.

Wow, that’s amazing! Thanks so much for making this NS, @sjpbailey. As my experience with SmartenIt has taught me, it’s good to have backup options in case a company goes under or divests. Will definitely pick up some of the TUYA-based devices to try out the NS.

Nevermind about starting a new thread, I'll just document this here for anyone trying to figure this out. Got the Sonoff flashed with Tasmota, assigned a reserved IP address through my router (doing it via Tasmota commands didn't work), and was able to send http web commands through my browser to turn various relays off and on. In the web browser, the commands that I found to turn the relays on/off look like this: On commands: http://192.168.1.1/cm?cmnd=Power1%20on You can replace 'on' with 'off' as needed. And each channel/relay is assigned a number: Power1, Power2, Power3, Power4. Next, I set up the device through the ISY's configuration--> Networking--> Network Resources tab. I decided to try a simpler route than xKing's method of setting up a node server on my Polisy, plus dedicated MQTT broker on an Raspberry Pi box. Maybe I'll go that route in the future. In Network Resources, I entered all the fields like so for each of the 4 relays and each command state (on and off) for a total of 8 network resources: Then clicked save--> save--> test, and it worked! Then I replaced the programs in my ISY that had the failed SmartenIt devices with the newly created Network Resources. In the program Actions drop down, select Networking--> Resource--> your new device names. Works like a charm and is simple. With the MQTT server option mentioned above, the device can get more sophisticated, like being able to tell you each channel's on/off state, but this is good enough to replace the basic functions of the EZIO4s.

So I decided to return the device as it wasn't friendly to customization and instead go for a Tasmota-flashed Sonoff 4 channel relay relay after seeing posts about the devices here. It costs more but there's a whole development community around these. I'll be starting a new thread about how to send commands to the device through the ISY without going the MQTT route, and if that doesn't work, I'll bite the bullet and go with the node server option.