DennisC

Try showing your message on two lines in the body of your custom notification like this: The From and Subject should be empty.

That is exactly what the cable set was designed to do. Look at the photo again. You have to use all the cables and connector included in the kit. The RJ45 cable plugs into the PLM, the other end goes into the serial converter, and the remaining cable goes from converter to USB and plugs into eisy.

You can still either chirp the siren alarm x times or have the keypad beep. All you need to do is go to ElkRP2 and enable an output, you can call it Siren or whatever you want. Next, create a rule that when the named output (ex: Siren) turns on, then either chirp the siren x times, or beep keypad, or both. Back in ISY - Polisy - eisy, add to the Then portion of your program to turn the output you just created (ex: Siren) on for x time, or even cycle it on/off several times to get the desired effect.

There is an open issue regarding this. Currently, you can only trigger a program via function keys based on Status of Last Key. You can read more about it here: For now, a work around is to set an Elk output when a F key is pressed and then run the program when the output turns on/off. As described here: However, in your case, you are looking to press a F key to have Elk speak, but I would ask why do it that way? Why not just have the Elk node server tell Elk to speak the words?

Right here: Available here: https://www.universal-devices.com/product/serial-plm-kit/

Yes, I send temperature and humidity from my Weatherflow node server, which obtains weather data from my Tempest, to my Elk keypads. The instructions are here:

In addition, if you have installed a ZMatter board in to Polisy, you would have connected the Zigbee antenna to the board. So, yes, the ZMatter dongle can support Zigbee. Previously, UD has indicated we are waiting on firmware support.

You need to use a Cat5 cable from the PLM to Port A. I bolded the instructions in my post above.

No, you have an old ISY994. I posted instructions above, try another Cat5 cable. Let;s see if we can get you up and afterwards you should seriously think about upgrading to a new eisy.

Here are instructions from the WIKI Installation The serial connection is required to configure ISY's network parameters if using a non-DHCP-enabled router, or a direct connection to a non-DHCP-server computer; otherwise it is optional: Serial Connection Connect the DB9M end of the null-modem serial cable (included with PRO version) to ISY's Port B, and connect the DB9F end of the cable to the serial connector (or USB-to-serial adapter) on the computer. Network Connection If using a router, connect one end of an included Ethernet cable to ISY's Network jack, and connect the other end to an available port on the router. Alternately, ISY may be connected to a network switch or hub which is connected to the router. If using a direct connection to computer, connect one end of an Ethernet cross-over cable (not included) to ISY's Network jack, and connect the other end to the RJ-45 network connector on the computer. PLM Connection Connect one end of an included Ethernet cable to ISY's Port A, and connect the other end to the PLM. Note: If longer cables are required in order to reach the router or the PLM, any standard cat5/cat5e/cat6 Ethernet cable may be substituted. Do not use the cable that is included with the PLM. Apply Power Plug the PLM into a regular power outlet. Do not plug it into a UPS or into a protected power bar (a non-protected power bar is fine). An external power supply may be used with a 2412S PLM. An external power supply must be used with a 2413S PLM. 5-30 VDC 300 mA minimum Center positive 2mm male barrel jack A Radio Shack 273-028 set to 6V will work. ISY boots. The Rx, Tx, and Mem LEDs may flash briefly, and the PWR LED should be on steady. The two small green LEDs on the RJ-45 Network connector should be on, and may flash.

If you have labels that indicate Port A, then you do have an ISY994, which is at end of life and support is slated to end around the end of the year. You need to use a Cat5 cable to connect the PLM to your ISY994.

How about posting a photo of what you have. It doesn't sound like you have a Polisy.

A steady blue light? Are you sure? Polisy should have a steady green light. What color is the case of your unit that you have indicated is a Polisy? This is a picture of Polisy, does it match what you have?

If you just received a new PLM, you should have the correct cable in the PLM box. What firmware and UI are you running? Go to admin console and click on Help - About, to supply the information. If you have greater than 5.3.4, then go to Configuration tab and make sure Insteon Support is checked.

Ok, are you using the correct port on the back of Polisy: Connect one end of the included Cat5e cable to Polisy’s Network Port and the other to your network. You must use the port that’s closest to the right most edge of Polisy when the front of Polisy is facing you (closest to the db-9 serial port). Note: the network must initially be DHCP auto enabled If so, what are the lights on Polisy and is the green light on on the PLM?

The current version of firmware is 5.6.0, so you are on the most current version. There is no speaker on eisy, so yes, if you want to no what is going on, you need to open a ssh session and observe the log. I also want to commend you, you were able to follow the instructions and troubleshooting path by reading the forum post, well done.

I still think there might be some confusion over exactly which UD product you are using. You indicated above that: "The product of 994 I have is eisy" ISY994 is just that, ISY994. This was replaced by Polisy, which was replaced by eisy. There is no ISY994 eisy. The reason I am asking for clarification is because ISY994 used a serial PLM and eisy uses a USB PLM. To use the serial PLM with eisy, you need the converter cabling kit UD offers, or you need to make a cable along with some 3rd party equipment. To activate Insteon on eisy, there is a check box on the Configuration tab that needs to be enabled. To help us, help you, please clarify what you have, exactly what you have done and what is happening.

I'm not positive, but I am not sure that the "ISY Portal Node Server" is still available? I "think" Geofencing is now done via UD Mobile.

Just wondering if you did this step originated, "To use your spokens on the new ISY, your preferred ISY may need to be updated with the new ISY uuid. If you selected "Updated preferred ISY" during the migration, it will be updated for you." If not, you might have to do that manually. Since the instructions indicate you can reverse the migration of the spokens, you should be able to migrate them if it wasn't completed. To me, it appears only migration of the license for the portal can't be undone. Also, make sure you have approved your new unit in the admin console: Configuration | Portals | +Approve

I'm also running a Polisy and eisy at the same location without issues.

https://192.168.0.120 or https://192.168.0.120:3000? To access PG3x, you must specify the port of :3000.

What exactly is the message in Chrome? Does it say there is no such site, it is unsafe, or? Do you mean a DHCP IP reservation? That is what you should have. That doesn't do anything regarding firewall settings. You need to make sure firewall settings are not blocking connection. Also check your routers log file for errors or blocks from to that IP address.

I reread your posts but couldn't tell, exactly what is the result when you type in the IP address? Have you checked firewalls and antivirus programs?

How are you trying g to get into PG3x? In your browser you need to enter https://xxx.xxx.x.xxx:3000. Is that what you are doing?

If you are up for it, try shutting down Polisy, remove power from Polisy for a bit and then start up. See if you can get in to PG3x again. If you can and the node servers are not running, try and start them. If they won't start, try reinstalling one in the same slot. There is an option after clicking on install to reinstall in the same slot. Do not uninstall the existing node server, just try to reinstall and start.