Guy Lavoie

No, that's normal. The system will acquire pretty well all available memory for efficiency.

Thanks for the update! Nice to see a report of a straight dongle replacement to a different type.

Great! ...but I'll wait until Monday 😉

I ran into an interesting little issue this morning. In modifying my Calendar plugin, I asked it to remove some text descriptors it was putting in some values, such as "13 days" for the number of days left in the month. I want just the number because I want to be able to do numeric comparisons, like > , etc. It was trying to change the UOM to 56 (raw) to do that and at one point asked me to delete the existing nodes in PG3x. It seems to be thinking that PG3x is being used for plugin management, even though this one was created from scratch as an integrated plugin. The other thing is that unlike with PG3x where you can click on the "Nodes" heading of a plugin and manually delete nodes, there is no such thing available in the integrated plugins, that I can see anyway. When it saw that it couldn't work, it took a more roundabout route to getting done, successfully.

Did the Pittsburgh Steelers get paid a royalty for their logo? 😆

I'm just getting back into this, and created a second plugin, of a totally different nature. No hardware or network access, strictly making date related calculations, like if we're in an odd or even week of the year, if we're in the last full Monday to Friday week of the month, etc. Cities have been getting creative on setting up services like garbage collection (pardon the trash talk...) and getting advance notifications for these can be useful. In my city garbage collection is every week, but alternating between recyclables and regular garbage. Compostables is every week, except for winter (December to March) where it's every two weeks. Then there is large item pickup once a month, on your regular garbage day that falls in the last full Monday to Friday week of the month. Automate that... Well now I can! 🙂Other handy values are weekday instance of the month (eg: second Wednesday) I need to get around to setting up github and make this available to others.

Well like I said, the controller itself (Ocelot or Leopard) is obsolete, but can still be used to access any expansion modules, like the SECU16, SECU16I and SECU16IR modules. A Leaopard with a dead screen just becomes an oversized Ocelot.

@Javi Something is still not quite right with adding Z-Wave devices. I just obtained a second LR device, a Shelly i4 module (4 inputs). When I try to add it, it seems to be doing it but the interview always suddenly times out at about 65%. I tried setting the interview timeout to various values, up to 3 minutes. Including disabling and re-enabling Z-Wave, and rebooting the controller, but the timeout always occurs after less than one minute. It's as if it's igonoring the timeout setting. I tried this on both my eisy and my test Polisy (both have their own ZMatter dongles). The ZWAY log file ends like this: [2026-11-10 20:52:52.360] [I] [...] Adding job: Security S2 Encapsulation (S2 Authenticated), Configuration Get to node 258 [2026-11-10 20:52:52.525] [D] [...] Secure payload: ( 70 05 04 ) [2026-11-10 20:52:52.526] [D] [...] SENDING (cb 0x2e): ( 01 17 00 13 01 02 0F 9F 03 1E 00 B7 5D 51 D8 32 26 3D 49 31 DD 35 25 2E A4 ) [2026-11-10 20:52:52.532] [D] [...] RECEIVED ACK [2026-11-10 20:52:52.533] [D] [...] RECEIVED: ( 01 04 01 13 01 E8 ) [2026-11-10 20:52:52.533] [D] [...] SENT ACK [2026-11-10 20:52:52.534] [I] [...] Job 0x13 (Security S2 Encapsulation (S2 Authenticated), Configuration Get to node 258): Response received - transfered to encapsulated jobs [2026-11-10 20:52:52.534] [D] [...] Delivered to Z-Wave stack [2026-11-10 20:52:52.534] [D] [...] Delivered to Z-Wave stack [2026-11-10 20:52:52.548] [D] [...] RECEIVED: ( 01 1D 00 13 2E 00 00 01 00 D8 7F 7F 7F 7F 03 03 01 00 00 00 00 04 01 00 00 FA B7 FA CD B5 CD ) [2026-11-10 20:52:52.548] [D] [...] SENT ACK [2026-11-10 20:52:52.549] [I] [...] Job 0x13 (Security S2 Encapsulation (S2 Authenticated), Configuration Get to node 258): Callback received - transfered to encapsulated jobs [2026-11-10 20:52:52.549] [I] [...] Job 0x13 (Configuration Get to node 258): Delivered [2026-11-10 20:52:52.549] [D] [...] SendData Response with callback 0x2e received: received by recipient [2026-11-10 20:52:52.549] [D] [...] Job 0x13 (Configuration Get to node 258): success [2026-11-10 20:52:52.549] [I] [...] Waiting for job reply: Configuration Get from node 258 [2026-11-10 20:52:52.549] [I] [...] Job 0x13 (Security S2 Encapsulation (S2 Authenticated), Configuration Get to node 258): Delivered [2026-11-10 20:52:52.549] [D] [...] SendData Response with callback 0x2e received: received by recipient [2026-11-10 20:52:52.549] [D] [...] SETDATA devices.258.data.lastSendInternal = ********** [2026-11-10 20:52:52.549] [D] [...] SETDATA devices.258.data.lastSend = 39593791 (0x025c273f) [2026-11-10 20:52:52.549] [D] [...] Job 0x13 (Security S2 Encapsulation (S2 Authenticated), Configuration Get to node 258): success [2026-11-10 20:52:52.549] [D] [...] Security S2 send timer cleared [2026-11-10 20:52:52.549] [I] [...] Removing job: Security S2 Encapsulation (S2 Authenticated), Configuration Get to node 258 [2026-11-10 20:52:52.560] [D] [...] RECEIVED: ( 01 1D 00 04 00 01 02 14 9F 03 03 00 BB 60 32 F0 95 D8 D1 DB D6 D7 BB DA 36 53 5D B9 D8 00 09 ) [2026-11-10 20:52:52.561] [D] [...] SENT ACK [2026-11-10 20:52:52.561] [D] [...] SETDATA devices.258.data.lastReceived = 0 (0x00000000) [2026-11-10 20:52:52.561] [I] [...] Node 258:0 CC SecurityS2: passing S2 Authenticated decrypted packet to application level: [ 70 06 04 01 00 00 00 00 ] [2026-11-10 20:52:52.561] [D] [...] Received reply on job (Configuration Get to node 258) [2026-11-10 20:52:52.561] [D] [...] SETDATA devices.258.instances.0.commandClasses.112.data.4.size = 1 (0x00000001) [2026-11-10 20:52:52.561] [D] [...] SETDATA devices.258.instances.0.commandClasses.112.data.4.val = 0 (0x00000000) [2026-11-10 20:52:52.561] [D] [...] SETDATA devices.258.instances.0.commandClasses.112.data.4 = Empty [2026-11-10 20:52:52.561] [I] [...] Node 258:0 CC Configuration: Parameter 0x0004 = 0 (size = 1) [2026-11-10 20:52:52.562] [I] [...] Adding job: Security S2 Encapsulation (S2 Authenticated), Configuration Properties Get to node 258 [2026-11-10 20:52:52.725] [D] [...] Secure payload: ( 70 0E 00 69 ) [2026-11-10 20:52:52.726] [D] [...] SENDING (cb 0x2f): ( 01 18 00 13 01 02 10 9F 03 1F 00 86 D5 00 2A D9 B8 A2 B3 FB F2 77 AD 25 2F B4 ) [2026-11-10 20:52:52.732] [D] [...] RECEIVED ACK

In that case, I'd suggest opening a ticket with UDI. The Zooz 800 series stick is listed as supported.

Before going further: what version of IoX are you running? Sounds like this is a new eisy. Not sure what version it would have out of the box. If you're using eisy-ui, go into the System tab at the bottom and look at the IoX version. If it's older than 6.1.1, you should see that updates are available. Install them. You might not see a prompt for when to reboot, but you should do so a half hour later. After that, and checking that eisy-ui shows the updated version, retry adding Z-Wave devices.

I'm trying to add a second LR module, another Shelly device, a i4 (a 4 input device) and I can't get it to add. The interview times out, when it gets to abour 65% of the interview. I have the Z-Wave communication speed set to default, and Interview Timeout set to 3 minutes, but it times out after about 45 seconds. Something is wrong.

1- If you go into "Programs" and select a program, you see your program on the right and it's in edit mode. For each section (If, Then, Else) there is a "Add" button to add lines. To change the order of lines, you click and drag them to where yoIf any program changes are made, you will see a "Save"u want them. To delete lines, you click on the line and then click on the garbage can icon in the edit window. If any program changes are made, you will see a "Save" button to save it. The garbage can icon at the top is to delete the program. 2- it's browser based, so just fire up your phone browser and log into the same url as on your PC.

It really shines in that respect. In my Ocelot plugin, it tests the expansion modules, and asked me if I could give it one of the relays to test with, in activating it and reading back the status. I gave it the relay number it could use. In another case I didn't know if reading back 16 bit variables was low byte first or the other way around, and it tested it both ways.

I have Weiser locks (essentially, the Canadaian version of Kwikset locks). Five of them, and they have been very reliable. Several Smartcode 10 (500 series chipset) and Homeconnect 620 (700 series chipset). No real need for resets.

Ah, so you also caught the AI plugin bug! I was also totally amazed. Plugin creation for the rest of us! I made my Ocelot plugin as my forst one, which is already somewhat complex. I have a few other plugin ideas too. Like everything else, there's a learning curve, and you wonder how you need to "talk" to it. But you develop confidence with use. I'm expecting a flurry of plugin creation!

I haven't experienced it myself, but the announcement for support of the new dongles said they were automatically detected.

That last step shouldn't be necessary. It was only to revert to the original Zooz dongle. The newer IoX versions are supposed to automatically detect the newer dongles.

Actually, Paul's post reminds me of an interesting thing that happened in one of my keypadlincs a number of months ago: it's backlight would blink in sync with any Insteon powerline signals. I posted about it a the time. A factory reset and device restore fixed it, and it's been fine ever since.

The Usual way is to go in admin console (not eisy-ui) ,click on Configuration, and see if there is a button offering you to migrate to the ZMatter dongle. If there is, then you're set up for zooz dongle. If not, the do the browser command I posted earlier, reboot, and check again.

If you can see the circuit trace it goes to.

Did you reboot your controller?

I'd do a restore device on it.

Maybe cut the push on connector and solder the wire to the board?

issue the following url with a browser, which should roll back the switch to ZMatter: http://<your_IP_address>:8080/rest/zmatter/zwave/deactivateZMatterZWave

Did you power off the eisy before replacing the PLM? It's important.