Bumbershoot

Kinda like the confusion that people have run into thinking they could simply reuse the cable they've been using between the serial PLM and ISY994... Those ports must be for some future expansion?

No, I don't think so. The Polisy's network cards have different MAC addresses (not even of the same manufacturer, it appears), so they'll present themselves to your network as completely different devices. As I understand it, your DHCP server might have issues if you use the same IP address for two different MAC addresses, though there's no doubt some networking kung-fu that would allow this to happen. EDIT: I think the ISY software just uses the underlying operating system's network services, and it doesn't care (or maybe even know) which interface it is.

FWIW, my WiFi router handles DHCP reservations for both ethernet and WiFi. When I switched to using WiFi for the Polisy, I just looked up the Polisy in the DHCP table on my WiFi router (it advertised itself as POLISY in the table with a different MAC/IP address than what is used for ethernet). I manually added it to the finder at the new IP address, IIRC. I now have static DHCP reservations for the Polisy whether it's connected via ethernet cable or via WiFi. The PG2 interface is interesting/difficult, but I certainly got it to work reliably -- I switched network interfaces at least three times over a couple of days when migrating off the ISY994. In production, my Polisy stays on a wired network connection. It works.

I'm not currently using this technique, but it worked well in the past. https://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking#Dynamic.2FCustom_Page_Creation I created a csv file and appended data to it as necessary, making it more useful than a simple log file. I haven't tried this on Polisy, however.

I believe HomeSeer HS-WX300 dimmers/switches have that capability when set in "Normal" mode. I have an older model that I use in "Status" mode, which makes the onboard LED's vastly more useful than the LED's in Insteon dimmers/switches.

I didn't know about this. I set up a routine that's using this function, and so far, it works beautifully! Thanks for sharing the idea!

That's doable with Z-Wave. I have a couple of these: https://www.amazon.com/GoControl-GD00Z-8-GC-Z-Wave-Security-Black/dp/B085LKPHK6/ref=sr_1_3?keywords=GoControl&qid=1652372776&sr=8-3 Combine that with a geofence, and you're good to go: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Node_Server_Occupancy_and_Locative_app_Instructions

I wonder if the PLM Pro is this, finally going to see the light of day?

Do you have your device (Tempest) added to the configuration? Key: your Station ID; Value: local Token: the token from "Data Authorizations" from the Stations on the web page of your station

You might need to restart the Admin Console to get the nodes to appear and populate.

I don't think so, but below is a screenshot of what's available. Here's a link to the Jishi Sonos API, so I suspect if what you want isn't there then Sonos might not support it.

All is working. It took a couple of bounces of the AC for the phrases to populate, but they're working and the performance seems to be good. Thanks again for this!

UDI did produce a PLM at one point, and a few prototypes are in use (I think Michel wrote somewhere that he still uses one in his home). Apparently, Smarthome decided against selling the necessary chips to UDI at the last minute, so it was never produced at quantity.

FYI - for anyone running reports using the soil moisture sensors, the reporting node (substitution variable) has changed in the PG3 version. In the PG2 version, the variable MOIST would produce data in an emailed report (this example assumes that the EcoWitt Node server is installed in slot 5): ${sys.node.n005_wh51_1.MOIST} In the PG3 version, the substitution variable has changed to ST: ${sys.node.n005_wh51_1.ST} You'll need to edit your reports. BTW, thanks @simplextech for the updated Node server!

Likewise for me. There are many other paths I could have taken besides Ring, but I got exactly the functionality I needed along with easy integration. I've recently helped other users migrate from the Insteon Hub to a Polisy, and would like to recommend Ring to them as the grow their installations, but only if it integrates with the UDI environment. @Michel Kohanim, any way we could help with this?

I just bought a Windows 10 PC simply to run Elk RP2 on for $145. Nice little unit, too.

It does/did have support for the cameras as motion sensors. I have a bunch of programs that use them. I'm eager to have the Ring Node server put back in action...

Bravo, kind sir! I just ran a test and it does indeed work!

No. You'll need one of these if you don't have the original that shipped in the box with the serial PLM https://smartenit.com/shop/plm-serial-cable/

1 - No need with Insteon, just restore a recent backup. 2 - Polyglot 3, if the required node servers are available. I'm running both at the moment, and will migrate to PG3 as additional node servers become available. 3 - Yes, just import a backup. 4 - The serial PLM cable you're using from your ISY won't work with Polisy. You need the original cable that shipped with your PLM. A USB PLM will work with Polisy if you have one. There are some small differences in the way the ISY software handles things on Polisy, and the ISY software is still under development. It generally works just fine, however.

Seems odd. All I can imagine is that the Z stick isn't properly seated in the USB slot or possibly Z-Wave support has been unchecked in the configuration tab.

I used one, and it worked just fine. I had one compatible smoke detector, but it relayed all test alarms from any of my other hardwired smokes. I used it to shut off HVAC and turn the house lights on. I didn't have a compatible CO2 alarm, so I can't speak to that.

For me it did. I moved all my Z-Wave devices over from the ISY994 to IoP using the Remove/Add menu items. Remember, if you're going to add a Z-Wave device that is already enrolled with another controller, you have to remove it before you can add it again. You can remove it using IoP even if it was added using another controller.

I don't think this causes any issues (works for me). I understood that this error will persist until UDI gets Z-Wave 700 certification and their firmware gets updated to reflect the certification.

I took a spin at this (just the "key" with no "value" in the configuration) and I can't get it to work, either. Setting the log to "debug" results in the following in the log: 2022-05-03 07:02:48,237 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getAll 2022-05-03 07:02:48,239 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getAll 2022-05-03 07:02:48,242 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: load {'change_no_pon': ''} 2022-05-03 07:02:48,244 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2022-05-03 07:02:48,244 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking change_no_pon / 2022-05-03 07:02:48,245 Command udi_interface.interface DEBUG interface:_handleInput: Key nsdata should be passed to node server. 2022-05-03 07:02:48,246 Thread-1 udi_interface.custom DEBUG custom:clear: CUSTOM: Clear ...saving 2022-05-03 07:02:48,247 Command udi_interface.interface DEBUG interface:_handleInput: Key oauth should be passed to node server. 2022-05-03 07:02:48,248 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2022-05-03 07:02:48,251 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {}}]} The github repository for the PG3 version isn't linked to on the PG3 store page, and I can't find it, so I don't know where else to look. A ticket with UDI might be the best route forward with this.