Bumbershoot

I just did a quick test and was able to place a file in a directory, but of course I had to use 'sudo' to do it. I was able to edit the file as well, using 'nano'. 'sudo nano ./your/Directories/Here/devlist.yml'

I had much better luck using a 'devlist.yml' file than depending upon LiFX discovery when I started the node server. I'm not currently using LiFX bulbs, but this made life far easier:

Assuming that you're on the latest/greatest firmware: Right click on the device/node you're interested in, select "X-Ray" from the context menu. An X-Ray window will pop up, then select "Node Info" from the drop down list, and click on "Go". In the example in the screenshot, the device is "ZY007_1", and the value you're looking for is "Lumin". The value in your email would look like this: ${sys.node.ZY007_1.LUMIN}

The other Sonos plugin (ST-Sonos) has this functionality. I've used this in programs, not scenes, and it mostly worked (I currently don't use this function), though occasionally it wouldn't ungroup successfully IIRC. I see there's a 7 day free trial that you could test it with.

Sorry, but I think you needed to backup the Z-Wave dongle separately, prior to doing a general backup of the ISY. The Z-Wave backup would be included in the ISY backup. You might be able to restore your ISY backup, backup the Z-Wave dongle, the backup the ISY and you'd be good. Opening a ticket is probably the right way to go, however. See screenshot.

I'm not sure this is the problem you're having, but you have to specifically allow software from unknown developers to run on your iMac. Once you try to run 'start.jnlp' and it fails, navigate to the "Systems Settings" app, then click on "Security & Privacy", then scroll down a bit to where you see a dialog that will allow you to install software from an unknown developer. The screenshots illustrate this.

I really doubt I can help you here (it's been a long time since I did this), but I still use associations for some Z-Wave lights in a bathroom. One of the dimmers controls two others (these are Zooz Zen77 dimmers). You have to put all the devices in a scene in your eISY, and one of the devices has to be the controller. You need to put the "Basic Association" nodes you want (sometimes there is more than one - in my case I have one for on/off and one for dimming) of the controlling device into the scene as controllers, and then the other devices as responders. See screenshots. This seems to be mostly reliable (on/off is reliable, but dimming is a bit hit or miss). It's not as seamless as an Insteon scene by any means. I believe the devices have to be in close proximity to one another for this to work, and the devices talk directly to one another, not through your ISY software.

It's not so simple, but if you want to avoid the Hue bulb turning on when this program runs, you could do this: take the Hue bulb out of this program, and write a second program that looks for the desired initiating event, and when it sees that event, sets the attributes for the Hue light, which will turn it on. It might not be a completely seamless visual effect, but...

I have a program that sets the kitchen lights to a low "on" level early in the morning (4:30am). When I ask Alexa to modify the on level when I make coffee doesn't have any affect on the program at all. The program is set to run at a specific time, and once that happens, the program is done for the day. What I do subsequently doesn't matter to the program I use. When I tell Alexa to set the light to a different value, the program doesn't execute. The difference between scenes and programs is that scenes change the lights in the scene in parallel (all at the same time), and programs change the lights in the program in series (one after the other). Scenes are much more elegant to use, but programs are easier to create and manage IMHO. It just depends on your use case. I hope I'm not misunderstanding your question. EDIT: BTW, Alexa can initiate both programs and scenes. A great parlor trick is when we have company over for dinner, and I say, "Alexa, turn on dinner", and the lights in the house all turn to set values (a scene), then a music station plays on the Sonos node server (the next line in the program that turns on the scene). It's almost too easy... EDIT2: If you want to run a program that adjusts a scene, then Alexa will do it for you. In the program, you could run "adjust scene", wait a few seconds, then run the scene with the adjusted values.

I have two remote sensors (one of these is called "Office Sensor"). The thermostat is set to average the temperature between the two remotes and the thermostats itself, but I have the ability to select an individual sensor and adjust the temperature based on that sensor. I don't quite understand what you're asking for, but you have this programmatic ability (the office gets direct sun and warms up quicker than the thermostat or the other sensor): EDIT: "Living Room" is the name of the Venstar thermostat that the remotes are connected to. New Program - [ID 0080][Parent 00A7] If 'Devices / dirPolyglot / Venstar / Living Room / Office Sensor' Temperature is 72°F Then Set 'Devices / dirPolyglot / Venstar / Living Room' Mode Off Else - No Actions - (To add one, press 'Action')

In our home, we find that the right level of lighting really makes the house much more pleasant, and being able to adjust a variety of dimmer switches without having to fiddle with each one really improves the usability of the house. We change the 'on' values of the kitchen lights based on activity, time, ambient light, etc. We don't even need to physically touch the switch. Preparing meals in the evening means we have the lights on brighter, around 80%. After dinner clean up and they go somewhat dimmer, maybe to 45%. Making coffee early in the morning, they're dimmer still. We can turn them on/off or to a particular percentage just by asking Alexa and not having to touch the switches (there are several that in combination light up our kitchen). The same goes for our living room, primary bedroom, etc., where the switches are much more inconveniently located around the rooms (which is the reason I started with home automation in the first place). BTW, this functionality has a high WAF (wife approval factor).

I use 1000 because I'm never going to set the variable's value to 1000, which means the program will run every time the value is set to any other number. The only possible numbers for the program to work are 0-100, which corresponds to a % on value for the Insteon dimmers. EDIT: FWIW, this program is called from an Alexa routine that sets the value of the state variable (s.KitchenLights) to a spoken value, i.e., "Alexa, set the kitchen lights to 45", and the devices in the program change to a 45% on value. The routine is called "kitchen lights"... Works like a charm.

You don't have to declare anything. Just create the variable (in this case, $s.KitchenLights is a state variable, which is why I prefix the name with the 's' - If it were an integer variable, I would have named it 'i.KitchenLights'). Once you've created the variable, it's available to use in programs. You have to select the ">" symbol in the AC program interface to select the % or variable you want to use. See screenshot:

Easily done, Here's an example (all the 'sld* devices are Insteon SwitchLinc Dimmers): KitchenLights - [ID 0077][Parent 000A] If $s.KitchenLights is not 1000 Then Set 'Devices / dirKitchen / sldKitchenSink' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldDining' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldKitchenIslandSouth' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldKitchenIslandNorth' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldTrackLightSouth' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldTrackLightNorth' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldUnderCounter' On '$s.KitchenLights %' Else - No Actions - (To add one, press 'Action') This program is used to interface with Alexa, and uses a STATE variable ($s.KitchenLights) to set a brightness value for the lights in the kitchen. "Alexa, set the kitchen lights to 50" will set the STATE variable to 50, which causes this program to run.

Currently, the app runs on M1 and M2 Apple machines.

This is almost the exact solution that I use. It has been highly reliable.

I find Z-Wave group associations to work, but they're a bit sketchy. I don't really have any useful advice. You might look in this thread to see if there's any useful information:

Right click on one of your Z-Wave devices, then you'll see the Z-Wave | OTA Firmware Upgrade menu items.

Confirmed here. I didn't notice as I don't use that function.

I believe the correct answer is "both".

I use the "say" function, which generates a predetermined TTS message to play on the selected speakers. Example: when someone approaches the front door, the motion sensor in my Ring doorbell activates, which activates an ISY program that plays a TTS announcement, such as, "Someone is at the front door", on a selected device. Here's what the "then" stanza of a program looks like: Then Set 'Devices / dirPolyglot / ST-Sonos / ST-Sonos / Sonos Living Room' Say Someone is at the front door Else - No Actions - (To add one, press 'Action') The "sayall" function takes longer to actuate, as it creates a Sonos group out of all your speakers before it plays the TTS announcement. It used to struggle a bit returning your Sonos back to the original groupings, but I haven't used the feature in a while. I don't use the MP3 clip function, so I don't know how that works.

Here's a link to look at on how to get "associations" working in Z-Wave. They work with devices in close proximity, but not with the elegance of Insteon scenes.

@Geddy, there is no "Update" button, and the "Install" button is still present. My results on reinstalling are the same as @GTench. Nothing interesting in the YoLink node server log, and below is a snip from the PG3x 3.1.27 log during the upgrade. Doesn't seem that there are any errors or issues: /28/2023, 14:40:03 [pg3] info: Starting log stream for pg3frontend_9AEIN :: /var/polyglot/pg3/ns/0021b9026016_10/logs/debug.log 5/28/2023, 14:40:20 [pg3] info: Installing 78312440-23ea-4ed6-9361-9cdc2d5e7c6b 5/28/2023, 14:40:20 [pg3] info: [00:21:b9:02:60:16_10] :: Creating Nodeserver 'YoLink' 5/28/2023, 14:40:20 [pg3] info: [YoLink(10)]: Stopping Nodeserver 5/28/2023, 14:40:20 [pg3] info: call_udx: Making reqeust to socket for /rest/pg3.stop.ns 5/28/2023, 14:40:20 [pg3] info: call_udx: /rest/pg3.stop.ns on socket happened. 5/28/2023, 14:40:20 [pg3] info: call_udx: /rest/pg3.stop.ns on finish happened. 5/28/2023, 14:40:20 [pg3] error: getNewLicense: TypeError: Assignment to constant variable. 5/28/2023, 14:40:20 [pg3] info: call_udx: incoming chunk {"status":"success"} 5/28/2023, 14:40:20 [pg3] info: call_udx: /rest/pg3.stop.ns returns {"status":"success"} 5/28/2023, 14:40:20 [pg3] info: YoLink preveously installed, re-installing... 5/28/2023, 14:40:20 [pg3] info: Adding customparams entries to custom database 5/28/2023, 14:40:21 [pg3] info: Adding nsdata, oauth entries to custom database 5/28/2023, 14:40:21 [pg3] info: [00:21:b9:02:60:16_10] Set nsdata 5/28/2023, 14:40:21 [pg3] info: [00:21:b9:02:60:16_10] Set oauth 5/28/2023, 14:40:21 [pg3] info: call_udx: /rest/pg3.stop.ns on close happened. 5/28/2023, 14:40:21 [pg3] info: Pushing notification {"title":"YoLink (10): Disconnected","body":"from PG3"} to UD Mobile 5/28/2023, 14:40:21 [pg3] info: checkLicense:: YoLink Valid perpetual license found. 5/28/2023, 14:40:21 [pg3] info: Deploying YoLink's files to node server directory 5/28/2023, 14:40:21 [pg3] info: call_udx: Making reqeust to socket for /rest/pg3.install.ns 5/28/2023, 14:40:21 [pg3] info: call_udx: /rest/pg3.install.ns on socket happened. 5/28/2023, 14:40:21 [pg3] info: call_udx: /rest/pg3.install.ns on finish happened. 5/28/2023, 14:40:26 [pg3] info: [00:21:b9:02:60:16_4] controller reporting command DON 5/28/2023, 14:40:27 [pg3] info: call_udx: incoming chunk {"status":"success"} 5/28/2023, 14:40:27 [pg3] info: call_udx: /rest/pg3.install.ns returns {"status":"success"} 5/28/2023, 14:40:27 [pg3] info: Installing YoLink on IoX 5/28/2023, 14:40:27 [pg3] info: call_udx: /rest/pg3.install.ns on close happened. 5/28/2023, 14:40:27 [pg3] info: [00:21:b9:02:60:16_10] 'YoLink' installed into Iox successfully... 5/28/2023, 14:40:27 [pg3] info: Installing YoLink's profile files on IoX 5/28/2023, 14:40:27 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/nodedef 5/28/2023, 14:40:27 [pg3] info: Uploading nodedefs.xml 5/28/2023, 14:40:27 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/editor 5/28/2023, 14:40:27 [pg3] info: Uploading editors.xml 5/28/2023, 14:40:27 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/nls 5/28/2023, 14:40:27 [pg3] info: Uploading en_us.txt 5/28/2023, 14:40:27 [pg3] info: Installation complete. Starting YoLink 5/28/2023, 14:40:27 [pg3] info: startNs:: YoLink 5/28/2023, 14:40:27 [pg3] info: startNs:: YoLink is valid 5/28/2023, 14:40:27 [pg3] info: upload successful 5/28/2023, 14:40:27 [pg3] info: upload successful 5/28/2023, 14:40:27 [pg3] info: checkLicense:: YoLink Valid perpetual license found. 5/28/2023, 14:40:27 [pg3] info: startNs:: YoLink finished update check 5/28/2023, 14:40:27 [pg3] info: upload successful 5/28/2023, 14:40:28 [pg3] info: startNs:: Starting YoLink 5/28/2023, 14:40:28 [pg3] info: call_udx: Making reqeust to socket for /rest/pg3.start.ns 5/28/2023, 14:40:28 [pg3] info: call_udx: /rest/pg3.start.ns on socket happened. 5/28/2023, 14:40:28 [pg3] info: call_udx: /rest/pg3.start.ns on finish happened. 5/28/2023, 14:40:28 [pg3] info: call_udx: incoming chunk {"status":"success"} 5/28/2023, 14:40:28 [pg3] info: call_udx: /rest/pg3.start.ns returns {"status":"success"} 5/28/2023, 14:40:28 [pg3] info: startNs:: YoLink starting polls 5/28/2023, 14:40:28 [pg3] info: Starting YoLink Info timer 0 5/28/2023, 14:40:28 [pg3] info: startNs:: YoLink updating database (enabled, timestarted) 5/28/2023, 14:40:28 [pg3] info: startNs:: YoLink started. 5/28/2023, 14:40:28 [pg3] info: call_udx: /rest/pg3.start.ns on close happened. 5/28/2023, 14:40:29 [pg3] info: Pushing notification {"title":"YoLink (10): Connected","body":"from PG3"} to UD Mobile 5/28/2023, 14:40:29 [pg3] info: [00:21:b9:02:60:16_10] Retrieved customparams 5/28/2023, 14:40:29 [pg3] info: [00:21:b9:02:60:16_10] Retrieved customtypeddata 5/28/2023, 14:40:29 [pg3] info: [00:21:b9:02:60:16_10] Retrieved notices 5/28/2023, 14:40:29 [pg3] info: [00:21:b9:02:60:16_10] Retrieved oauth 5/28/2023, 14:40:30 [pg3] info: Starting log stream for pg3frontend_9AEIN :: /var/polyglot/pg3/ns/0021b9026016_10/logs/debug.log 5/28/2023, 14:40:32 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/nodedef 5/28/2023, 14:40:32 [pg3] info: Uploading nodedefs.xml 5/28/2023, 14:40:32 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/editor 5/28/2023, 14:40:32 [pg3] info: Uploading editors.xml 5/28/2023, 14:40:32 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/nls 5/28/2023, 14:40:32 [pg3] info: Uploading en_us.txt 5/28/2023, 14:40:32 [pg3] info: upload successful 5/28/2023, 14:40:32 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:40:32 [pg3] info: upload successful 5/28/2023, 14:40:32 [pg3] info: node setup on profile 10 already exists, no nodeDef or driver changes detected 5/28/2023, 14:40:32 [pg3] info: upload successful 5/28/2023, 14:40:38 [pg3] info: [00:21:b9:02:60:16_10] Set customparams 5/28/2023, 14:40:38 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:40:38 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:40:38 [pg3] info: node 8b4c0100050e67 on profile 10 already exists, no nodeDef or driver changes detected 5/28/2023, 14:40:41 [pg3] info: [00:21:b9:02:60:16_10] 8b4c0100050e67 reporting command DON 5/28/2023, 14:40:44 [pg3] info: [00:21:b9:02:60:16_10] Set customparams 5/28/2023, 14:40:44 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:40:44 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:40:44 [pg3] info: node 8b4c010005968a on profile 10 already exists, no nodeDef or driver changes detected 5/28/2023, 14:40:48 [pg3] info: [00:21:b9:02:60:16_10] Set customparams 5/28/2023, 14:40:48 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:40:48 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:40:48 [pg3] info: node 8b4c01000585b8 on profile 10 already exists, no nodeDef or driver changes detected 5/28/2023, 14:40:51 [pg3] info: [00:21:b9:02:60:16_10] 8b4c01000585b8 reporting command DOF 5/28/2023, 14:40:54 [pg3] info: [00:21:b9:02:60:16_10] Set customparams 5/28/2023, 14:40:54 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:40:54 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:40:54 [pg3] info: node 8b4c010005a51d on profile 10 already exists, no nodeDef or driver changes detected 5/28/2023, 14:41:02 [pg3] info: [00:21:b9:02:60:16_10] Set customparams 5/28/2023, 14:41:02 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:41:02 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:41:02 [pg3] info: node 8b4c010005a9ed on profile 10 already exists, no nodeDef or driver changes detected 5/28/2023, 14:41:10 [pg3] info: [00:21:b9:02:60:16_10] Set customparams 5/28/2023, 14:41:10 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:41:10 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/nodedef 5/28/2023, 14:41:10 [pg3] info: Uploading nodedefs.xml 5/28/2023, 14:41:10 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/editor 5/28/2023, 14:41:10 [pg3] info: Uploading editors.xml 5/28/2023, 14:41:10 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/nls 5/28/2023, 14:41:10 [pg3] info: Uploading en_us.txt 5/28/2023, 14:41:10 [pg3] info: upload successful 5/28/2023, 14:41:10 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:41:10 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:41:10 [pg3] info: node 8b4c1604003576 on profile 10 already exists, no nodeDef or driver changes detected 5/28/2023, 14:41:10 [pg3] info: upload successful 5/28/2023, 14:41:11 [pg3] info: upload successful 5/28/2023, 14:41:16 [pg3] info: [00:21:b9:02:60:16_10] Set customparams 5/28/2023, 14:41:16 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:41:16 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:41:16 [pg3] info: node 8b4c010005969b on profile 10 already exists, no nodeDef or driver changes detected 5/28/2023, 14:41:20 [pg3] info: [00:21:b9:02:60:16_10] Set customparams 5/28/2023, 14:41:20 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:41:20 [pg3] info: [00:21:b9:02:60:16_10] Set notices 5/28/2023, 14:41:20 [pg3] info: node 8b4c010005886a on profile 10 already exists, no nodeDef or driver changes detected 5/28/2023, 14:41:24 [pg3] info: [00:21:b9:02:60:16_10] 8b4c010005886a reporting command DOF 5/28/2023, 14:41:26 [pg3] info: [00:21:b9:02:60:16_4] controller reporting command DOF 5/28/2023, 14:41:27 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/nodedef 5/28/2023, 14:41:27 [pg3] info: Uploading nodedefs.xml 5/28/2023, 14:41:27 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/editor 5/28/2023, 14:41:27 [pg3] info: Uploading editors.xml 5/28/2023, 14:41:27 [pg3] info: installProfile: YoLink :: read /var/polyglot/pg3/ns/0021b9026016_10/profile/nls 5/28/2023, 14:41:27 [pg3] info: Uploading en_us.txt 5/28/2023, 14:41:27 [pg3] info: upload successful 5/28/2023, 14:41:27 [pg3] info: upload successful 5/28/2023, 14:41:28 [pg3] info: upload successful 5/28/2023, 14:41:28 [pg3] info: [00:21:b9:02:60:16_10] setup reporting command DON

I have a i3 paddle that I haven't installed. I wanted the Mrs. to get a choice between the paddles and dials, and she chose the dials for this application. The paddle worked just fine when controlled by IoX 5.6.0, but local manipulation events using the paddle were unseen, so the status never changed in IoX.

Not sure what's up, but the motion nodes don't have any displayable properties that indicate motion. As for the programs, did you restart the AC after you installed the node server? Be sure to use "Control" in your programs instead of "Status". Below is a program that I'm using, and it's working like a champ. Outdoor Motion - [ID 00CC][Parent 000F] If 'Devices / dirPolyglot / Ring / Ring / Front Door (Motion)' is switched Motion Or 'Devices / dirPolyglot / Ring / Ring / Deck - West (Motion)' is switched Motion Or 'Devices / dirPolyglot / Ring / Ring / Deck - East (Motion)' is switched Motion Or 'Devices / dirPolyglot / Ring / Ring / Side (Motion)' is switched Motion Then Resource 'Device Notification' Else - No Actions - (To add one, press 'Action')