GJ Software Products

@brians @Chris JahnI just excluded, did a factory reset on the ZEN17, brought it back in and that did not help either. node#.2 still commands R2 and shows the status for S1, and node#.3 does nothing.

@brians P2, P3 = 11, not 10? I got a ZEN17 to experiment with for my DI/DO project and am experiencing the strangest thing. After configuring parameters 2 and 3 to 10, excluding and adding the device back in, and even then powerfailing it, it brings in 4 nodes beneath the primary node, .1 through .4 . .1 commands R1, .2 is the status for S1, .3 does nothing, and .4 is the status for S2. One would think that .3 would command R2. But interesting enough, if you issue a command to .2 it commands R2. Essentially the .2 node reports the status of S1 and commands R2. I’ve excluded and added the device a couple times to no avail. While P2 and P3 persist through the exclude and add process, P10 and P11 don’t and I have to set them after the inclusion/add. Here are the parameters (queried) that I feel are applicable: P2=10, P3=10, P10=0, P11=0 . Any idea what’s going on here? Am I missing something?

@Mecheng70I wish I knew more about the internals of IoX to recommend anything other than reboot. Have you tried to reboot the eisy? When in doubt power out? Just like riding a wave runner. Make sure you got a backup. You might want to open a support ticket... Good luck!

@Mecheng70I upgraded last night to 5.5.5 in my eisy with the matter module and I've got ~30 Z-Wave devices that appear to be working although I haven't done a full functional test. Zooz, Leviton, GE, Kwikset, Aeotech It took a bit for things to "settle down", the ELK NS couldn't get a connection to the MQTT service after the auto restart after the install but worked on a hard reset from the unix command prompt. Some of my programs seemed to behave a bit funny but that seems to have caught up with itself and things seem back to normal this morning.

A bit ago I upgraded to 5.5.5 and after the eisy restarted I had to stop & start the ELK NS to get the nodes to populate with valid values. Although this time around when I forced a reboot it came to life on it's own. The log (attached) after the upgrade shows "ERROR interface:send: MQTT Send timeout" but after a stop & start that fixed it. And then it held through a reboot. I think all is well, just a similar /strange quirk like last time related to the startup of the MQTT service? But then the full reboot seemed to fix it too... PG3x 3.1.22, ELK 3.5.8 AfterUpgrade.zip

I noticed after the upgrade to 5.5.5 I get the following message on the Unix Console "/etc/rc: WARNING: $ud_pkg_stat_enable is not set properly - see rc.conf(5)." What should rc.conf look like? I assume this is a line in rc.conf? Got any idea why it's throwing this warning? Other than that, the ELK NS had to be stopped & started for the nodes to populate but then after a reboot from the Unix command prompt it started on it's own the 2nd time. Other than those couple little quirks everything appears to be ok.

From the ZEN16 documentation:

The ZEN16 is behaving similar. I only got one node that has a status field, the "main" device. If I turn this on or off it turns on/off all 3 relays. Here's what I got: And looking at the Event Viewer, although you see ST 0 and ST 100 every time the input opens & closes, the node ID is the same, ZY037_1, not 037.1, 2, 3 as they display in the tree.

I got a couple Zooz ZEN16s on sale that I was expecting to use as a (3) DI and (3) DO module. The device shows up as an On-Off Power Switch with (3) Basic Assoc Only nodes beneath it and it adds (3) Binary Switch nodes. No status or commands show for any of the (6) items. I’ve yet to understand how Basic Associations work and shouldn’t the Binary Switch objects have a status displayed? How can I get at the DOs & DIs individually to send discrete signals across the Network?

I had the same issue. Had program in my 994i that worked for years but as soon as I went to the eisy anything following the wait in the then would not run if the evaluation of the if went false during the wait. I did like spoken about above, I'm now using two programs. Yes, I too have never seen a language that re-evaluates the if once it's dropped into the then or else unless you're using a looping function like a do while...

I upgraded PG3x to 3.1.21 and it starts up fine now after a hard reboot from the Unix command line. Thanks All!

I had trouble with the ELK NS coming back to life after the upgrade to 5.5.4 yesterday and it appears to be it couldn't connect to the MQTT broker. I was able to issue it a Start command and it takes off running after that. I've been informed there is a known bug in PG3 after a full reboot and will need to wait for the next release. IoX & PG3 is starting up for me. I'm wondering if the problem could too be related to this full reboot bug?

How are the log files maintained in the eisy? Do they purge after 30 days? I came upon an old Unix box that had no retention policy and the log files would fill up the disk and hang the system and you would have to manually delete them. I had to dig into the MQTT logs on the eisy and while they get archived & compressed to ~1/2 a meg if they don't ever get purged I could see the disk space problem arising. I just want to see if I can get confirmation I don't need to be concerned with the log files consuming all the disk space at some point in time.

@briansNo, I haven't figured out how to do it using basic associations. I really don't know squat about zwave basic associations. I started playing with a scene but got nowhere. I'm just using programs to make them behave like a KeypadLinc.

It's been a reflective day here on the home front, I've officially decommissioned my ISY 994i that has been running the house for many years as everything (Insteon, Z-Wave, and ELK) have been successfully moved to my new eisy with the matter module. Not that there weren't a couple PITAs and there's a couple things still to be fixed in the firmware (it is published BETA so what do you expect?) but overall I am pleased with the outcome and look forward to the enhancements on the way. It might not be ready yet for an "out-of-the-box" homeowner to get into any complex configuration but anyone with a little comp sci savvy can be fairly successful if not 100% successful moving a system to the eisy. I didn't use the migration tools, I rebuilt my 30+ node system from scratch. Now I get to teach myself Python (that I'm way overdue on) & start playing with Node Server development if I can find time. Having been there, done that, I'd say go for it, move to the eisy!

@Jimbo.AutomatesDidn't look in the log. Hopefully it persists through the restart. "Nothing was populated"... All the text boxes for the values were empty (null?) with no data displayed. Let me see if there is any log data available. I just saw the new lines as it was restarting...

@TRI0N Take a look at That's how I replaced my KeypadLincs. You'll need the advanced sheet from Zooz that gives you all the paramaters too...

Just ‘kinda an FYI with a couple questions… I’m running the ELK nodeserver3.5.8 on an eisy that I upgraded IoX to 5.5.4 last night and I noticed this morning that I didn’t get the “Speak Phrase…” when the front door was unlocked. When I went and looked the ELK node, nothing was populated. Is it a common practice to have to restart the node server after a system interuption? I would think it would start automatically? What would happen after a power outage if I was not home to restart it?

@vbphil. Thanks. Yea, I got follow turned on for this thread and hopefully it'll get cleaned up. I knew this was beta, it is what it is. I run a lot of Beta stuff for some pretty big & recognized firms. Used to working out the bugs. I see we come from the same field, I'm in Aerospace too, not necessarily embedded stuff but I manage/support/develop on a control system for a couple hundred buildings in an Aerospace R&D Facility.

Ok, I found & installed 5.5.4, sync update w/ interview and I get the other node Leak Detected Alarm and that appears to work in my program. But only the new Leak Deteched Alarm node seems to work, Water Alarm under the "primary or 1st) node does not. Hopefully UDI can get this all rolled up in one node like it was before.

I too am having problems with a ZSE42 that I took from a working 994i at 5.3.4 and brought it into a eisy at 5.5.3 and the Status field I had in the 994 I cannot get at in my program in the eisy. Sounds like sync/update/int only get's you halfway there so I guess I'm just stuck 'till the next update?

I just installed the ELK node server and I can issue commands to, and get status back from the ELK M1EXP from both the module on my 994i and the PG3 NS on my eisy. I haven't fully proven this all out but I was glad to see both can be online see the ELK.

@brians I disabled control of the main switch using parameter 19 (&20). I've got 5 discrete buttons that I can trap a button press event on and I have programs to maintain the value of a state variable on or off and turn the LEDs on and off:

@briansHere's what the ZEN32 looks like in my eisy on the Z-Wave Matter module: I'm just trapping the button press events in a program & using them to turn stuff on and off. I've never really understood/figured out how to use Associations.

With all the data available in Z-Wave X-Ray can anyone confirm that when looking in Z-Wave X-Ray DH Controller the property data.firmware.build is the manufacturer’s release in the Z-Wave device? Or where do I find the manufacturer’s firmware build information? Or can I even? Or do I have to maybe use Simplicity Studio? I got a Zooz device and I would like to check the firmware level of that device. Thanks.