gviliunas

Be sure to verify the voltage of the lighting. Some commercial lighting runs at 277V.

I tried configuring my ISY on Polisy with the same settings that are currently working on my ISY. I am using smtpout.secureserver.net (godaddy server) on port 80 and see the same problem as @whyworkwhen I try to send a test e-mail.

@mbkingThanks for your help! It worked and the finder now finds ISY on Polisy.

I had previously upgraded to version 5.04 and was able to connect to ISY on http://<ip address>:8080/desc via the finder. I have not used ISY on Polisy for a few days and several update packages were installed via the Polisy web page. Now the finder cannot find ISY on Polisy. - The Polisy service is running on Polisy. Tried rebooting Polisy. - If I try to update via ssh session, I get: [admin@polisy ~]$ sudo pkg update Updating FreeBSD-base repository catalogue... pkg: https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/packagesite.pkg: Not Found FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. - If I check https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/ There is no file "packagesite.pkg" only packagesite.txz

I was able to upgrade my polisy isy with problem but after this could not communicate with the PLM or any connected Insteon devices. Restarting ISY or disconnecting / reconnecting the PLM did not help. Rebooting Polisy solved the issue. Confirmed that LAN access to ISY now works properly.

PLMs shipped with DB9 to RJ45 cables. I was expecting to use this to connect the PLM to Polisy when the time came.

FWIW, I pair my multisensor 6s in non-secure mode. They seem to respond a little quicker this way.

Since the Z-Wave module is not fully reset in an ISY reboot, be sure to power-cycle ISY rather than just using the button in the ISY configuration tab to reboot.

Upgraded my mixed Insteon / Z-Wave system from ver. 5.3.2 without any issues.

I don't have this issue either with either version BUT, I have seen some strange presentations when opening the Admin Console. Sometimes, a program with a "Devicexyz Switched On" condition shows instead an "undefined ruleset" instead instead of the control construct. Even with this, the program was working so I knew ISY was interpreting the condition properly. I have also seen limited device features, as in your example, and Z-Wave devices on the Main page not showing the proper node features. In the past, I would re-define the condition, save, and move on to fix the Program issues. More recently, I discovered that I only needed to close and re-open the AC and the program had magically fixed itself and Z-Wave nodes on the Main page would be shown correctly. Not sure if anybody else is seeing this but this is an easy fix to try first.

@JTsao, This has been an issue mentioned for many years. Usually this is related to the battery failing on the old version 1 Insteon motion sensor or caused by programming issues with the keypadlinks. Here is some information: https://wiki.universal-devices.com/index.php?title=INSTEON_Random_All_On_Events There is also a very long thread on this Forum but I can't locate it. You should search... Since getting rid of all my MS1s and following the KPL best programming practice, I haven't had any all-ON events (for years now). Good Luck

Updated from 5.3.1 without any issues. Everything is working properly. Thank you Chris and the UDI team!

@tom.karez@gmail.comI looked up the Linear WD500Z-1 and these appear to be based on the older 300-series Z-Wave chip. These don't support Network Wide Inclusion so yes, ISY is probably going to need to be within a few feet of each switch to be able to include into your system. The operating distance with these devices should be greater once included. In these situations, I know that some have temporarily used an extension cord to move ISY near these devices for inclusion. After inclusion, some have found it good to position ISY horizontally and use a Z-Wave repeater nearby. https://products.z-wavealliance.org/products/1032/embedpics

It seems that I read that the 994 supports up to a 32Gb card now but can't find the reference. You may want to open the ticket with UDI support to confirm this. Good Luck EDIT: I found the reference from UDI: "Max SD is 32GB SDHC. With kind regards, Michel"

The first think that I would check is the power supply. If you have another "wall wort" with center-positive 2.5mm X 5.5mm connector, 12-30VDC, I would try this first. If the ISY is older, strange problems could be caused by a failing SD card. There are WIKI articles describing how to change and re-initialize the SD card. Save the old card if these don't work and submit a support ticket to UDI. They provide excellent support.

@LarryCRetired Is the MS seeing an uncovered window? I have a MS in my kitchen. If I don't close the blinds covering the window at night, the air currents across the cold window, at night, trigger the Motion Sensor.

@Michel Kohanim done! Thanks

******** My experience detailed below has been fixed with version 0.32 of UD Mobile. After installing and entering ISY Portal credentials, the sync operation now completes successfully without needing to configure the Local Connection ********* ************************ Got an invitation to install and give UD Mobile a try. (I thought that this was an updated geofencing client but was in for a good surprise) I'm using a Google Pixel 3a phone with Android 11 1. Downloaded UD Mobile from the Google store. 2. Entered ISY Portal credentials - Save 3. See Remote Connection Settings - Save 4. Sync ISY with UD Mobile - Yes Observe lots of transfer activity 1st try, the sync stalls with java.net.SocketTimeoutException: timeout (no Screenshot) 2nd try, try again. This time stalls at Inserting: Network Resources (See Screenshot attached) 5. 3rd try: Notice that on the Remote Connection Settings page there is an "Advanced Settings" area. 6. In Advanced Settings, entered IP and credentials for Local Port Settings 7. Clicked to Add New Local Network - Populated with current WIFI info (Thanks for that button!) - Save 8. Select to Add New Local Network and click on the WIFI SSID previously added - Save 9. Sync - Notice this is much faster than the previous sync via the ISY Portal. 10. Received "Finished with Error" message (See Screenshot attached) 11. 4th try: Back into Settings, try sync again. This time the sync finished with no errors. Although I had not had a need for mobile ISY access, I like the look and feel of this app. I can see myself making use of this to check light and thermostat status when I'm away

@WFPI believe that when you do a device replace, it is normal, at the end of the replacement, for the Admin Console to close. This isn't a "crash." I think you are warned of this in the replace dialog.

ISY 5.3.0 Most people might be aware of this problem/solution. I wasn't until last weekend so thought I'd document this in case some are still having problems with Z-Wave and Control program triggers. I'm using a Homeseer WD200+ switch (v5.14 firmware) in an entry hallway. I rely on being able to detect "Control" conditions in order to properly trigger entry and exit programs. Sometime in the recent ISY update past, "Control" stopped triggering my programs. While looking through this, I discovered a new feature UDI added to the device Z-Wave menu: "Add/Refresh Button Press Node." I clicked to add this new "Detect Button Press" node to my WD200+ Hallways switch and then used this new node as the Control test condition in my programs. WORKS PERFECTLY. Just to be clear, my issue is with triggering udi programs. I have not tried using a button press node to trigger scenes and am not sure this will work for those needing a z-wave scene controller.

@TomL With Z-Wave, there is still a bit of "wild west." Not so much plug-and-play but more of plug-and-play-with-it.... I don't have these anymore but was able to get my hinge pin sensors to work by changing the notification mode of the sensor. I remember that the default setting did not work. The GE instructions have you press the button. There is an entry on the Z-wave Alliance showing this being controlled by Parameter 20. Try the button method or setting parameter 20 to 2 or 3 after waking-up the sensor. One of these should work. The node I used once connected to ISY is the "Barrier Sensor"

@ExDvtchWhat version of firmware did you upgrade from? Are you using the 500-series Z-Wave dongle (No blue LED in the rear of ISY)? Ver. 5.3 does not support the older 300-series dongle.

@Mecheng70, I tested this code and it seems to work properly but there are two caveats and one question: 1. The variable s.casita_guest_code must be a State variable. If not, the program will never be triggered. Programs cannot be triggered by changes in Integer variables. Because you are setting s.previous_guest_code = s.casita_guest_code in your program, it seems that something changing s.casita_guest_code will cause the program to do what you want. 2. The variable s.previous_guest_code may be a State or Integer variable. In your program, changing this variable will not change s.casita_guest_code so you probably don't want the program to run if s.previous_guest_code changes so this can be (and you probably want this to be) an Integer. Question: Why do you have this line: "Stop program 'Door - Casita Code?" Once triggered, all of the "Then" lines are atomic and the program will stop anyway.

@esloyerIt is usually better to use your own ISP's email server or gmail rather than UDI's default server.

Yes, it looks like UDI took the Boot Loader line out with v5.2.0 RC3. That is okay. 6.81.00 is the latest version so you have no problem here. The 500 series doesn't need a Boot Loader