kzboray

@Envirogreen, Just an idea. I use a Volimo Primo for streaming, it's similar to the Sonos and unless I have a play list loaded either via the web interface or my phone, Just sending a play command isn't enough information for the player to start. I'm not familiar with the Sonos system so I don't know if the NS allows you send a playlist selection command first. Something to try. Also as i recall there are two different Sonos NS's one in the local NS store and another in the https://polyglot.isy.io store. You might try the other one and see if you get different results.

@Gunn This write up applies to V4x software, for V5x see the second post below this one. Great write up! This problem has a simple solution! Select the Insteon scene for Fan OFF, in the bottom half of the screen you will see a couple of buttons and a pull down. Change the protocol to Insteon and the pull down to OFF. Now click on UPDATE. Do this same thing for each scene with the appropriate value (OFF, MEDIUM, HIGH, LOW) and you should be all set. If you look at all your scenes you will see that their status is listed as HIGH. You want this value to reflect the speed you want for each scene. As far as the button toggle I think you'll find TOGGLE works better. That way a button is either on for a selected speed or off if another speed has been chosen. You can also look at BUTTON GROUPINGS to make sure all buttons are setup correctly. You only want the button for the speed you are selecting ON and all the others should be OFF.

@ewind Polisy HW is the current / future replacement for ISY994i? Future. ISY on Polisy is in beta and being tested, that being said it's better than a lot of released software I've used. ISY programs and devices can be imported to Polisy, and ISY can be unplugged? The migration tools for ISY994i to Polisy ISY are going to be released soon. Probably before the end of the year. Polyglot on board or Polyglot cloud or both is the future software repository? I want to be careful here as some Node Servers access cloud based device accounts i.e. Hue, LifX,Ring, Sonos etc Polyglot Node Servers for PG2 are available via a store which is accessible in two ways. First via the local Polyglot web interface: https://the IP address of your Polisy And via the web at: https://polyglot.isy.io/ Some of the available Node Server are duplicated in both stores, and the opposite is also true. Some of the Node Server currently available can only be found in one or the other, not both. PG3 will continue this evolution to an online store making installation of new Node Servers available by simply clicking on the Node Server you want to install and use on your Polisy. Is Z-wave native on Polisy or does it require a USB adaptor? You will need to purchase a Z-Wave adapter. UDI is testing on a Zooz 700 z-wave plus (S2) adapter. It is available from Amazon: Zooz 700 Plus Does Serial PLM plug in directly? Both the serial using the cable provided with your serial PLM and the USB PLM plug directly into the Polisy. Is there anything the Polisy Pro offers besides Wi-Fi & Bluetooth? I'm not sure what you're really asking. Maybe a read of the product page will help: http:// https://www.universal-devices.com/product/polisy-pro/ If I have a healthy Ethernet network what would Wi-Fi & BT benefit other than laternate network paths? If you are using Wi-Fi connected devices that a Node Server talks to...say a LifX light bulb then a healthy Wi-Fi network is required. There are currently no supported devices for the Bluetooth receiver.

@Michaelv What Larryllix was getting at is that the behavior you are describing normally is related to a program that is turning on/off your devices. There is also the possibility that you have something set to "Run at Startup" Check in your program Summary page. By disabling the programs you can quickly determine if there is a program responsible. If that is the case then simply enable them one at a time until you find the one responsible. Then you'll be able to change it to suite your desired outcome.

@TechmanThank you for that update. I should have checked before I posted the links!

@SLP The Power Link Modules come in two flavors. USB or Serial connection. Here's the link for both, but only the USB version is available atm. There is a thread talking about the probable future availability of the serial version. Bottom line it's going to be a long wait for the serial version and since the USB works fine with the Polisy, you shouldn't have any difficulties. USB PLM Serial PLM Amazon USB PLM

@SLP You can use either the serial or USB PLM with the Polisy. Also Michel mentioned early this week that they would have an ISY / NS migration tool available soon. So if you order a Polisy, by the time you get it, you might be able to just migrate your current config with a little TLC to some z-wave devices and programs.

@someguy Bring up the windows task bar and in the search window type in <cmd> That will bring up the Command Prompt window. Now in that window type in: ssh admin@The IP address of your Polisy Your IP will be different than mine listed above, I am just showing you that as an example of what you should be typing and what you should see. Once you have opened the SSH shell for the first time you will be promoted to accept the key. Type yes and you can now SSH to your Polisy. Now you will need to type in the Polisy admin password which by default is admin. You should then see this screen. At this point you are ready to start updating your Polisy. Copy and past the first line below, then when that has completed, copy and paste the second line and then allow 10minutes for your Polisy to completely update and reboot. curl -s https://pkg.isy.io/script/update121.sh | sudo bash sudo shutdown -r now Once it has fully rebooted, you will need to open a new SSH Command prompt. Follow the same procedure as list above, however this time you won't be prompted to accept the key. This is normal, that only happens the first time you SSH to a new device. Now that you are connected to the Polisy once again via SSH, copy and paste the following one line at a time again. cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now You will once again have to wait while the Polisy updates and reboots. Once this update has been completed you should be able to simply use the Polisy web interface to update. When you start Polyglot for the first time, https://the IP address of your Polisy You will be warned that the certificate is invalid and advised not to proceed to the web site. This is normal. ignore the warning/s and proceed. The steps to ignore the warning vary by web browser and antivirus software installed. Read the prompts and proceed past the warnings.

UDI has exceptional support, you should hear something as soon as someone is awake.

OK, so the problems not with the Insteon devices or with the ISY. It's either the HomeBridge or Homekit. That being the case, there may be someone here that can help, but you might want to post on the HomeBridge and Homekit forums as well. I'm not a HomeBridge guy so this is as far as I can go. Good luck!

@Venicenerd First I would ask, are you able to control multiple devices directly from the ISY?

I often have issues with the LifX NS finding the LifX devices after a Polisy reboot. It takes me a lot of fiddling before I get the NS to find the LifX devices again. So far I haven't been able to determine exactly what I need to do to enable the NS to find the LifX devices again after a Polisy reboot so I haven't put in a support ticket. I'm not sure if it's a local issue, or something with the NS or Polisy itself. What I have found some success with after a reboot of Polisy is to remove the NS completely, reboot my router and then reinstall the LifX NS before it will see the LifX devices. Rebooting the router seems to be part of the solution, although there are address reservations for each LifX device on my network so I'm not sure why a reboot of the router should effect the NS's ability to see the devices. Even this doesn't always work and I end up repeating this process a couple of times, beating my head against my desk a few times and usually going to lunch before it starts working again. While the LifX NS can't find the LifX devices. Home Assistant never has any problems seeing them so I'm pretty sure it's a NS issue. The furthest LifX device is only 12' from the router so it's not a signal strength issue. Working LifX NS Discovery Log: 2021-12-08 10:10:30,862 MainThread polyinterface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2021-12-08 10:10:33,163 MainThread polyinterface INFO polyinterface:init_interface: Received Config from STDIN. 2021-12-08 10:10:33,164 MainThread polyinterface INFO __init__:<module>: UDI Polyglot v2 Interface 2.1.0 Starting... 2021-12-08 10:10:33,449 MainThread polyinterface DEBUG polyinterface:get_network_interface: gws: {'default': {2: ('10.0.0.1', 'igb0')}, 2: [('10.0.0.1', 'igb0', True)]} 2021-12-08 10:10:33,450 MainThread polyinterface DEBUG polyinterface:get_network_interface: gw: default=('10.0.0.1', 'igb0') 2021-12-08 10:10:33,451 MainThread polyinterface DEBUG polyinterface:get_network_interface: ifad: igb0=[{'addr': '10.0.0.55', 'netmask': '255.255.255.0', 'broadcast': '10.0.0.255'}] 2021-12-08 10:10:33,452 MainThread polyinterface INFO polyinterface:__init__: Connect: Network Interface: {'addr': '10.0.0.55', 'netmask': '255.255.255.0', 'broadcast': '10.0.0.255'} 2021-12-08 10:10:33,454 Interface polyinterface INFO polyinterface:_startMqtt: Connecting to MQTT... localhost:1883 2021-12-08 10:10:33,489 MQTT polyinterface INFO polyinterface:_connect: MQTT Connected with result code 0 (Success) 2021-12-08 10:10:33,491 MQTT polyinterface INFO polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/ns/3 - MID: 1 Result: 0 2021-12-08 10:10:33,492 MQTT polyinterface INFO polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/connections/polyglot - MID: 2 Result: 0 2021-12-08 10:10:33,493 MQTT polyinterface INFO polyinterface:_connect: Sent Connected message to Polyglot 2021-12-08 10:10:33,500 MQTT polyinterface INFO polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2021-12-08 10:10:33,504 MQTT polyinterface INFO polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2021-12-08 10:10:33,592 NodeServer polyinterface INFO lifx-poly:start: Starting LiFX Polyglot v2 NodeServer version 2.1.26, LiFX LAN: 1.2.7 2021-12-08 10:10:33,597 Thread-1 polyinterface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2021-12-08 10:10:33,598 NodeServer polyinterface DEBUG lifx-poly:start: Start complete 2021-12-08 10:10:36,042 Thread-1 polyinterface INFO lifx-poly:_discovery_process: 9 bulbs found. Checking status and adding to ISY if necessary. I've also tried creating a devlist.yaml file, but when I do that, while the NS populates with all 13 LifX devices, none of them are actually available for control. The error logs just fills up with connection errors. Devlist LifX NS Discovery Log: 2021-12-08 10:17:49,827 MainThread polyinterface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2021-12-08 10:17:51,855 MainThread polyinterface INFO polyinterface:init_interface: Received Config from STDIN. 2021-12-08 10:17:51,856 MainThread polyinterface INFO __init__:<module>: UDI Polyglot v2 Interface 2.1.0 Starting... 2021-12-08 10:17:52,143 MainThread polyinterface DEBUG polyinterface:get_network_interface: gws: {'default': {2: ('10.0.0.1', 'igb0')}, 2: [('10.0.0.1', 'igb0', True)]} 2021-12-08 10:17:52,144 MainThread polyinterface DEBUG polyinterface:get_network_interface: gw: default=('10.0.0.1', 'igb0') 2021-12-08 10:17:52,144 MainThread polyinterface DEBUG polyinterface:get_network_interface: ifad: igb0=[{'addr': '10.0.0.55', 'netmask': '255.255.255.0', 'broadcast': '10.0.0.255'}] 2021-12-08 10:17:52,145 MainThread polyinterface INFO polyinterface:__init__: Connect: Network Interface: {'addr': '10.0.0.55', 'netmask': '255.255.255.0', 'broadcast': '10.0.0.255'} 2021-12-08 10:17:52,146 Interface polyinterface INFO polyinterface:_startMqtt: Connecting to MQTT... localhost:1883 2021-12-08 10:17:52,181 MQTT polyinterface INFO polyinterface:_connect: MQTT Connected with result code 0 (Success) 2021-12-08 10:17:52,183 MQTT polyinterface INFO polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/ns/3 - MID: 1 Result: 0 2021-12-08 10:17:52,183 MQTT polyinterface INFO polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/connections/polyglot - MID: 2 Result: 0 2021-12-08 10:17:52,184 MQTT polyinterface INFO polyinterface:_connect: Sent Connected message to Polyglot 2021-12-08 10:17:52,188 MQTT polyinterface INFO polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2021-12-08 10:17:52,190 MQTT polyinterface INFO polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2021-12-08 10:17:52,237 NodeServer polyinterface INFO lifx-poly:start: Starting LiFX Polyglot v2 NodeServer version 2.1.26, LiFX LAN: 1.2.7 2021-12-08 10:17:52,242 Thread-1 polyinterface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2021-12-08 10:17:52,243 NodeServer polyinterface DEBUG lifx-poly:start: Start complete 2021-12-08 10:17:52,244 Thread-1 polyinterface INFO lifx-poly:_discovery_process: Attempting manual discovery... 2021-12-08 10:17:52,415 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-1(d073d53289b6) 2021-12-08 10:17:52,418 Thread-1 polyinterface INFO polyinterface:addNode: Adding node Vanity-1(d073d53289b6) 2021-12-08 10:17:52,423 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-2(d073d53303bc) 2021-12-08 10:17:52,426 Thread-1 polyinterface INFO polyinterface:addNode: Adding node Vanity-2(d073d53303bc) 2021-12-08 10:17:52,429 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-3(d073d53303cc) 2021-12-08 10:17:52,433 Thread-1 polyinterface INFO polyinterface:addNode: Adding node Vanity-3(d073d53303cc) 2021-12-08 10:17:52,436 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-4(d073d5330c09) 2021-12-08 10:17:52,439 Thread-1 polyinterface INFO polyinterface:addNode: Adding node Vanity-4(d073d5330c09) 2021-12-08 10:17:52,441 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-5(d073d5349cb2) 2021-12-08 10:17:52,446 Thread-1 polyinterface INFO polyinterface:addNode: Adding node Vanity-5(d073d5349cb2) 2021-12-08 10:17:52,448 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found Bulb: Bedroom-1(d073d533d74d) 2021-12-08 10:17:52,450 Thread-1 polyinterface INFO polyinterface:addNode: Adding node Bedroom-1(d073d533d74d) 2021-12-08 10:17:52,454 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found Bulb: Bedroom-2(d073d5340a63) 2021-12-08 10:17:52,457 Thread-1 polyinterface INFO polyinterface:addNode: Adding node Bedroom-2(d073d5340a63) 2021-12-08 10:17:52,461 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found Bulb: DiningRm-1(d073d567165f) 2021-12-08 10:17:52,464 Thread-1 polyinterface INFO polyinterface:addNode: Adding node DiningRm-1(d073d567165f) 2021-12-08 10:17:52,491 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found Bulb: DiningRm-2(d073d567d1dd) 2021-12-08 10:17:52,494 Thread-1 polyinterface INFO polyinterface:addNode: Adding node DiningRm-2(d073d567d1dd) 2021-12-08 10:17:52,510 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Group Vanity, 5 members 2021-12-08 10:17:52,511 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found LiFX Group: Vanity 2021-12-08 10:17:52,512 Thread-1 polyinterface INFO polyinterface:addNode: Adding node LIFX Group Vanity(grp000) 2021-12-08 10:17:52,534 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Group Bedroom, 2 members 2021-12-08 10:17:52,542 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found LiFX Group: Bedroom 2021-12-08 10:17:52,544 Thread-1 polyinterface INFO polyinterface:addNode: Adding node LIFX Group Bedroom(grp001) 2021-12-08 10:17:52,545 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Group DiningRm, 2 members 2021-12-08 10:17:52,563 Thread-1 polyinterface INFO lifx-poly:_manual_discovery: Found LiFX Group: DiningRm 2021-12-08 10:17:52,571 Thread-1 polyinterface INFO polyinterface:addNode: Adding node LIFX Group DiningRm(grp002) 2021-12-08 10:17:52,593 Thread-1 polyinterface INFO lifx-poly:_discovery_process: Manual discovery is complete 2021-12-08 10:17:52,778 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver d073d53289b6 - GV0: -41, uom: 56 2021-12-08 10:17:54,057 Controller polyinterface ERROR lifx-poly:update: Connection Error on getting Vanity-2 bulb color. This happens from time to time, normally safe to ignore. WorkflowException: Did not receive [<class 'lifxlan.msgtypes.LightState'>] from d0:73:d5:33:03:bc (Name: None) in response to <class 'lifxlan.msgtypes.LightGet'> 2021-12-08 10:17:54,059 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver d073d53303bc - GV5: 0, uom: 2 2021-12-08 10:17:55,086 Controller polyinterface ERROR lifx-poly:long_update: Connection Error on getting Vanity-2 bulb uptime. This happens from time to time, normally safe to ignore. WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateInfo'>] from d0:73:d5:33:03:bc (Name: None) in response to <class 'lifxlan.msgtypes.GetInfo'> 2021-12-08 10:17:56,114 Controller polyinterface ERROR lifx-poly:long_update: Connection Error on getting Vanity-2 bulb WiFi signal strength. This happens from time to time, normally safe to ignore. WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateWifiInfo'>] from d0:73:d5:33:03:bc (Name: None) in response to <class 'lifxlan.msgtypes.GetWifiInfo'> 2021-12-08 10:17:56,115 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver d073d53303bc - GV5: 0, uom: 2 2021-12-08 10:17:57,156 Controller polyinterface ERROR lifx-poly:update: Connection Error on getting Vanity-3 bulb color. This happens from time to time, normally safe to ignore. WorkflowException: Did not receive [<class 'lifxlan.msgtypes.LightState'>] from d0:73:d5:33:03:cc (Name: None) in response to <class 'lifxlan.msgtypes.LightGet'> 2021-12-08 10:17:57,158 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver d073d53303cc - GV5: 0, uom: 2 2021-12-08 10:17:58,195 Controller polyinterface ERROR lifx-poly:long_update: Connection Error on getting Vanity-3 bulb uptime. This happens from time to time, normally safe to ignore. WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateInfo'>] from d0:73:d5:33:03:cc (Name: None) in response to <class 'lifxlan.msgtypes.GetInfo'> 2021-12-08 10:17:59,219 Controller polyinterface ERROR lifx-poly:long_update: Connection Error on getting Vanity-3 bulb WiFi signal strength. This happens from time to time, normally safe to ignore. WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateWifiInfo'>] from d0:73:d5:33:03:cc (Name: None) in response to <class 'lifxlan.msgtypes.GetWifiInfo'> 2021-12-08 10:18:00,243 Controller polyinterface ERROR lifx-poly:update: Connection Error on getting Vanity-5 bulb color. This happens from time to time, normally safe to ignore. WorkflowException: Did not receive [<class 'lifxlan.msgtypes.LightState'>] from d0:73:d5:34:9c:b2 (Name: None) in response to <class 'lifxlan.msgtypes.LightGet'> 2021-12-08 10:18:00,244 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver d073d5349cb2 - GV5: 0, uom: 2 2021-12-08 10:18:01,275 Controller polyinterface ERROR lifx-poly:long_update: Connection Error on getting Vanity-5 bulb uptime. This happens from time to time, normally safe to ignore. WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateInfo'>] from d0:73:d5:34:9c:b2 (Name: None) in response to <class 'lifxlan.msgtypes.GetInfo'> 2021-12-08 10:18:02,347 Controller polyinterface ERROR lifx-poly:long_update: Connection Error on getting Vanity-5 bulb WiFi signal strength. This happens from time to time, normally safe to ignore. WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateWifiInfo'>] from d0:73:d5:34:9c:b2 (Name: None) in response to <class 'lifxlan.msgtypes.GetWifiInfo'> 2021-12-08 10:18:02,687 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver d073d533d74d - GV0: -40, uom: 56 Any suggestion? Thank you!

@Michel KohanimIt an ISY994i Pro attached to a Polisy Pro. ISY994i Pro: 5.3.4 LifX NS - 2.1.26 Polisy: FreeBSD 13.0-RELEASE-p4 (POLISY) #13 releng/13.0-n244760-940681634ee: Wed Aug 25 UDX - 2.5.3_2 ISY - 5.2.0_58 Thank you Michel!

@sjenkins You are not alone. I just checked the portal and sure enough the Polisy is listed, but not available. From the local Launcher LAN and Cloud both work fine.

I've been playing with HA a bit as well for the last 10 days. I have one bathroom with 5 LifX bulbs and a single Insteon Keypad Linc Switch that I decided to use as a test. So far I have created two scenes, one for on and the other for off. I haven't figured out how to create a scene for a LifX group yet so the scenes simply tell all five bulbs to power on or off. Now keep in mind this is Insteon interfacing with LifX, or in the UDI world it would be an ISY talking to a Polyglot NS. What I have found is that the HA solution is much faster in responding to the switch being turned on or off. With the Polyglot NS it could take 2 or three seconds for the LifX bulbs to respond to the switch being turned on or off. With HA the bulbs respond instantly, or in milliseconds since I can't perceive a delay. This is doubly impressive because the HA scene is actually commanding each bulb individually as opposed to the Polyglot NS which is able to active the LifX group natively. But, as I play with HA I am more and more impressed with UDI and what they have created with the ISY and Ployglot servers. Things that are easy to do on an ISY require programming in HA. Something as simple as dimming the LED brightness of the Keypad Linc necessitates programming in HA. I'm a total newb with HA and have years of experience with ISY's and Polyglot servers, but I can already see that HA is going to require an entirely new set of skills and for advanced capabilities it's going to take learning the programming language of HA to move forward. Yuck, yet another language to learn. I am not a programmer, but I can usually follow someone else's work and make changes if I need to. That was what attracted me to the ISY in the first place. It's programming is simple but incredibly powerful. ISY / Polyglot works really well for the most part. My girlfriend is loving the responsiveness of the bathroom lights, but misses the circadian lighting routines that turned the lights red and set their power levels very low between the alarm being set at night and disarmed in the morning. It's been four days since I changed from ISY / Polyglot LifX NS to HA in that room and already she wants the old system back, even with the responsiveness being so dramatically different between them. So for me HA seems to be much faster than the ISY / Polyglot NS for LifX / Insteon integration and control but less friendly to setup and manage. It will be interesting to see what the more advanced and experienced HA users have to say.

Upgraded yesterday and was unable to access the Polisy ISY from launcher. Tried reverting to 5.1.1 and still couldn't get it to work. Reinstalled 5.2 from SSH, rebooted, and restarted ISY and still no joy. Found an update around 11pm last night and tried that, no luck. Still couldn't access ISY. Went to bed then up today for another update and it's working great. Now on to playing with z-wave!!! Thank you @Michel Kohanim and team!

You can buy a ready made Polisy server from UDI. Its a ready made Polyglot server that will eventually replace the ISY994i. https://www.universal-devices.com/product/polisy/

You would need to use a Polyglot server and then add a node-server for the outlet brand that you have. At that point the outlet would become visible to the ISY. Caveat is that the outlet you have has to be a brand that is currently supported via a node-server.

++++++++++++++ UPDATE ++++++++++++++ As it turns out my QNAP server a 870pro circa 2015 won’t support USB pass-through. I was not able to determine if this is still the case on newer OS versions, but for QNAP OS 4.3.6 you just can’t create a HomeAssistant container via the ContainerStation app that supports USB pass-through, you have to do it via the command line. Once you have created the container it will show up in the Container Station app and you can Start/Stop it there as well as do some minor configuration changes. But you should pass all the necessary parameters via the command line. Specifically I was trying to pass-through an Insteon USB PLM attached to /dev/ttyUSB0. It’s important to know what the port is, because you will be asked to enter it when setting up the Insteon Integration in HA. You can find it by… dmesg | grep Serial The command to start the container is this… docker run -d --name="home-assistant" -v /share/CACHEDEV1_DATA/homes/kzboray/homeassistant:/config -v /etc/localtime:/etc/localtime:ro -e TZ=America/Los_Angeles --memory="4g" --device=/dev/ttyUSB0:/dev/ttyUSB0 --net=host homeassistant/home-assistant Location of the HA config files. Change it to where ever you want them to be. -v /share/CACHEDEV1_DATA/homes/kzboray/homeassistant:/config Time Zone setting. If this isn’t set you will have problems with HA -e TZ=America/Los_Angeles The max amount of memory for the container. A Single digit number followed by M, G, or T --memory="4g" This is where the USB device is passed-through to HA. You can have multiple entires, so if I add a z-wave dongle I would add another --device. --device=/dev/ttyUSB0:/dev/ttyUSB0 Finally the network port must be set to Host. --net=host A caveat is that by creating a container this way you really need to setup the proper configuration in the command line or you will be stuck with the container you create. The only way to change the container setup is to first remove it and then create a new one. Also removing the container in Container Station or via the command line will not remove the configuration.yaml file. This means when you create another container via the command line it will see the old configuration.yaml. This might be fine, or you may want to delete the /config directory after removing the container. I am new to Docker and a newb at Linux so I am sure there will be new problems with this as time goes on, but this should help to get you started.

@dinostop You might want to double check that you have checked the Insteon Support on your Polisy.

First time HA user trying to get HA working in a container running on a QNAP server. I’ve successfully loaded the container and HA works great! It see all the devices on my network, but I can’t figure out how to pass through the Smarthome Insteon PLM connected via USB to the QNAP Container Station application. I can see the USB device listed in the OS... [~] # lsusb | grep Serial Bus 003 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC And I can see it’s on ttyUSB0... [~] # dmesg | grep Serial [ 7.223967] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 21.839210] usbserial: USB Serial support registered for pl2303 [ 350.701171] usbserial: USB Serial support registered for FTDI USB Serial Device [ 350.708525] ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected [ 350.721294] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0 [309620.927037] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [309621.060767] usbserial: USB Serial deregistering driver FTDI USB Serial Device [309664.804139] usbserial: USB Serial support registered for FTDI USB Serial Device [309664.811582] ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected [309664.824747] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0 But when I go to setup the container in Container Station on the QNAP device ttyUSB0 isn’t listed. Any suggestions?

@DennisC Ah I understand. To access Polisy (ISY) you use the ISY Launcher application (Java based) Your existing ISY as well as the new Polisy ISY will both be listed. If you don't see the Polisy ISY listed. Clear the java cache and see if that helps.

@DennisC I think if you try https://ip_addr of your Polisy it will work. There shouldn't be any thing else you need to do. You may get a warning about the site not being safe. Continue past the warning. You'll be fine.

@larryllix Version 5.0.16 has been depreciated and version 5.3.4 is the most current and can be found here. Read the instructions carefully. There are things you will most likely need to update manually. https://forum.universal-devices.com/topic/33287-release-534-test-build-is-now-available/

Admittedly I didn't read the whole thread @larryllix, but you might double check that Insteon Support is enabled, it might be that simple.