Bumbershoot

They do, although it's in the "Last Chance" area of their website. $99 USD.

I wrestled with several Sonos installations on mesh networks, and one solution has worked every time -- add a Sonos Boost. Otherwise, I understand that if one of your Sonos speakers has a wired network connection, it solves the problem, but I can't speak from experience.

@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.

That's not something I've ever tried, though I suspect the result of trying to make that work will be some sort of pain. Your existing devices don't know anything about the new PLM, and vice versa, so you'll have to delete devices from your existing network and install them in the Indigo setup. If you have a test jig and a spare Insteon device, then you might use that combo with your Indigo setup, keeping the two Insteon networks separate, otherwise, I see some factory resets and reinstalling Insteon devices in your future. I don't think a PLM will interfere with a device that's not in it's link table, but I don't know...

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')

I don't use it, but in my YoLink node server configuration, I have an empty slot for "TTS0", and "NBR_TTS" has a value of "1". Just guessing, but have you tried putting some text into the "Value" field of the "TTS0" key? You might try entering some text there, restart the node server and possibly the AC and see if you have a value you can pick in the AC. I suspect that the "NBR_TTS" value in the configuration will indicate how many TTS (text to speech) nodes you want imported into the AC, and the TTS(0,1,2,3,etc.) value gives a distinct name for each TTS node. As I said, I don't use this so it's just a guess...

I know you need a Ring account to link with the node server, but I don't think you need a subscription to the protect plan. I see that the node server has a free trial account, so nothing would be lost to give it a go and find out. The motion detection of the doorbell and cameras works well and is quite useful.

I just purchased/installed it, and all my Ring cameras and doorbells are now available in IoX. Very glad to see this happen. @Geddy, will there be a sub-forum created for this node server? Thanks @bmercier! The previous iteration of this node server was rock solid.

FWIW, I do exactly that using three existing node servers: ST-EcoWitt, Weatherflow and Rainmachine. The EcoWitt moisture sensors are going on their third season, with only one failure. I've found them to communicate reliably over pretty good distances (more than 125 feet), and I've only changed the batteries once. The only downside is that a EcoWitt Gateway is required, but that's enabled me to add some additional sensors, such as this air quality sensor, which is far less expensive than Purple Air sensors. This integrates into my HVAC during fire season. This sensor is solar powered, and I've never changed the rechargeable batteries on this. Thus far, I've been very pleased with the EcoWitt sensors. Inexpensive and solid.

As a dimmer, they work exactly as intended for my purposes. These things are in a bathroom and closet, so my use cases for them are fairly simple and I haven't exercised every possible use case I can think of, i.e., I don't know if they audibly beep, etc. I haven't installed the Dial that will be used as an on/off switch yet, but when I put it in my test jig, it worked.

I'm running on an eisy, and I just upgraded. Can't answer your questions, though.

Odd, I'm able to adjust the ramp rate. I have mine set on 0.5 seconds, and I can change it. I do notice that to get the green "Writing" icon to quit displaying I have to toggle the dimmer on/off from the AC, then the icon goes away and the ramp rate is set properly. I haven't tried the backlight yet, as I'll likely never change it due to where these dimmers will be located.

I had a replacement sent after some sensor failures, but that was in Feb. '22. I had to occasionally reboot the unit that failed, but I haven't had to do it with the latest one. I've had a few data failures (the RSSI between the hub/Tempest is normally -77), but I've never had to reboot this one. I've just restarted the hub and waited a while. The data very occasionally drops/returns by itself, for reasons unknown.

Bug Fixes Insteon I3 Dial status not updated after turning dial Tested, and now the status is updated correctly. I have six of these things to install, replacing Zooz Zen77's.

@bpwwer, this is the first indication I've seen that the Ring node server may come back to life. If it's true, then I'm very pleased to hear it!

I make a backup of IoX every time I make changes, so I can likely survive an IoX update that doesn't go well fairly easily. However, upstream FreeBSD package updates can now break things in ways that would never occur on the ISY994 - node servers seem particularly vulnerable to this - so I'm very much in favor of some sort of update management that UDI, and only UDI, control the content of. Disallowing (or at least not supporting) command line updating has been a good start. For my particular purposes, once IoX reaches feature stability (after Matter is enabled and hopefully settles down), then I'd suggest an option for automatically updating outdated installations to one version behind current after a new version is released, in order to maintain free support. By this I mean IoX/PG3x versions, not FreeBSD versions. It would be up to UDI to manage the host OS. This would put the onus on people to either maintain a Portal account or update their systems periodically, which would no doubt cause some users untold anguish and cause others to abandon the platform. Personally, I don't expect UDI to support every outdated version of IoX/PG3x/FreeBSD that was released, forever. That's crazy. At some point, for some folks, there'll be some pain. For remote installations that do not maintain an Internet connection, or for installations that just fall behind, then some sort of paid update service wouldn't be a terrible idea.

This has been going on ever since the move to FreeBSD/Polisy:

There's a menu item in IoX/ISY: Tools | Generate Topology that might provide you with what you're looking for. I don't think that Z-Wave is as smooth as Insteon for lighting, but you can create associations between dimmers/switches that are useful, though they're limited in number and coordination between the devices is nowhere near as graceful as with Insteon IMHO. I've tested the i3 dial, and it's not yet fully supported by IoX (though UDI indicated that they'll provide support soon). I have an i3 paddle on order, so I'll test that as well. I don't have any information as to how strong the RF communications are on these new devices compared to the old devices, but they're still dual mode, meaning they still use power line communications as well as RF. New PLM's are due shortly from Insteon, and they've made noises about an upgraded PLM, possibly due later in the year.

For the i3 dial and paddle, each device can be configured as either a switch or a dimmer, and they will be firmware upgradable (at some future point).

I don't understand Z-Wave nodes all that well, but I suspect that the node you're trying to report on doesn't support an "ST" value. When you use the X-Ray utility, select "Node Info" instead of "Node Definition" on the device, and look between the <properties> ... </properties> tags (if it has any) for the property id to query. I don't have one of the devices you're asking about, but I think I'd have to use the "CLITEMP" property if I wanted to report on the temperature reported by my Z-Wave multi sensor. <properties> <property uom="51" formatted="100%" value="100" id="BATLVL"/> <property prec="1" uom="17" formatted="63.5&#xb0;F" value="635" id="CLITEMP"/> <property uom="36" formatted="0 lux" value="0" id="LUMIN"/> </properties>

There is. See this page in the wiki: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking#Dynamic/Custom_Page_Creation In the example below, the values from a couple of moisture sensors are inserted into a csv file.

It looks like minor UDX/IoX updates dropped (along with 100 FreeBSD updates). No idea what the changes are. Installed packages to be UPGRADED: udx: 3.3.9_1 -> 3.3.9_2 [udi] Installed packages to be UPGRADED: isy: 5.5.9 -> 5.5.9_1 [udi]

https://shop.insteon.com/products/i3-paddle

I gave my i3 Dial a quick run in my test jig last night (running 5.5.9 on an eisy) and no data was presented in the Event Viewer when status was changed at the device. Actually, I didn’t notice any change in behavior from 5.5.7. I’m delighted that UDI is working on supporting these devices, however.