drprm1

Used SSH to update Polisy and install PG3 Added Polisy to launcher where it gives the choices AC lan, AC cloud, Polyglot V2 (deprecated), and Polyglot V3 Can go right to PG3 but can't bring up PG2.... How do I bring this up? (I'm assuming I should be able to???) Thanks

Thanks

I have no doubt this is the correct cable and will be using it when it comes time. Was just wondering why the connector specifications don’t seem to match the cable end.

I know. This is the cable I got out from behind the flap in the box.

Getting ready to make the move to Polisy. Ordered the serial to rj45 adapter but then found a new, in box, serial PLM in my closet ? I’m hardly the electronics expert but the photo of the end of the cable enclosed in the box only has 3 connections…The connector specifications show 4 connections in different spots. Can someone explain this to me or do I have the wrong cable??? Thanks

I too noticed multiple Pushover messages for one event. Placed a 5 second wait before calling the NR. Working so far…

https://polyglot.universal-devices.com/

5..3.4 Firmware=UI No joy

No, just follow the Wiki....... Just time consuming

Don’t remember if I tried that long of a time out. My credentials didn’t change. Checked with Prowl. Just finished switching all over to Pushover. Thanks

Thanks for suggestion SNI is checked AND my timeout is 2000 as per wiki. I’ve tried changing a test NR timeout sequentially higher with no luck

Thanks but it doesn’t work in my case.

Solid system 5.1.0.....Would like Prowl notifications to work again so updated to 5.3.4 and checked SNI box. I now have system with many extra nodes, many missing nodes, and programs which won't run. (Haven't checked yet for scene adjustment problems) I’ve had to redo everything and find problems before. Just rather not….. Oh and Prowl notifications still don't work....Awesome!

I normally upgrade and update whenever its available but have hesitated because my Schlage locks didn't work with the 500 board. I realized this when on 5.1.0 and downgraded back to the 300 board... I know someone will say 300 won't work with 5.1.0 but it has and has been problem free since i changed....until now with the Prowl issue. If upgrading to 5.3.4 is the only way to make it work I assume something changed on Prowls end making it incompatible with previous versions????

Just realized that all my Prowl NR aren't working either (all others are fine) Any update on getting this working? I too have used Prowl with no problems for years and it recently stopped. My UI and firmware are both 5.1.0 (Rather not upgrade to 5.3.4 or higher because I still use the 300 board which works with my Schlage locks) I have a relatively new SD card... Tried generating a new Prowl api key but the test nr still didnt work Thanks!

My 2.6 shows 9e

Had a PLM go bad (no communicaion, empty PLM link table. Replaced it yesterday with a ver2.6 I just got. No problems replacing and everything working fine so far....... Did a PLM link table count after modem restore and got a count of 343 which was about what I had before other PLM went bad.. Did another link count this morning and got 571. Did three more link counts and got 107, 142 and lastly 109. Anybody have any idea why this might be happening and should I be concerned? UI and Firmware match at 5.1.0

Just got delivery of a new PLM ver 2.6.. Hope it lasts longer than my ver 2.4 which only worked a little over a year.

Kind of thought that would be the case. Thanks

My PLM, ver 2.4, in service one year and two months started acting up in that programs weren't firing. Checked PLM links table to find it empty....Have 2 spares, ver 2.2, which I took out of service not because they were bad I just wanted to replace with newer version. Replaced the bad one with one of the older versions and everything is good for the moment. Ive ordered the caps to repair the newer PLM and my question is is there any way to tell if the repair is good other than put it in place and do a modem restore? Lets say the repair is bad can I just put the older functional modem back in place or will I need to do a restore modem on it again as well? Can't believe I only got 14 months out of it.......... Thanks

@Chris Jahn @Michel Kohanim V5.1.0 Looking for advice please... I moved back to my 300 series dongle many months ago and recently upgraded from v5.0.15 to v5.1.0. Although I have over 60 zwave devices I had minimal issues with the upgrade and now everything works great except for a persistent green update icon associated with one zwave device.(the device works fine and my OCD is about over it) Now I see "Please Note: Due to reported issues, if you are not using a 500 Series Z-Wave board in your ISY then we do not recommend you upgrade to 5.1.0" Going forward was wondering if it would save me problems if I went back to v5.0.15, put my series 500 dongle in, then upgrade to 5.1.0? ( I fully intend on moving back to the 500 in the future)

Missed that

I noticed this too and finally realized that unlike before the upgrade I could simply change the temp but now I have to change the temp then hit the associated button. I may be wrong but I don't remember having to do that before the upgrade... Ex. change temp then hit "cool setpoint" Try this

Thanks!