kzboray

@cksedg Here's a link to the Manual. It's not very forthcoming as the siren was tied directly to the Smarthome phone app. I also know that UDI had to reverse engineer all support for the 2868-222. Smarthome refused to give UDI any information on the device. As I recall the 2868-222 may have been the straw that broke the camels back with UDI supporting future Smarthome products and a shift towards z-wave. 2868-222 Documentation I have also played around a bit with the 2868-222 and never had much success getting it to do the things I wanted it to. As I recall from my testing about a year ago, it is meant to be triggered by some other device; either immediately or on a delay, I never could get it to chime, only the siren would activate. As far as the all the other functions go I'd play with them and see if you can figure out how best to utilize them.

@oneklakes It's not difficult, but you do need to know how to SSH to your Polisy. You can use the ssh command built into windows or use a utility like Putty. once you've logged onto your Polisy do the following. 1. Make sure your Polisy is up-to-date sudo pkg update && sudo pkg upgrade 2. Install PG3 sudo pkg install pg3 sudo service pg3 enable sudo service pg3 start

@gregkinney I have little experience with z-wave, but have played with the Zooz zen32 and the Aeotec smart switch7 quite a bit. I was mainly focused on interoperability between z-wave brands as it relates to scene control for lighting. I was also looking for replacements for existing multi-switch devices from Insteon. Both of the devices I played with are 700 series and performed quite well even in my test environment with only two devices. Performance was much better than the older 300 or 500 series as measured by distance, speed of response to commands, and consistency. I have no experience with Yale products, but I can say form the description the AYR-MOD-ZW3 seems to be a z-wave plus device which is a 500 series and not a 700 series. There are others on the forums here with a lot more z-wave experience than me and I would encourage you to post on things that interest you. The amount of experience available on this forum is truly amazing at times.

Sorry @CopyRon Unfortunately all that looks good. It's time to open a ticket with support. https://www.universal-devices.com/contact-us/

This one is available https://smartenit.com/shop/plm-serial-cable/ Or build it yourself. RJ45 PIN1 --> RS232 TX RJ45 PIN8 --> RS232 RX RJ45 PIN7 --> GND

@CopyRon It seems like your Polisy can't find it's way off your local net. I am assuming (yikes) you can still use the Polisy's web interface for PG2 and PG3. SSH to your Polisy and use this command. And let us know what the output is. $ grep "nameserver" /etc/resolv.conf Then use this command as well. $ ping google.com You should see the following output. Use CTRL-C to stop it. PING google.com (142.250.189.174): 56 data bytes 64 bytes from 142.250.189.174: icmp_seq=0 ttl=116 time=12.923 ms 64 bytes from 142.250.189.174: icmp_seq=1 ttl=116 time=11.761 ms 64 bytes from 142.250.189.174: icmp_seq=2 ttl=116 time=11.700 ms ^c Again let us know what your results are.

@Geddy Ya I was hoping that along with re-doing the original bash command would jump start a failed update. Kinda grasping at straws and hoping to get @CopyRon going. Otherwise Michel is going to have to work his magic.

There is one simple thing you can try. On the front of the Polisy there is a very small pin hole. There is a hidden switch that you can depress using a paper clip or something similar. Press it once and then wait until your Polisy beeps. Then wait another minute to make sure it hasn't rebooted which would cause it to beep again. If it beeps then a minute later beeps again. walk away for a bit, it's running an update and it can take awhile ~20min. If it beeps once and then nothing, yoru ready to begin trying to update again. SSH into your Polisy and try executing the command below one more time. I'm thinking you rebooted the Polisy in the middle of the original update. Pressing the front panel button one time will force an update and may allow yours to complete the original update process. Then I would try running the full update from the beginning. So first... Enter each line one at a time. The first line can take forever to finish running. curl -s https://pkg.isy.io/script/update121.sh | sudo bash sudo shutdown -r now After this process completes, which can take up to 20 minutes, hopefully you will be able to runt he second command sequence listed below. No! Really this can take a lot of time Be patient. Now you are ready to try this again. cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now If this doesn't work then it's time to call in the big guns. Open a ticket with support.

I suspect your Polisy is running 12.x. You can try these instructions to upgrade your older Polisy, but you might be better off just opening a ticket with support at Universal Devices Support 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 20 minutes 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; it can take up to 20 minutes. 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://IP_Addr (PG2) https://IP_Addr:3000 (PG3) For PG2 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.

@larryllix I started to try something like that and got side tracked. I wanted to run it by you guys before I started up on it again and make sure I was on the right track. Between you and @Bumbershoot I've got some good thoughts on what to do. Thank you!

I have several programs that change the lighting throughout the day. Here's an example. It sets the color, brightness, and a 9 min fade from the last setting. That way if the light is already on, there is a gradual transition to the new settings. Kaz's Ceiling Light HSBKD Day - [ID 000F][Parent 000C] If From Sunrise + 1 second To Sunset + 30 minutes (same day) Then Set 'Kaz's Bedroom / Kaz's Ceiling Lights / LIFX Group Bedroom' Hue 58000 Saturation 0 Brightness 65535 Color Temp 6000° K in 540000 ms $s.Kaz.Light.Last.Setting = 1 Else - No Actions - (To add one, press 'Action') As nap time approaches and bluer light can help avoid that dragging feeling starting around 2pm till about 5pm I again change the color and brightness; this time towards blue and about 75% full brightness. Then again around sunset it changes into a more orangeish dimmer value for evening and finally into a dim red (submariner lighting)as a night light after everyone is in bed. You know, just in case I need to use the bathroom 6 times before sunrise. ?‍♂️ The last program I have involved in all this is an override that turns the lights on full brightness for things like the fire alarm going off, or if I just need really really bright light in the room for something I'm doing. I do this via a fast on / fast off (double tap, yes that's rule #2) The problem is after a fast on I have no way of returning the light back to it's previous setting based upon time of day. Here's the override program. Kaz's Ceiling Light HSBKD Full Brightness - [ID 003C][Parent 000C] If 'Kaz's Bedroom / Kaz's 6-Button KeyPad / Kaz's Fan KeyPad LIGHT(1)' is switched Fast On And 'Guest Room / Guest 6-Button KeyPad / Guest Fan KeyPad Light(1)' Status is 100% Then Set 'Kaz's Bedroom / Kaz's Ceiling Lights / LIFX Group Bedroom' Hue 58000 Saturation 0 Brightness 65535 Color Temp 9000° K in 1000 ms Set 'Kaz's Bedroom / Kaz's Ceiling Lights / LIFX Group Bedroom' On Else - No Actions - (To add one, press 'Action') So how do I recall the previous setting on the next press of the ON button?

Follow the directions in this link for either 5.x firmware or if you scroll down a bit you will find the 4.x setup. Both the 5.x and the 4.x listed will keep the lights in sync, and support voice integration and control via Alexa etc. https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration

That sounds like a Michel question. I'd open a ticket with support.

@oskrypuch There are both a PG2 and PG3 Node server for Ecobee. I'd use the PG3 as PG2 is going away.

I should also mention that if you use the newer 5.x version of setting up a KPL and FanLinc, you will end up with an extra button. The Fan OFF isn't needed in this configuration, which by the way works with Alexa. You can of course add in an OFF button program, but I like having an extra button to play with.

With 5.x firmware things have changed a bit, but the old way of creating a scene for each button still work too. Check out this page for step by step. Be sure to use the instructions for the version of firmware you are using. i.e. 5.x or 4.x. https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration

@JimboAutomates Tagging you for the above. @Pcarp I'm unsure about a couple of things. Your listed version of Polyglot is a little high. The current beta version is 3.0.62. Are you sure about the version of Polyglot you are running. You can double check by accessing your Polisy and then checking the bottom of the Dashboard page. You should see something like this. Then can you also post a copy of the Wireless Tags NS log please. I have tagged Jimbo.Automates the developer so that he can take a look as well. To download a log file go to the Wireless Tags NS page and click on the <Log> button then add that file to this post.

@tlightne In the future it may be helpful to alert the developer. I went ahead and copied your post from April to the GitHub Issues for this node server.

@simplextech If you're feeling like migrating another NS. seems like there is a home for NodeLink Logging on PG3.

@MrBill As i understood what @hart2hart was trying to be accomplished, these would be used as triggers for something to happen. Thus the state variable.

Setup variables for each and write them at the start / end of a cycle. You probably want to use state variables. s.start.date=${sys.date} s.start.time=${sys.time} s.start.variable= etc I'm not sure what you mean about a network resource to send to a service.

@dcard I don't use the Hue NS, but here's some of your questions answered from the NS page itself. The PG2 version has been ported to PG3 so expect similar functionality. UDI Polyglot v2 Philips Hue Poly This Poly provides an interface between Hue Bridge and Polyglot v2 server. All Philips branded bulbs are supported (Dimmable, White, Color and Extended Color), bulbs could be added to the Insteon scenes as responders and should respond to all basic commands, including dimming. Configuration Once installed - push the button on the Hue Bridge and add Node server into Polyglot, that will allow it to pair with the Bridge. If you have been using v1 of the Hue Poly - you will likely have a file named bridges, copy that file into ~/.python_hue - you should be able to skip the pairing process and start this Poly out of the box. Sometimes automatic bridge IP address discovery fails, in that case - you can specify Bridge IP address in a custom parameter ip for the Node server using Polyglot's frontend interface. Additionally - if username parameter is given - Node server will use it (in case you have a username established already and don't want another one created on the Bridge). Notes Poly assumes that Bridge IP address never change, so it is recommended that you create an IP address reservation for the Hue Bridge on your router. Please report any problems on the UDI user forum. Thanks and good luck. History Phue Library with minor modifications is used as a backend. Original Implementation of the Hue Poly by UniversalDevices team was a base. LiFX Poly was used as a template in order to re-write this Poly for Polyglot v2

Just sharing my experience. sudo pkg update & sudo pkg upgrade sudo service pg3 restart Opened my web browser (FireFox) and found that PG3 was showing it needed to be restarted. putty polisy sudo service PG3 restart No change to PG3, still showing it needs to be restarted. Logged out of PG3 and restarted one more time. Logged back in and everything was fine. It seems that last step of logging out and back in fixed things. Your mileage may vary.

@cw1400 I'd open a ticket with UDI. I suspect you are up against a UDX bug. You can try the following first if you like. SSH to the Polisy then... sudo pkg update && sudo pkg upgrade sudo service udx restart sudo service isy restart If you have a backup of the configuration, you can load it now.

[admin@polisy /var/polyglot/node servers]$ sudo service polyglot stop Stopping polyglot. [admin@polisy /var/polyglot/node servers]$ My first full migration completed. PG3 and beyond.