jim_

JUST FYI To close this post ... a good solution to detect simple switch closures. The Wave i4's a very inexpensive compared to other ZW switch detectors on the market After many emails with Shelly support, the conclusion is as follows: The i4 have two purposes The main one is to be used with a button (spring loaded switch) in order to trigger the scenes (or other automation) with the Command Class Central Scene which is usually used in the Z-Wave remote controllers. The second is to be used by a toggle switch (normal On Off switch) this feature was added on users request. The main purpose of that is to report the state of an attached sensor (switch no button) so On or Off. There is a toggle function, but requires a value 0 (zero) mode and the switch speed is ~500 milliseconds as shows in these traces. As documented, value 2 (toggle) is specific to " Command Class Central Scene " using specific switch(s) and ZW controller Normal 1 second button (on / off) : where messaging follows button closure Thu 02/20/2025 13:55:52 : [ZY025_201N001 ] FDUP 2 (uom=115 prec=0) <<<<<<<<<<<< button closed = FDUP Thu 02/20/2025 13:55:53 : [ZY025_201N001 ] FDSTOP 4 (uom=115 prec=0) <<<<<<<<<<< button open = FDSTOP Fast ~500ms button cycle (on / off) : where button cycle changes the messaging state Thu 02/20/2025 13:57:04 : [ZY025_002_1 ] ST 0 (uom=78 prec=0) <<<<<<<< Transition from previous state to OFF (ST 0) Next Button Cycle Thu 02/20/2025 13:57:07 : [ZY025_002_1 ] ST 100 (uom=78 prec=0) <<<<< Transition from previous state to ON (ST 100) Also worth mentioning, in value 1 mode, the EISY controller can set the initial state to either ON or OFF for each switch 1-4, so function can be set to follow on / off or off / on which is a big PLUS when integrating with 3rd party equipment. e.g. if your connected to a generic motion detector where the relay operates normally closed, trigger to an open. I have 2 x i4's deployed, 4 standalone motion detectors, 2 connected to door switches (parallel) DSC alarm and NVR alarm out ... all controlling lights

Trying not to go down a deep hole here, but a NEW i4 out of the box, same issue After inclusion to EISY, value shows the default "0" value for switch 1 using the Zwave Config Param pop-up In event viewer, one see's this using a spring push button, hold count for 1-onethousand, release X2 Sun 02/02/2025 16:08:11 : [D2D EVENT ] Event [ZY025_201N001] [ST] [2] uom=115 prec=0 Sun 02/02/2025 16:08:11 : [ZY025_201N001 ] ST 2 (uom=115 prec=0) Sun 02/02/2025 16:08:11 : [D2D EVENT ] Event [ZY025_201N001] [FDUP] [2] uom=115 prec=0 Sun 02/02/2025 16:08:11 : [ZY025_201N001 ] FDUP 2 (uom=115 prec=0) Sun 02/02/2025 16:08:12 : [D2D EVENT ] Event [ZY025_201N001] [ST] [4] uom=115 prec=0 Sun 02/02/2025 16:08:12 : [ZY025_201N001 ] ST 4 (uom=115 prec=0) Sun 02/02/2025 16:08:12 : [D2D EVENT ] Event [ZY025_201N001] [FDSTOP] [4] uom=115 prec=0 Sun 02/02/2025 16:08:12 : [ZY025_201N001 ] FDSTOP 4 (uom=115 prec=0) Changing values are pretty clear in event viewer Sun 02/02/2025 16:13:31 : Create REST U7 [/rest/nodes/ZY025_1/cmd/CONFIG?NUM.107=1&VAL.111=1] Sun 02/02/2025 16:13:31 : U7 Rest: submitCmd([ZY025_1],[CONFIG],[NUM.107=1&VAL.111=1]) Sun 02/02/2025 16:13:31 : [ZW-TX-A 00296 25.0 ] [ZY025_1] Config Set parameter=1 value=1 (x1) size=1 Sun 02/02/2025 16:13:31 : [ZW-DONE 00296 25.0 ] [ZY025_1] Config Set parameter=1 value=1 (x1) size=1 Sun 02/02/2025 16:13:39 : Create REST U7 [/rest/nodes/ZY025_1/cmd/CONFIG?NUM.107=1&VAL.111=2] Sun 02/02/2025 16:13:39 : U7 Rest: submitCmd([ZY025_1],[CONFIG],[NUM.107=1&VAL.111=2]) Sun 02/02/2025 16:13:39 : [ZW-TX-A 00297 25.0 ] [ZY025_1] Config Set parameter=1 value=2 (x2) size=1 Sun 02/02/2025 16:13:39 : [ZW-DONE 00297 25.0 ] [ZY025_1] Config Set parameter=1 value=2 (x2) size=1 Testing the spring loaded switch in mode 2, same 1-onethousand count push / release ... same ON / OFF as mode 1 NOTE how the functional output jumps from Scene Button 1 >>> to >>> Binary Switch in Mode 1 or 2 Sun 02/02/2025 16:16:05 : [ZWAVE-CTL-EVENT ] Basic Set from 25.0 unmapped (ignored) Sun 02/02/2025 16:16:06 : [D2D EVENT ] Event [ZY025_002_1] [ST] [100] uom=78 prec=0 Sun 02/02/2025 16:16:06 : [ZY025_002_1 ] ST 100 (uom=78 prec=0)3e Sun 02/02/2025 16:16:07 : [ZWAVE-CTL-EVENT ] Basic Set from 25.0 unmapped (ignored) Sun 02/02/2025 16:16:07 : [D2D EVENT ] Event [ZY025_002_1] [ST] [0] uom=78 prec=0 Sun 02/02/2025 16:16:07 : [ZY025_002_1 ] ST 0 (uom=78 prec=0) AND ... in XRAY, Config confirms mode for switch 1 does change when this value is observed Switch 1 > Integer DATA devices.25.instances.0.commandClasses.112.data.1.val = 2 (0x00000002) verses Switch 2 > Integer DATA devices.25.instances.0.commandClasses.112.data.2.val = 0 (0x00000000) etc In the end, It is what it is ...

Thanks Rob ... I was hoping someone would twig if I was missing a step ... I've using both ways of configuration (both on the pop-up menu and on the root entry page of the console) and while setting mode 0 or 1 work, mode 2 just doesn't take. I understand that Shelly is offering these devices with the expectation they will be deployed into a normalized Zwave enviroment and typically interlink with "other" Shelly modules ... it is what it is So far all of my installs work in Mode 1, just wanted to have mode 2 available ... I'll keep poking it

While EnvisaLink-DSC is a available on Poly, my internet can be questionable at times, so me (in the minority of users), I'd rather run on something local. With over 130 network devices of various function(s), I actual run a network monitor [PRTG] to advise on any failures. DSC Link ran on the same PC, so having a deadicated PC already in place, may as well use it. If an EISY compatibale version of NodeLink were to be made available, it would be greatly appreciated For my small installation [3 zones], I found a cheat using Shelly Zwave i4 modules wiring them in parallel to DSC sensors such as door contacts or motion detectors. So far, integration has been very stable and no false triggers to date in almost 2 months running

I’m posting to ask a question about setting Zwave config. I really don’t know much about Zwave deployments or integrations, but I’m not able to set mode 2 on this switch, can anyone suggest if I’m setting the options correctly ? As per the manufacture’s bible https://kb.shelly.cloud/knowledge-base/wave-i4-dc-us Z-Wave Parameters Parameter No. 1 - SW (SW1) Switch type This parameter defines how the Device should treat the switch (which type) connected to the SW (SW1) terminal. Value size: 1 Byte Default value: 0 Values & descriptions: 0 - momentary switch (push button), 1 - toggle switch (contact closed - ON / contact opened - OFF), 2 - toggle switch (Device changes status when switch changes status) Testing First, I asked Shelly support for a more detailed explanation of modes 1 & 2 as the documentation was vague, this was their reply. NOTE: When I requested support for “Mode 2” not working … Shelly support responded, unless the modules are deployed using a certified Zwave controller, they cannot guarantee correct operation. 1. Parameter set to value 1 (contact closed ON / contact closed OFF): In this setting, the switch behaves like a traditional switch controlling a normal bulb. The position of the switch determines the state of the output. For example, when the switch is pressed down, the light is ON (power is ON), and when the switch is pressed up, the light is OFF, regardless of any changes made to the output via the gateway or commands. 2. Parameter set to value 2 (toggle mode): In this setting, the position of the switch no longer matters. Each time you change the position of the switch, it toggles the state of the output (e.g., ON to OFF or OFF to ON). This happens even if you use the gateway or commands to change the state of the output in between. The switch simply flips the output state whenever it is toggled Set Mode 0 on switch port 1 Event viewer == Mon 01/27/2025 15:16:09 : U7 Rest: submitCmd([ZY024_1],[CONFIG],[NUM.107=1&VAL.111=0]) You’ll see FDUP & FDSTOP value toggle for Scene Button 1 matching event viewer Mon 01/27/2025 15:17:23 : [ZY024_201N001 ] ST 2 (uom=115 prec=0) Mon 01/27/2025 15:17:23 : [ZY024_201N001 ] FDUP 2 (uom=115 prec=0) <<< button closed Mon 01/27/2025 15:17:24 : [ZY024_201N001 ] ST 4 (uom=115 prec=0) Mon 01/27/2025 15:17:24 : [ZY024_201N001 ] FDSTOP 4 (uom=115 prec=0) <<< button open Set Mode 1 on switch port 1 Event Viewer == Mon 01/27/2025 15:25:38 : U7 Rest: submitCmd([ZY024_1],[CONFIG],[NUM.107=1&VAL.111=1]) Mon 01/27/2025 15:25:50 : [ZWAVE-CTL-EVENT ] Basic Set from 24.0 unmapped (ignored) Mon 01/27/2025 15:25:51 : [ZY024_002_1 ] ST 100 (uom=78 prec=0) <<< button closed Mon 01/27/2025 15:25:51 : [ZWAVE-CTL-EVENT ] Basic Set from 24.0 unmapped (ignored) Mon 01/27/2025 15:25:51 : [ZY024_002_1 ] ST 0 (uom=78 prec=0) <<< button open =================================================================================== Mon 01/27/2025 16:06:23 : U7 Rest: submitCmd([ZY024_1],[CONFIG],[NUM.107=1&VAL.111=2]) In Mode 2, functions appear identical to mode 1 in event viewer, so what am I missing in the Zwave world to set this to Mode 2 ? ===================================================================================== p.s. I have one of these units deployed for the past month and appear to be very stable tying them into a DSC panel, hardwired door contacts and multiple standalone motion detectors. If anyone want more detail, please feel free to ping me

Now I can add the plugin PING, and while there is configuration help, there is no field to enter a IP Address The only editable fields are the PING duration timers Again help ... (

Thanks to DennisC for the help ... For anyone who is new ISY or eisy and reading this thread, in the main Wiki, there is a DOC named ISY Portal Installation Instructions ... You will need to register the MAC address of your UD device, then approve it on the Admin Console

I found and removed ISYLink from plugins / configure ... Rebooted, connected Polyglot 3x, still get errors trying to install PING Looked at the Log, can someone translate please 2024-12-19 09:04:25.307 [pg3] info: ------------------------------------------------------------ 2024-12-19 09:04:25.309 [pg3] info: Starting PG3x version 3.2.27 2024-12-19 09:04:25.309 [pg3] info: Using Workdir /var/polyglot/pg3/ 2024-12-19 09:04:25.313 [pg3] info: Starting sqlite database at /var/polyglot/pg3/pg3.db 2024-12-19 09:04:25.335 [pg3] info: Encryption key found ID: XXX long key XXX. Database version 1 2024-12-19 09:04:25.339 [pg3] info: Query IoX for platform UUID. 2024-12-19 09:04:40.991 [pg3] info: ------------------------------------------------------------ 2024-12-19 09:04:40.992 [pg3] info: Starting PG3x version 3.2.27 2024-12-19 09:04:40.993 [pg3] info: Using Workdir /var/polyglot/pg3/ 2024-12-19 09:04:40.996 [pg3] info: Starting sqlite database at /var/polyglot/pg3/pg3.db 2024-12-19 09:04:41.001 [pg3] info: Encryption key found ID: XXX long key XXX. Database version 1 2024-12-19 09:04:41.005 [pg3] info: Query IoX for platform UUID. 2024-12-19 09:04:41.028 [pg3] info: Found IoX with UUID XXX MAC ADDR XXX 2024-12-19 09:04:41.033 [pg3] info: Loaded globalsettings successfully. Database version 1 2024-12-19 09:04:41.035 [pg3] info: isys currently in table: [{"id":"XXX long key XXX","uuid":"XXX MAC ADDR XXX","name":"IoX","ip":"127.0.0.1","port":8080,"username":"#####","password":"#####","enabled":1,"discovered":1,"version":"5.8.4","secure":0,"timeAdded":1734381793822,"timeModified":1734616900181,"dbVersion":1}] 2024-12-19 09:04:41.036 [pg3] info: isy table: Loaded (1) successfully 2024-12-19 09:04:41.036 [pg3] info: IoX: XXX MAC ADDR XXX 5.8.4 127.0.0.1 XXX long key XXX 2024-12-19 09:04:41.038 [pg3] info: nodeserver table: Loaded 1 nodeserver(s) successfully 2024-12-19 09:04:41.040 [pg3] info: store is up-to-date 2024-12-19 09:04:41.054 [pg3] info: Forcing custom certificates to off 2024-12-19 09:04:41.057 [pg3] info: Updated configuration with overrides 2024-12-19 09:04:41.058 [pg3] info: Setting PG3 log level to error 2024-12-19 09:04:41.149 [pg3] error: Failed to get node server store https://pg3store.isy.io/v2/list :: Error: getaddrinfo ENOTFOUND pg3store.isy.io 2024-12-19 09:04:41.150 [pg3] error: (catch) Failed to get node server store https://pg3store.isy.io/v2/list :: TypeError: Cannot read properties of undefined (reading 'data') 2024-12-19 09:04:41.150 [pg3] error: Failed to get any data from Production store... 2024-12-19 09:04:41.155 [pg3] error: Failed to get node server store https://pg3betastore.isy.io/v1/list :: Error: getaddrinfo ENOTFOUND pg3betastore.isy.io 2024-12-19 09:04:41.155 [pg3] error: (catch) Failed to get node server store https://pg3betastore.isy.io/v1/list :: TypeError: Cannot read properties of undefined (reading 'data') 2024-12-19 09:04:41.156 [pg3] error: Failed to get any data from Beta store... 2024-12-19 09:06:52.627 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:07:01.373 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:10:11.051 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:10:30.346 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:11:03.660 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:11:09.856 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:11:43.195 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:11:45.742 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:12:17.023 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:12:23.423 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:12:28.896 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:12:32.753 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:26:22.897 [pg3] error: Failed to get license 2024-12-19 09:26:22.897 [pg3] error: AxiosError: Request failed with status code 404 2024-12-19 09:26:22.897 [pg3] error: getNewLicense: TypeError: Cannot read properties of undefined (reading 'statusText') 2024-12-19 09:26:23.243 [pg3] error: transactionReport: uuid XXX MAC ADDR XXX not found in portal account 2024-12-19 09:26:29.641 [pg3] error: Failed to get license

I have read through Polisy:User Guide, but not grasping the big picture of how this works I am able to login to Polyglot 3x, first thing I see is this page, I searched through DOC's and the forum, can't find anything to explain what isylink is ?? I then tried to install something simple like PING, but get a big red error any help getting started would be appreciated

Thanks Geddy, I agree, I've been keeping txt files for decades of configs. Cant count the number of times people came to me begging for a copy to restore switches or appliances ... but I did earn lots of beers Migration complete, UD support provided a slightly modified set of steps as I was migrating from 994 with serial PLM direct to eisy with USB PLM. The doc was about 8 single lines of steps, far easier to follow than the public guide

Thanks for both comments With my many decades of engineering and operations, my world was all about DOCs and following standard equipment deployments. Having designed IP networks, we look at all the connected devices we live with daily. Hardware manufactures now include both wired and WiFi to offer more flexibility and redundancy. That's my rant Geddy, your right, I need to bring this back to user helps user, I got caught in the frustration of poor docs. After studying the guide tonight https://wiki.universal-devices.com/UD_Mobile#eisy_WiFi_Configuration for hours, I gave up and picked up my mobile. Starting with a freshly reset eisy, powered up with no LAN and logged in to watch the messages on the console On my mobile, I just opened the 3 dots top right, selected WiFi config for eisy, followed the prompts (not adding new node) It took a while, and after a few refreshes, the system messages started rolling on the console, it rebooted and I could ping the internet from the eisy The method UD is using is magical, looks like virtual NAT as ifconfig does NOT match the new local IP or the MAC found in DHCP server ... but its working Now, here's the test ... reconnect the LAN cable, does it reconverge, NOPE, but you will see the eisy teardown the 2 interfaces associated with WiFi "wifibox0" and "tap0" If you reboot (sudo reboot), with the LAN connected, it works ... if you reboot with the LAN disconnected, WiFi works, BUT be aware, each time it restarts, it acquires a new / different IP from the previous in WiFi mode (this is wrong) My Linux is ok, I know enterprise linux distro and all the commands, but the openBSD is different, I'll get my son to poke at this beast I ran a hardware query on the unit, there is an Intel WiFi 6 AX201 present, but unassigned ... but I'll poke at it on a rainy day Now, I can only master migration

Agreed, however the document which is the isy:User_Guide#Installation fails to direct the reader to the UD_Mobile I'm bench testing to be come familiar with the new platform before permanent install replacing my 994. During my testing, I found that if the LAN is disconnected for a period of time, this causes a NTP issue in the eisy network stack. I have the eisy connected to a monitor and you will see a constant ntpd error, unable to resolve pool.ntp.org. (AKA can't sink with external NTP clock), I've found some other issues as well, but will investigate later So, why install WiFi ? Do you have a laptop that supports both LAN & WiFi, if LAN fails, WiFi restores the connection and your still connected to whatever is required I have read the UD_Mobile and now even more confused .. I am NOT an existing portal user, therefore I jump to section Local Connections and Local VPN The very next line states Before starting verify you are connected to the same WiFi network as your UD Hardware. The next line > Go to Settings Tab > Systems > your-system-name, etc etc When opening settings, (hamburger wheel) nowhere do you find the word "Systems", I could scroll down to App Settings and add a NEW Controller ? There is also the Admin section, WiFi Configuration , Configure eisy's WiFi Adapter ... which always fails with the same error " Could not get BLE Connection " There is no straight forward document explaining how to enable WiFi on this eisy !!!

I have the Mobile and found the eisy's WiFi via bluetooth After adding the SSID and Password, the screen pop's up an error " Could not get BLE Connection " repeated the proceedure several times with same result

Thank you, that was my suspicion... Again the [Eisy:User Guide] has failed to identify this twist in their migration procedure

I disconnected LAN and pressed the button x2 as per the guide ... so now what happens, where do you do the configuration for the SSID / Key as there is no method to edit on the EISY (Network is greyed out) ? Like most dual connected platform / OS, if LAN fails, WiFi can assume connection, so I wanted to test it Again, the [Eisy:User Guide] fails to guide the reader on how WiFi connection is established