GJ Software Products

I've Never seen an Outback Inverter, now I gotta go looking! <lol>. Done a lot of Modbus with Square D (Schneider) PLCs, iON Electric Meters, UPSs by a couple manufacturers, ABB VFDs, Onicon Energy Meters, Caterpillar Generators, a few other off the wall integrations to Niagara but never seen an Outback Inverter. Is that used with pV(solar)?

I too would like to better understand the format of the JSON file, where it goes, and how it integrates. I.E. the format to define the registers, how to point to the address of the slave/RTU device, and how to access the nodes using isy. Some reference documentation would be great. I'd like to talk to my eisy with a SQD PLC using Modbus but without *any* documentation I really don't know where to begin on the eisy/pg3 side. Just need a bit to get me started without loading the node server and fighting my way through it.

Followed the instructions, all went well, it does take a bit to update & re-boot, I had to re-boot again. Clear Java cache so you get the updated admin console and that's about it. All seems well so far. -Grant

So, I just found out that the child proof coating on Duracell CR batteries is known to cause connectivity issues. That was apparent there was a voltage problem, but I kept checking with a few different batteries and they all read ~3.0v but maybe the holder don't like 'em. Now I just gotta find something besides Duracell. Sounds like a trip to Home Depot tomorrow. I'll post if this works.

I've had 1/2 dozen or so if these devices for a couple years now, they all used to work fine, but now at 5.8.4 the behavior has gotten strange. The other day one triggered when it detected moisture, then testing the others they did not trigger, they wake up when they feel like it, I excluded and re-included, they came in as a wake device(maybe just saw the one property?), I continued to fool with them, one after I had the battery out for ~! hour, let me include it in as a leak detector, it worked for a bit, but then it stopped working after I ran it through a few wet/dry cycles. Has anyone else had recent difficulties with these ZOOZ LSE42s? Got any recommendations? Thanks.

Digging deeper I found it needed a Firmware Update to get HDMI working. Updated the firmware and wahlah! Console output visible on HDMI port again. But I still should have a backup system to bring online in case of a failure.

@DennisC Thanks. You're right. I'm referring to the Z-Wave/Zigbee USB Dongle from UD. I figured that'd have to work but I'd read so much (or just enough) to make me uncertain if the full backup would maintain what I think is called the Home ID of the system or if I'd have to reinitialize every Z-Wave device because the original Home ID wouldn't persist. Thanks again for your input!

The HDMI port for the console output on my eisy stopped working. I've been thinking about this for a while, if I've got a complete backup, I.E. backup the dongle first then backup the eisy to a file on my HDD can that be restored to a new eisy and/or new dongle without having to discover and join each zwave and zigbee device over again? Let's say the eisy fails and I get a new one. What's the procedure to recover? Likewise for the Matter dongle?

Same thing here...

I'm still intermittently getting this error as recent as 3/9/24. 5.8.0_1 , 3.2.19 , 3.10.15 .

I figured I'd post this and see if anyone else experienced it. This AM after the time change last night I noticed all my night lights were still on. On opening the AC I found that the last run time for all my programs flagged run at startup or triggered by a program with run at startup was blank. I rebooted and everything started working right. Hummm... Oh yea, I'm at 5.8.0_1 .

Still today I too am seeing: "ELK (1): Failed" then "ELK (1): Connected" within one minute on the UD Mobile app. The node seems to be working, it's just those annoying messages. I'm at 5.7.1_7, 3.2.17, and Elk 3.10.11 .

I ran "Upgrade Packages" again (2nd time for _7) like @Techman said above, last night, I got a message upgrade complete on UD Mobile but it didn't ask me to reboot so I waited for a bit and rebooted. I haven't got the Elk nodeserver disconnect/reconnect messages since and z-wave, etc. appears all is running well.

@ShawnW For the heck of it I went ahead and ran Upgrade Packages again and my eisy just came back to life and I was fooling with it, I saw your post come up, it looks like after running Upgrade Packages again for _7 my eisy I think is behaving better... I'd say make your backups & run Upgrade Packages again. -Grant

Was there an update after the fix on 12/7?