Geddy

@fanpatsdec first - easiest/preferred way to post a program is to right click on the program and use the "Copy to clipboard" option (last menu item). Then paste it as text in the forum post. This way it helps others if they need to suggest an edit to not have to re-type the program or try to describe the change. You're the second person that's had an issue with "fast on/off" not triggering. I don't think this would be a bug, but might be a concern that should be reviewed by a support ticket with UD. https://www.universal-devices.com/my-tickets For testing try changing from "Fast off" to just "off" and see if the device triggers the program. The other user appears to be having issues with communication not even seeing the device trigger in event viewer. Open event viewer and set it to level 3. Then operate the switch for both on/off and fast on/fast off and then copy the event viewer to a text editor and see what the IoX received for events.

@andrew77 I don't see anything in the program you posted that would cause this not to run. I was going to say if you had the wait at 25 minutes maybe something was turning the fan off (or turning it on again) while the wait was in progress that cause the "IF" to re-evaluate and restart the wait or make the program "False" and not turn it off. Try watching the program tree if the status of the fan is "ON". Does the program turn solid green? This would indicate the program is running. If the status of the fan goes to off then the program icon would be partially red , indicating "FALSE" state last time it was evaluated. I just tested your program and my fan turned off as expected and the program appeared with the red icon because now the "If" is "false". Try "find/replace" (right click on any program and it's near the bottom menu option) in programs for the "Bathroom Fan" and see if you have other programs controlling it. There might be something else causing the program to turn "False" before your wait is complete. I tested while remote to the location and used UD mobile to turn the fan on and status on admin console showed "on" so program was true and turned the fan off (I lowered my "wait" to 10 seconds for quick trigger). Remember if anything causes the "IF" to re-evaluate during the wait the program essentially restarts. It's possible your 25 minutes is restarting and still going longer than you expect it to. Perhaps use "Switched" for the fan device to trigger the program. That way it's a physical process of turning the fan on that triggers the wait.

Something you should know too is that many carriers have limited email to SMS overall. So while you might think you're good with a 2 min delay it could be the carrier limiting the delivery all together. It's been an ongoing issue on the forums for the last several years and only seems to be getting worse by some posts I've seen. (just search: "at&t limiting email to sms" and see all the issues popping up) There's no "good" way around it with only an ISY994, but one suggestion has been using a dedicated email client on a mobile device (like Spark email app) and only have the ISY email account checked on there to get alerts through that app. I believe there's a way to use UD Mobile and network resources to send alerts, but I've never attempted to do that so would just refer you to the wiki to read more about UD Mobile.

@TUhl01 or perhaps try: eisy.local:8443/WEB/sysconfig.txt - kind of got off target of what @chris.com was looking for though. @chris.com if you read some of the other posts in this area you'd see what others have been doing with this plugin and perhaps the steps you were asking about for setting it up. As you mentioned though, seems like the latest version has some options that aren't (or weren't) fully available at least until the UDX system is updated.

@JMC I think you've had this issue before. Not sure what you did to get it sorted out before. I know @bpwwer was also in on a recent post about this. I don't use that OS so can't help with what you're attempting. Looks like last time you removed IceTea and reinstalled and stuff worked. Old posts you had about this (or similar):

Glad you got it sorted out. Was about to reply... This is an SMTP error specifically "SMTP_WRITE_FAILED". Are you sending a bunch of messages all at once? https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages What are you using as your SMTP server? If using the UD default option and sending a lot of email at once you might be better served with a Gmail setup. https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_gmail_Account

@JMC what computer OS are you running? have you attempted to clear Java cache? Make sure you select all three options. Typically the third box is unchecked. By checking that box it should remove the desktop icon and underlying connection with it. Allowing it to be re-added when start.jnlp is run the next time. Delete any start.jnlp or admin.jnlp files on your system. Download a fresh file from the Universal Devices website (https://www.universal-devices.com/) and click on “My ISY” on the upper right of the homepage. Most of these directions work for Windows and macOS systems. If running something else please let us know what it is and maybe others can chime in.

What kind of results do you get when controlling a device from admin console? Post the event viewer of that interaction. It will help make sure the hops and ACK is received. I ended up having a 4 outlet setup installed where my network/TV/ISY sit. Most network devices and A/V equipment are on a UPS, but the PLM is directly connected to the wall. I have whole home surge protection at the panel. Thankfully the UPS doesn't seem to impact communication for my setup. Some have suggested putting noise filters in and plugging the UPS into those. If I have an issue in the future that would be my step to reduce signal issues. When you moved the PLM did you power cycle the ISY994? If not, please reboot the ISY994. Make sure all your connections to the ISY994 and PLM are secure. What computer system are you using to access admin console? Are you on macOS? Would you make sure you verify the UI and Firmware match (Admin Console -> Help -> About)? Just wanted to be sure before getting too far along. Event viewer is normally not "empty" unless you just pressed clear and posted that screen shot.

Because your program is “switched” so that’s only when physically operated. Otherwise you need to use “status”, and it would trigger from admin console. If the event viewer doesn’t see a physical switch event (on/off to fast on/fast off) then it’s not sending a signal to the ISY994. The switch could have gone bad, but if able to control from admin console does seem to be a noise issue or failing switch. If you operate any other devices in the program (or in the same area) do you see the changes in event viewer?

In admin console right click the program and select "run then". Do you get the results expected from the "THEN" portion of the program? If so, as @Techman suggested post the program. (Right click on the program and "copy to clipboard" then paste as text in the post. That's better than a screenshot or photo of the screen. It helps those trying to help you by not having to re-type edits in a reply and also makes it searchable should you ever want to find it again in the future.) Just by chance...have you rebooted the device since the time change?

In Admin Console open Event Viewer (Tools -> Diagnostics -> Event Viewer). Set it to Level 3 "Device Communication Events". Then go operate the device for fast off. Depending on how much other activity you have going on it might scroll quickly. Can click the "Copy to Clipboard" icon and then paste the log into Notepad. I'm not 100% sure, but you might be looking for something like "LTOFFRR".

Yeah, as @Techman suggested...open a support ticket with UD to get the Polisy updated to current IoX and PG3x then you could try the migration process. The underlying issue is not being able to get things running again with the new PLM and the ISY994. If you don't have a good/current backup you could be migrating to the Polisy with similar issues. I know there was a few IoX versions that would get frozen trying to update on the Polisy, but it's been so long I don't remember the exact versions.

Correct. Sorry. On the folder copy it adds that. Otherwise, for individual programs it's just copy to clipboard. It is still the "last" menu option. Not really. There's no verification process (at least that appears to a user). Typically a bad backup will stop and give errors. Another user recently had issues and was having problems with the backup process completing. Do you run any Z-Wave devices? Make sure you make a z-wave backup then the ISY backup so it's all inclusive. When the ISY is in "safe mode" that means it does not recognize/see the PLM. Make sure the PLM is plugged in 30-60 seconds before starting up the ISY994. Also, there should be a solid green light on the PLM. I'm not sure what you mean. You mentioned that PLM is working. If things are working as expected then make a backup now and use that backup to migrate to eisy. Shouldn't need to involve Insteon Support in the process of backup the ISY994 or moving to eisy. That's all UD Support and UD Forum assistance.

Aside from the assistance @Techman has offered I'm a bit confused. Can you confirm something for us? Is the ISY994 still running devices or have you moved to IoX on the Polisy? Your comment in the last sentence made me ask this: "I'm just trying to get Isy running on my Polisy" If the ISY994 is still the controller for the Insteon devices and you changed the PLM did you go through the process outlined in the wiki? Do you have any battery devices that you haven't re-linked correctly after replacing the PLM? If the ISY994 is no longer in the mix (then why did you mention it?) you might need to open a support ticket directly with UD to get help getting past where you are on IoX and PG3. I don't know if the Polisy is stuck because you aren't on PG3x on the device or if there's something else hung up at 5.4.4. Open a support ticket with UD: https://www.universal-devices.com/my-tickets

If you don't know which Universal Devices product you're using you probably aren't using one. You can review their website for information related to what they offer: https://universal-devices.com/ It sounds like you're just using a Hue Hub and directly operating it through Alexa. Not sure how that works so I can't help you. Maybe others can, but you're probably better off looking for specifics for Alexa and Hue products. Good luck on your adventures!

No need to change PLM again. I also have the serial and moved it from my ISY994 to eisy without issue using the serial to USB converter cord available at the time the eisy came out. It appears UDI is offering a different cable now that doesn't require going from the serial to USB cables so it might be shorter and one less thing to worry about in the communication aspect. It does concern me that you just replaced the PLM on the ISY994 and you think either it or the ISY are flaky. Might be worth making sure you have a solid backup from the ISY994 before migrating to the eisy to avoid bringing over any funky issues. I will make sure to suggest to you that you make a "hard copy" of all your programs currently on the ISY994. On the Program tab right click on the root folder (usually "My Programs") and use the last menu item of "Copy to Clipboard". Then paste into a text app (for Windows I suggest Notepad). NOT into a word processing app/document - you don't want to risk auto formatting changing things. Save this file somewhere so you can reference the programs after your migration. If you have Z-Wave or are not on 5.x firmware on the ISY994 there might be some adjustments needed for the programs and this file will help a lot of steps with correcting any program issues that might occur.

@NinjaNun welcome to the Universal Devices forums. The hub here would be a Universal Devices hub running ISY (either an ISY994, Polisy, or eisy). Do you have any of those hubs in the mix of what you're attempting to fix?

When did you update to PG3x? And I know you said you did a power cycle recently, but there was a post from @bmercier that the 503 error was from UDX not running. The best way to trigger that is a full power cycle. If you recently updated to PG3x it's quite possible something was stuck in the update when power got pulled last time. Try running the update packages process in Admin Console. (I know this isn't anything to do with PG3->PG3x, but can "cleanup" other functions) If you have UD Mobile connected to that device you should get alerts for it going offline and coming back online and probably even time to reboot. Wait about 2-3 minutes after that reboot notification then use the multi function button to shutdown (three presses). I forget if Polisy shows lights when it's shutdown or not. Then pull the power supply, wait 30-60 seconds and power it back on. Allow several minutes for the device to start up and settle. Should hear some beeps, but also monitor the front lights if you have it in an area you can see the front of the device. If after this still cannot access it I would suggest opening a support ticket. https://www.universal-devices.com/my-tickets

My suggestion - don't run anything! Windows has gotten a little better (IMO) with their own security defender or whatever they call it and their firewall has been improved greatly. I haven't run any 3rd party virus software since Win10 came out. I also try to make sure not to visit unhealthy sites and don't randomly click on email links...so that might help some. If all you want/need is anti-virus I like ESET (not a big drain on resources). I run that on my son's computer and it doesn't impact anything he does (lots of gaming). Since you're still getting some java errors and other device issues after setting up the eisy I still think it's either computer system or network related issues you're experiencing. Those are hard to diagnose through forum posts so do think @paulbates suggestion to open a ticket would be beneficial to your issue(s). As for the PG3x access make sure you're using the same user/pass as you use to access admin console. Those the same and only changed via the admin console side. Your picture was very low quality so couldn't tell the exact error. It appears to be a 503 error. This usually meant UDX is not running. If there aren't any updates pending or installing then a full power cycle of the device might be needed. Have you updated the eisy to the current IoX and PG3x? Current release versions can be found here: https://forum.universal-devices.com/forum/339-current-release-announcements/ (click the "Follow" link in the top right of that page to get alerts when new releases are announced.) Glad it went mostly okay. I expect a support ticket will help you greatly. Please post back what ends up helping/resolving the situation.

What happens if you move the time constraint up into the ( ) of the first and statement? Long shot, but first adjustment I might suggest since you say it works fine without the time constraint. Also, is your "switchB" and "switchC" using a "status" or "switched" qualifier? 1st edit: And ( switchB is on <- Is this using "Status"? or switchC is on <- Is this using "Status"? And From 3:00:00 AM To 1:00:00 PM (same day) ) I just made a test program and it worked either way. Post your actual program. You might be using switched where status would be correct. Test and-time - If 'Lamp' Status is not Off And ( 'Office' Status is On Or 'Bed1Lamp' Status is not Off ) And From 6:30:00PM To 7:30:00PM (same day) Then Set 'Office Fan' On Else - No Actions - (To add one, press 'Action') Mine triggers true if I turn "Lamp" on - I was testing with admin console and Alexa so used "status" rather than "switched" (meaning physically activated). If you're "switching on" "switchA 1" with an app, voice command, or another program then you have to use the status. Only if you are manually operating "switchA 1" will it work for "switched open". Since you might be testing outside of your time constraint you should adjust the end time to a time later than your current time so you can run the IF to get it to test currently and not wait until tomorrow.

Going from memory because I installed this ages ago and haven't had to change anything since so hopefully it's still simple. When you installed the Hue plugin (formerly node server) press the button on top of the hub and the plugin should find it and pair to it. I think you might have to restart the plugin. I don't remember if there was a "find hub" button to click when the plugin is first installed/restarted and no hub found. However, try just restarting the plugin and then pressing the button on the hub within about 60 seconds and the hub should be found. You might want to put the logging into debug mode and watch the log run as it pairs with the hub. Once it's connected I would suggest restarting the plugin again and it should pull in all the devices. Please make sure you set up an IP reservation in your router for the Hue Hub! From the notes on the readme for this plugin: This was an issue a lot had in the past, and most will stumble into this if/when they replace routers and the DHCP table changes. Additionally, if you happen to have multiple hubs you have to use a strange way to add the IP addresses: In the configuration area add a custom parameter: bridges Then the IP should be in this format: ["10.0.1.1","10.0.2.1"] Be sure you include the brackets [ ] and the quotes around the IP addresses of the bridges! Lastly, make sure you have admin console closed (not running) while you add plugins. The only way nodes are added to the admin console is at load so if it's open and you add plugins and get new nodes showing in Polyglot dashboard they won't appear in admin console until it is reloaded. Same for UD Mobile, you will need to synchronize the app once things are altered/setup. Hope this helps.

No, but we need a lot more information to help further. I don't completely know how to review/support link tables so others might have other ideas about why they're looking this way. To help deeper please let us know the following: What type of device is turning on? How old is the device? (are you able to see the address/date tag/sticker on the device?) What IoX Firmware and UI are you using? (Admin Console: Help -> About) Make sure they MATCH Perform a "Find/Replace" on the Programs list Right click on "My Programs" folder (root of the program tree) "Find/Replace" Search for the device that is turning on (don't replace it with anything, but just find what programs it is referenced in. Then see if those programs have run unexpectedly) Check your program summary tab to see if a program has recently run to turn the device on How did you setup/migrate to the eisy? Did you come from ISY994 or Polisy? Did you use the same PLM you had before? If you changed PLM did you follow the replace PLM process? It might be as simple as factory resetting the device then performing a restore from the IoX admin console.

Make sure if you're setting these parameters in admin console to click the "button" to the left of the on level and ramp rate. You should see it change "writing" in the device tree momentarily and maybe a "system busy" box pop up and go away. Having to click the button has been a quirk in the admin console since 5.x was introduced. It's not intuitive as many will use the "Write Changes" button at the bottom of the screen. Edit: I just tried with UD Mobile (I had AC open) - had same issue you reported that if I changed on% and ramp rate it did not seem to change. I closed admin console and ran a sync on UD Mobile and the on/off ramped correctly and to the on%. I then reset the on% to 100 and ramp rate to .2 seconds and it correctly updated and operated. I then changed back to lower on% and slower ramp and it worked. Do you have admin console open when you're making the changes on the app? Have you run sync on the UD Mobile app recently? I only ran sync once. Again, my tests were on an individual dimming lamp link device, not a scene. Scenes are a little different monster than controlling the device directly. Can you post a screen shot of the KPL scene? Should show "Device | Action | Status" information. Post of the root of the scene and any controllers of the scene. I'm not very strong in diagnosing scene issues, but know many others here are and maybe they can help at the scene level.

@Nishal & @737simguy not a direct update from @Michel Kohanim, but posted in another thread that they're "very very close".

YES! When you use the Portal URL and connect with the "cloud" option you have to use the my.isy.io portal credentials.