kzboray

Here's an ASCII table with CR/LF and Null. I'm not sure how to help with the issues your having. But I thought you might give ASCII a go and see if that works any better.

@xKing I'm trying to set HSBKD without having the light power on. Will "change_no_pon" do that? I have added a custom parameter, but I'm not sure if I need to add a value, something like "true" or "1". As it is setting HSBKD in a program powers on the bulb. I'm trying to set color and brightness changes over time for circadian lighting and I don't want the light to actually come on as I make the changes, only when a switch turns it on or when a voice command is issued. But when that happens I want the bulb at the right color / brightness value. Is this possible?

I actually opened a ticket with UDI, just to verify I was doing things correctly. Michel pointed me to the wiki, which I should have read more carefully. Here it is. "NOTE: If using portal connections (i.e. Alexa or Google Home) the user may wish to choose the 4 Scene method (indicated below) for version 4.x. The multi-controller, single scene scheme used in the version 5.x examples, do not allow for speed control and keypad button to match when the speed is adjusted via the portal. In short, You need 4 different scenes one for each speed and backlight combination. Each scene is in charge of ensuring that the fan speed follows the button. And, the scene itself (the circular multi color icon) is what you should use for Alexa. Not the device. The reason this is the case is because, although you can control the backlight for KPLs, but you cannot make them send a command as if you were clicking on them (no command by proxy). So, you will need to send the command to the parent scene. And, thus, you will need 4 scenes if you want to use Alexa."

@jkraus Since you're not familiar with SSH, I'd open a ticket and let UDI handle that one. There are to many ways things can go wrong once you start making changes via the command line.

That looks like PG2. The portal account is unmanageable, that is normal. If you fire up PG3 IP_Addr_Polisy:3000 admin / admin You will see that Portal isn't listed. As far as that errent entry 2/2. I would just ssh into the Polisy and... WinSCP works too! cd /var/polyglot/node servers ls (lower case Ls, You should see something related to the 2/2 NS or possibly an empty directory. That's the one you want to delete.) rm -R directory_name (what ever the name is that you find.) Be very careful not to delete the wrong directory. It will remove the Node server in PG2

Open PG3 in a web browser and then click the delete button for the Node Server you want to delete.

Alternatively you should be able to just power cycle the Polisy.

It's referring to the PG3 server. Open a connection to the Polisy using SSH. SSH your_polisy_ip Login is admin Password is admin type the following command sudo service pg3 restart That should get PG3 up and running.

I Think @MrBill and yourself have the right idea. Your Polisy isn't setup for the right ISY. Open your PG3 web page and click on <ISY>. Check that you have the correct UUID listed. For example I have two ISY's One is my original ISY994, the other is the newer IoP. You can add your IoP, by clicking on the <Add New ISY> Name is what ever you want to call your IoP IP is the IP addr of your IoP Port should be either 8080 or 8433 User Name by default is admin Password by default is admin Once you get Admin Console running make sure you have the ISY check box checked.

I'd suggest clearing you Java cache, reinstalling ISY finder from here, and restarting AC. https://isy.universal-devices.com/start.jnlp

@larryllix & @MrBill Yes that is how I have always done it. Four programs and variables, but I wanted to try the single scene method described in the wiki for 5.x as recommended by @Javi. Unfortunately it seems the single scene method while it works for setting fan speeds, does not fully work with Alexa integration. ? It controls the fan speed, but not the local buttons to show the selected fan speed based upon voice control. Manual control works perfectly. But then I've never had an issue with a bigger hammer working every time. ? Thank you all for your comments and suggestions!

@RPerrault & @MrBill First let me thank both of you for your input. RPerrault, your described method is very similar to what I've done in the past. I was really hoping there is some kind of trick I don't know to allow the scene to work with all attributes between Alexa and the IoP. Half the job is getting done; the fan works, but the buttons not being set bugs me.

@MrBill That is exactly how I have the FanLinc configured; 5x configuration. The problem is that when I tell "Alexa" to set the fan speed to say high, the fan indeed goes to speed setting high, but the 6-Button keypad status does not change to mirror the current fan speed. Using an IoP 5.4.3.

So in the past I've created programs for each fan speed to set the proper status on the 6-Button keypad, but I'm wondering if there is a better way? The downside to doing it this way is that if someone uses the keypad to quickly change fan speeds it can get itself into a loop where the cloud speed and the local button speed selection are different, so it starts bouncing from one to the other. The only way to stop this is to log into the AC and disable the program momentarily. How do all you experts accomplish making the Alexa set fan speed correctly and update the local 6-button status as well?

Have you tried the basic, single button push on the front panel of the Polisy? If not I would give that a go, and if that fails open a support ticket with UDI. https://www.universal-devices.com/my-tickets/

@Gary Funk Give this a go. I think it will get you up and running. Upgrade Original PoliSy (without the packaged kernel) curl -s https://pkg.isy.io/script/update121.sh | sudo bash sudo shutdown -r now Wait for the unit to reboot, up to twenty minutes, then: cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now

Since PG3 supports multiple Polyglot's I was trying to use the Portal URL to add a remote Polisy to PG3 without any success. Just trying to see if there might be a way to accomplish this without using a VPN or port forwarding in the router.

Is it possible to use the portal address to access a remote Polisy? I don't want to have to poke a hole in the firewall to allow remote management of the Polisy. When I use the portal URL in place of the IP address it fails to add the Polisy. Example only: Admin Console URL: https://my.isy.io/isy/2389687e62f28763e207962a298746b/desc

@dbuss Please read this thread.

@bigdog 1) I have seen references to a Z-Wave 500 "dongle". Do I need an additional dongle of some kind or is the module all I need? The ISY994i-zw originally came with a Z-wave 300 series receiver / transmitter installed. As best I can recall near the end of 2019 UDI released a new firmware for the ISY that supported the newer z-wave 500 series of transmitters / receivers. Z-wave is backwards compatible, so if you have series 300 light switches, they will work with the newer 500 series transmitter / receiver in the ISY994i. If you have an older ISY with the original 300 series z-wave card, you can order from UDI a newer 500 series card to replace it. You can do the upgrade yourself. It's only 4 screws and a simple swap. Series 500 offers enhanced distance, and several other improvements over the 300 series specification. Like all technology, the z-wave specification is constantly evolving. You can purchase series 300, 500, and 700 products. Since they are all backwards compatible, they will work, but to benefit from the newer features of the 700 series you would have to have a network of all 700 products. Just as an FYI the series 800 specification is now being discussed and will soon be completed. But since the series 700 products just became readily available in the last two years, I don't expect to see series 800 products anytime soon. 2) It seems like the module will support 300 and 500 series. Is the what "Plus" means? Z-wave plus is an update to the z-wave 300 specification. It has a lot of the features added in the z-wave 500 specification. Again all products on the z-wave network must support z-wave plus to offer the best advantage. 3) I have also seen references to S2 security. There are two levels of security with all z-wave devices. S0 and S2. S2 is new and offers much better encryption during the initial handshake that occurs when you pair z-wave devices. This is to prevent someone from snooping your network and being able to hi-jack your z-wave devices. While with most devices this is probably not necessary, if I had a z-wave door lock or heavens forbid a security sensor, I would defiantly want to use only devices that supported S2 security. Since S2 is new, it hasn't been adopted by every manufacturer out there yet. Only products labeled S2 have support for S2 security. 4) Do I have this with the module or does this require a Polisy and a Z-Wave 700 dongle? The Polisy doesn't come with a per-installed z-wave adapter (transmitter / receiver) instead you simply purchase the dongle you want and plug it in via a USB port. The current list of supported z-wave dongles is only the 700 S2 stick from Zooz, but with time I imagine this list will grow.

If you click on the Purchases tab, it will take you to the purchased NS's page, but it doesn't list any actually purchased NS's. However if you click the Refresh button it will properly display purchased NS's.

@Westlake Ventures It will be ID'ed as an ISY. It sounds like your ISY isn't on the network. Do you see the error light and memory light on the front of the ISY blinking? This would indicate the ISY isn't connected to a network. If they are not blinking then, do you have multiple networks? Wifi 2.4MHz and 5MHz. You need your phone to be on the same network to use Fing. Error light and Memory light blinking simultaneously: ISY is not able to get on the network.Please ensure: The Network jack on the back of ISY is connected to your router The lights on the Network jack have one steady on and the other one blinking. If not, check cable and connectivity to the router Your router provides DHCP There are no other devices on the network with the same IP address (IP Conflict) If you have configured your ISY to use DHCP, then you will have to search your network for devices that might be in the same DHCP range as your router is providing If you have configured your ISY with a static IP address, and as long as you have a good backup, you can Factory Reset your ISY and then restore a good backup (File | Restore ISY). Once prompted to change the network settings, choose No

@Westlake Ventures There is a free, ad driven application called "Fing - Network Tools" available for Android phones. Install it then scan your network. It will list the ISY and it's IP.

@DClausen When you start ISY Launcher the UUID will be listed for all located ISY's including IoP's.

I have installed over a thousand Insteon products including switches, dimmers, door sensors, on / off modules, etc in homes all over the bay area since 2005. In that time I've had one switch fail which was my fault (I wired it incorrectly and blew it up). That includes 20 something PLM's without a single failure. The one exception to this is the FanLinc, what a POS. I've had so many fail I've lost count. In the past I simply had Smarthome replace them since they often failed within a year or two. Now I suppose I'll have to figure out how to repair them. Fingers crossed I haven't had one fail in almost two years, but I do have spares on hand for when one does. I'm not sure what I'm doing differently than others who have high failure rates, but I've found the Insteon product line to be very reliable. I do make sure the the ISY / Polisy / PLM's I install are in climate controlled conditions. In closed spaces I install active cooling, but otherwise I'm really not sure why people have such high failure rates.