Bumbershoot

If you haven't done so yet, the bios on that machine will most likely not have been upgraded to EUFI. 6 successive presses on the front panel button will force an upgrade to EUFI. I think that the 'udx' service now requires that. Probably best to open a ticket, however.

After the upgrade to PG3 3.0.61 I gave the Node server a restart and noticed this error in the log during discovery: 2022-04-29 05:11:51,720 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: failed d073d56be801.runCmd(SETB) list assignment index out of range Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 793, in _handleInput self.nodes_internal[item['address']].runCmd(item) File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/node.py", line 155, in runCmd fun(self, command) File "./lifx-poly.py", line 574, in setManual self.color[2] = _val IndexError: list assignment index out of range 2022-04-29 05:11:51,801 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: failed d073d568e354.runCmd(SETB) list assignment index out of range Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 793, in _handleInput self.nodes_internal[item['address']].runCmd(item) File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/node.py", line 155, in runCmd fun(self, command) File "./lifx-poly.py", line 574, in setManual self.color[2] = _val IndexError: list assignment index out of range The Node server seemed to function just fine. A second restart several minutes later did not result in this error. I'm am not using a 'devlist.yml' file in this instance.

This is a newer suite of programs than I'm running, but they are very similar. I would say yes, set them up this way. Once you get one or two set up, give them a test by activating a sensor.

All Insteon leak sensors here, and I've been using these programs for at least six years. Flawless. I found these programs here on the forums. They're a bit of work to set up, but they've been 100% reliable. No real leaks, though, but the programs get exercised occasionally from housekeeping.

I might have taken this a little too far, but I put a color LiFX bulb in the water closet, and I dim it very low and change the color to red - like a darkroom - so as not to hose our night vision when we come out. This keeps us from stumbling around in the bedroom. This has a high WAF, surprisingly.

That makes perfect sense. Kind of gets down to how nodes are defined, but I agree with you. 232 devices, many more nodes.

Sorry, it's less than that: How many devices (nodes) can be included in a Z-Wave network? A Z-Wave network can handle a maximum of 232 devices (nodes), including the primary controller. https://www.clarecontrols.com/helpcenter/z-wave-faqs

Not a PG3 expert, but leaving the group and user doesn't do anything bad to the OS. They'll just be reinstalled later with you install PG3 again. Likely, these entities are just a line in a couple of files (/etc/passwd and /etc/group) and possibly a directory (/var/polyglot). I've uninstalled/reinstalled PG3 a couple of times to no bad effect. Of course, YMMV.

I'm not sure there'd be a benefit of excluding/including a device to force a new path. For one thing, the Z-Wave device number would change, which could break things in already established programs and scenes (Z-Wave won't reuse a device number until it gets to *I think* 255, then it'll start over at 2). I think the Update Neighbors tool is meant to achieve this. If you want to see what the path is, what neighbors the device sees, you can get it from the context menu of the device and have the data printed to the Event Viewer 'Z-Wave | Show information in Event Viewer' (in this case, the device is talking directly to the controller, about 35 feet away): Wed 04/27/2022 15:03:12 : [ZW-SHOW ] ---------------------------------------------- Wed 04/27/2022 15:03:12 : [ZW-SHOW ] Last working route from ISY to Node 10 - ZW 010 Dimmer SwitchOffice Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Direct Wed 04/27/2022 15:03:12 : [ZW-SHOW ] Wed 04/27/2022 15:03:12 : [ZW-SHOW ] Node 10 - ZW 010 Dimmer SwitchOffice has the following neighbors Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 1 - [This ISY] Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 2 - ZW 002 Guest Dimmer Switch Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 3 - ZW 003 Multilevel Sensor - Ea Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 5 - ZW 005 Siren Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 7 - ZW 007 Garage Bench Switch Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 8 - ZW 008 Laundry Light Switch Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 9 - ZW 009 Office Motion Switch Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 11 - ZW 011 Office Plug-in Dimmer Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 12 - ZW 012 Garage Door East Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 14 - ZW 014 Garage Door West Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - - Node 18 - ZW 018 Schlage Door Lock Wed 04/27/2022 15:03:12 : [ZW-SHOW ] - Repeater - Node 19 - ZW 019 Water Cop Wed 04/27/2022 15:03:12 : [ZW-SHOW ] Wed 04/27/2022 15:03:12 : [ZW-SHOW ] ----------------------------------------------

The reboot isn't too bad, much faster than the ISY in my case. I already had Z-Wave devices installed, so otherwise, I'd be removing door locks and messing around in the crawl space of my house to get the devices excluded/included. Moving the Polisy around using WiFi for the network was vastly easier for me. YMMV.

Once you get the device included in your Polisy, you can right click (context menu) on the device and choose "Z-Wave | Update Neighbors".

I bought a Polisy Pro, and put it on my WiFi when I did my migration. That way I could move the Polisy to close proximity to my locks, etc., in order to perform the Z-Wave exclude/include. Newer and many powered devices support network wide inclusion, so you might be able to leave the Polisy in it's permanent location for those.

IIRC that the SSH connection will terminate prior to the completion of an orderly shutdown, so I'd still wait a bit before unplugging after the network connection drops.

You've basically gotten the concept. When you start the Admin Console on your Polisy, it'll look nearly exactly the same as it did on your ISY, even after you've migrated your setup from the ISY to the Polisy. No worries there. Polyglot will also be running, and if you don't currently have node servers, then you'll only need to look at it to perform some admin functions on the box itself (though you can actually do the same stuff with a bent paper clip inserted into a little port on the front of the box). Polyglot (the Node server interface) is accessed through your web browser.

When I start the AC, and open up the Event Viewer, I find this line: Mon 04/25/2022 06:45:36 : [ZWAVE-FW ] Unrecognized Z-Wave firmware version/library [7.17] If you need a more granular report than that, I don't think the telnet interface will provide you with much. IoP may have a much more robust telnet interface (though I doubt it).

That's exactly my plan as well. I have 11 irrigation zones of various plant/soil types, but with record cold temperatures this month in the Pacific NW, I haven't had a chance to run the irrigation system much. Thanks for the reply.

I haven't paid Flume a single ¢ since I bought the thing, and the API has always been accessible. The accuracy seems astonishing to me as well, as the reported monthly water usage have been only a couple of gallons different from what my utility sees, and this is without device calibration. I'm impressed with this device, so far, and it works well with the Flume Node server. @hart2hart, are you getting value from the subscription?

I found the IPv4 Networking settings in PG2 to be a bit confusing. IIRC, you have to make certain that the WiFi interface in actually turned on. Just removing the ethernet cable and restarting the Polisy won't do it. In any event, I got it to work when I needed it. Other than that, I've switched back to using a wired network...

The command 'ifconfig -a' will get you the MAC address of the interface, if it's active, which you can then look up in your router tables once it's connected. You might be able to copy that and make a static DHCP reservation in your router before restarting the Polisy to use the interface, as well. I just looked it up once Polisy WiFi was connected. YMMV.

You can always use the 'netstat' command, but it won't show an inactive interface without in IP address. In my router, it showed up as 'POLISY' if I recall. The interface isn't active, so I can't check.

It's in the PG2 interface. It has to be coming to PG3, but I guess it's not there yet.

WiFi does work. I used it when I repositioned my Polisy to get it closer to some older Z-Wave devices for exclusion/inclusion.

The only 'gotcha' with doing this is that if you've already migrated your Insteon devices, you'll get lots of pop-up notices in the AC about unavailable Insteon devices unless you also plug in a PLM (I used a spare) or turn off Insteon support in the AC prior to the restart. Not a big deal, but something to note.

I did find an advantage of having a Pro when I migrated. I had some Z-Wave devices in difficult locations that I could not exclude or include from the default Polisy location, and I didn't have a long enough ethernet cable to move the Polisy closer. The solution was to enable WiFi on the Polisy, and move the Polisy close to the Z-Wave devices to enable exclusion/inclusion. These devices are older devices such as Schlage locks, etc. Worked like a charm.

EDIT: This isn't a fatal error! The Node server is running as designed, as far as I can tell. I've deleted the PG2 version, and installed the PG3 version, but it errors on startup: 2022-04-18 07:18:46,691 MainThread udi_interface.interface INFO interface:addNode: Adding node WirelessTagsController(wtcontroller) [None] 2022-04-18 07:18:46,694 MainThread udi_interface.interface INFO interface:setController: Using node "wtcontroller", driver "ST" for connection status. 2022-04-18 07:18:46,884 Thread-6 udi_interface ERROR Controller:handler_nsdata: NSDATA is a string? Are you running a local copy? data=undefined Thanks for whatever insight you can give, or, I can just ignore it...