Irakandjii

My thanks to UD. The system is back up and running! It was not something I could have done, so no point in elaborating other that it is fixed in an exceptionally professional manner

Hi I show [Ticket #22965] Poloy dropped off line Oct 20, cannot get reconnected The original ticket and 2 additional informations of my progress

I also have the IP address showing up as 0.0.0.0 and my router does not recognize the MAC address. So the DHCP registry for the MAC shows diconnected. The "cloud console" works to reboot etc. but no changes seem to be saved. For example my location is not saved between sessions

This does not complete for me, I just get a "polisy.local’s server IP address" could not be found. message I cannot connect to Polygot on the Polisy Looks like I am out of the running until my ticket comes up.

Doh, I saw this too late. My Polisy Pro is as old as they come. Pre-Order version. It upgraded to 13.2 but says niether the Insteon PLM nor the z-wave controllers are connected so nothing works. I have tried all the steps on this forum to no avail. I submitted a ticket. Hopefully I can bring it back to life. I am in Canada and Aartech can't sell me the USB to Serial cable for the PLM or the Case for my existing z-wave board. Hence, I can't even upgrade to an EISY if required. This is really frustrating. Turns out I can just need to buy a new EISY, a new complete zMatter Dongle and a new USB Insteon PLM for about $1000. I really wish this darn thing had not auto upgraded me into hell.

Just found a thread that seems to speak to this issue. I will check that out. Sorry for the bother.

My Polisy programs stopped working sometime in October. Not sure of the exact date. (I was bed ridden with a severe case of covid) Yesturday I started to debug it. Oddly the IoX launcher behaved differently that the last time I used it. I did not get a direct console connection to the Polisy on a network IP. The Polisy showed up as a cloud console. I followed some instructions on this forum to update to 5.7.0_5 since this seemed to describe the problem of programs not working. The update process from the console seemed to have an effect, front lights flashed etc. but I got 5 beeps ... Programs still did not work, more importantly with the cloud console I could not test because instructions from the console to turn lights on and off (Insteon, z-Wave and hue) failed to work on all devices, door lock reported ssl security errors etc. Further investigation revealed my router will not assign an IP address to the Polisy. It is the same router I have used for the past 2 years. There is a reference in the routers DHCP table for the Polisys MAC address, but the Polisy is undetected. I moved the Polisy to direct connect to the router and eliminate possible switch problems. Still no joy. I tried network reset. pin in hole until 2 leds -> no change I ended up doing a factory reset, pin in the hole until 3 LEDS lit (again with the cloud console) it definately reset since I needed the factory credentials to log in. Still there is no IP address and NOTHING works, did a recover from backup nothing works. I cannot ssl into the polisy because there is no IP address. I should have a good electrical connection for the cat4e cable, the leds blink appropiately indicatin speed and physical connection. I suspect a fault in the network subsytem of the Polisy I have no idea what else to do

I have this error too in the Mobile app. Yet, I am on a Polisy and just updated from an i994. It is the old reverence to the i994 that is showing the message. I cannot find a way in the App to remove the now defunct system. Seems it may be an issue with the App. Update: I logged out of everything and restarted --> The error cleared

Hi folks I am in the process of upgrading my i994 to policy with the matter board. I am very happy that S2 security protocols are now in place for z-wave since I am using S2 enabled devices. I am using Aeotec z-wave extender 7's that support z-wave S2 and the devices are now recognized by Polisy appropriately requiring a PIN to authorize. So the network now supports it. I have some preexisting extenders that were installed before S2 support and they were migrated to Polisy, it appears they are not supporting S2 yet. Looks like I must forget / reinstall them. Has anyone compiled a best practices for migrating / install z-wave S2 enabled networks? If not, I would be willing to assist in its development. We could begin by posting to this thread.

I used the instructions as written. I have a single z-wave device left in placeholder mode. I have had problems with it before so it may just be a fault in the switch. My Door locks were detected and function properly using the old ISY-944 program. 8 z-wave devices 23 Insteon devices 6 programs I am pleased with the outcome. Thank you.

Yes you are correct, I had forgotten that I used a TTL to USB adapter when doing this in the past. Senior moment. I have edited the post and removed my previous speculation. I toyed with using an old TTL to USB Serial adapter and then ... thought .. but why?

I am not sure if this is helpful to folks, but I had some trouble understanding the above with picture orientations and all. I want to make my own cable to make things easier. I have an aversion to adapters. Though the one identified above would certainly be simple enough. Based on the following published documentation. PowerLinc Modem (Serial) (insteon.com) RS-232 DB9 pinout diagram @ pinoutguide.com The pin numbers used below are the standard numbering. Usually stamped into the DB9 and defined by the shape of the RJ45 jack. Pictures are provided in the links above. The RJ45 jack on the PLM uses : PIN 1 = RS232 Rx --> PIN 2 on DB9 PIN 8 = RS232 Tx --> PIN 3 on DB9 PIN 7 = Ground --> PIN 5 on DB9 RS232 potentially uses voltage levels from -12 to 12 volts, but can be as low as -3 to 3 volts. This is not compatible with USB hence the need for an adapter. Removed references to TTL , if it reappears the concept is incorrect.

FYI for locks, make sure the repeaters are paired to the mesh in secure mode. For example, the aeotec repeaters default to non-secure mode when you pair them unless specifically told to pair securely. Just one of those easy to miss things that mess up door locks.

I can assure you it works in Canada. I have a Schlage 469 installed in Ottawa. You need to be mindful when you set it up though and make sure you have the Schlage lock documentation. You need to ensure you have a robust zwave mesh In my case I use an aeotec repeater with line of site to the lock. I have verified that the repeated has an excellent connection to the ISY994 You need to link the lock If the lock has ever been used before you MUST; factory reset the lock exclude the lock using the ISY exclude function, otherwise skip step 1 above. Link the lock using the add device button in the ISY Console. You need to program the lock in the ISY Console.

The article is about setting up the Scenes and programming, NOT about legal issues which are location (Country, State, County, City) dependent. It is incumbent on the user to check these based on their local requirements. That being said, Thanks for the advice and I followed up by reading the link. The associated legal opinion clearly states the UL compliance is not a legal requirement. The article is biased towards the USA. Readers within the USA may have issues with their setup depending on their state and local laws, so this reference may be helpful to them. in Canada we are not as litigation imbalanced as in the USA and spurious lawsuits are not encouraged or tolerated. The IR system that is in place is more than adequate to prevent operation if children or objects are in the way. It has been tested as effective for this purpose. To be clear. My system meets the minimum UL requirement and is consistent with my local building codes. The Siren is a good idea, I will consider that, mainly to scare off the odd cat or racoon trespasser.