simplextech

Yup.

PLM is still required for Insteon. Does not matter what control system. Whether it's Polisy, HomeSeer, Indigo, etc, etc. Insteon requires PLM for controller communication. Granted there is possibility to use the USB Insteon interface if you can still find one. This method only provides wireless access to Insteon devices so you lose all benefit of powerline communications.

It's going to take me some time to move devices around and setup a test environment for RA2 Select again. I also don't think this should be continued in this thread under this sub-forum.

The preferred method for any life/safety devices are to use a security panel. A common favorite is Elk. If you do not have a security panel or don't want to purchase one the next option would be Z-Wave Smoke detectors. The current (only?) Z-Wave smoke detector is the First Alert ZCOMBO which is a Smoke/CO detector. I in fact have several of the First Alert ZCOMBO that I've recently retired as they were replaced with Smoke detectors connected to my Elk panel.

v1.0.6 Updated Node.js PolyInterface Log Level selection from UI now works User configuration values are no longer necessary. v1.0.2 Typo correction in a message v1.0.1 Bug fix for ISY returning /CONF/NET/RES.CFG not found for network resources URL v1.0.0 Initial release of ISY Inventory (now ST-Inventory) for Polyglot 3

If it's deleted from PG but still showing in the ISY then delete it from the ISY NodeServer menu. Node Servers -> Configure -> NS to delete -> Click it to open the menu -> Click Delete

I've seen that error before when PG3 does not shutdown a nodeserver properly or the node process is not removed when the nodeserver crashes for some reason. You can login to the Polisy and kill the node process and then start the NS or just reboot.

When posting logs use the "code" format otherwise they are unreadable. Text file attachment is best. Did you configure the nodeserver with the IP Address and Admin user/password for your ISY?

Yes it takes you to the Simplex Technology website. The nodeserver is not a public repo hosted on GitHub. Documentation will be maintained on our website or other method. Considering using Readthedocs for nodeservers for ease of maintenance.

Looks like the trial period option of "week" is not valid on the backend. Yet the option is presented in the web UI when adding the nodeserver. I'll change the trial period and see what happens.

No you don't have to. I was intending to use the responses as a method to prioritize development of what people are actually using. BTW - I pushed ST-Inventory for PG3. I've seen a lot of talk. Talk doesn't buy whiskey

I'm guessing then you like RA2 Select nodeserver? I setup a poll a few weeks ago about NodeServers to be ported and had very. very. little reply.

"Soon" is a relative thing. It is planned.

I rack mount everything so a rack mount bracket would be nice. I put a shelf in my rack for now.

The NodeServer presents Hubitat devices status/control to the ISY for use. It does not present ISY devices to Hubitat.

I agree with this. V 5 is the "official" every other version would be a feature or minor/patch update. 5.x.x = Major 5.3.x = Feature 5.3.x = Patch

In a takeover where the customer already had Lutron. Or a customer that prefers Lutron over C4 switches (queue @lilyoyo1).

Then I will stand back and let UD support handle this. I'm just going based on memory of previous Z-Wave testing.

With Insteon if you have multiple dimmers in a Scene and you turn them on/off/dim/bright the action happens to all devices simultaneously. This is not the case with Z-Wave because Z-Wave is a serial protocol sending commands one at a time to each device. This is where the "popcorn effect" term comes from. You can visually notice the on/off of lights not being at the same time. The more devices you try to control in unison with Z-Wave the more prominent the popcorn effect becomes.

What devices are you trying to use for a Scene? Generally Dimmers, Switches, work fine in a ISY Scene for common functions of on/off/dim/bright. However you won't get the full Insteon functionaity from Z-Wave devices inside a Scene. You also won't have synchronized lighting control with Z-Wave like you will with Insteon as the Z-Wave protocol doesn't have a multicast or group functionality (yet).

Z-Wave Associations are a device to device association and requires a controller to configure those associations. Setting up a ISY "Scene" is not the same thing. As far as I know currently the ISY does not support setting up/managing Z-Wave Associations. The Z-Wave protocol does not support "Scenes". You will find "Scene Controllers" which are usually keypads or buttons made with the intention of use with direct associations.

As was previously mentioned HomeWorks is different system. What was does with Ra 3 though was to combine the software into a single package. Previous there was a Designer software for HomeWorks and a different software for Ra 2. It's actually really nice they are now just combined. As for device pricing send me a PM with what you're looking for. Lots of scalpers out there currently due to the low supply.

The NodeServer does not support *All* devices that Hubitat does. Device support can be added. It does not pull any settings or configurations of the devices. It integrate the devices from Hubitat for usage within the ISY. The devices within Hubitat are configured and owned by Hubitat but the status and control of devices is available from the ISY for use in programs also known as events or "rule" in Hubitat. The current version of the Hubitat NodeServer is available for Polyglot V2. Polyglot V2 can run on a raspberry Pi or the preferred option is the Universal Devices Polisy. All Simplex Technology Nodeservers are being migrated to Polyglot V3. At which time the Nodeservers will have a price associated with them (to be determined) and those NodeServers will only run, be available for Polisy.

There is a NodeServer for integrating Hubitat with ISY. This is not a bi-directional connection between the systems. The intent is to make Hubitat devices available to the ISY as nodes for use in programming. Original intent was to bring ZigBee devices to the ISY and it has grown to provide access to a larger amount of devices.

Welcome.