tmorse305

Solved! This was my issue: Admin Console Minimized/Invisible and Cannot be Restored This is usually related Admin Console state files not being updated properly and especially in case of multi monitors. All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.* file patterns: udi_tree.state udi_frame.state udi_pgm.state udi_finder.state udi_launcher.state Thanks again to @Michel Kohanimfor the great support he provides.

Thanks I did that at Michel's suggestion but it didn't help unfortunately

@MrBill, thanks for the reply. I have cleared everything a few time to no avail. I was reading online about the error I received, it was suggested that you uninstall Java. I just did and then reinstalled. Still not working... Update: I figured out how to enable the Java console. Attached is the trace starting with launching ISY Finder and selecting the AC. I wasn't sure how sensitive the finger print information is so I chopped a bunch of digits of the end of each one just to be safe. Maybe this will help with the troubleshooting. Thanks,Trace from Java console.txt

Yes, although I tried it both ways, the launcher and http://myisyaddress... Same result Clarification: I only see the error when I use the http://myisyaddress... If I use the Launcher it just hangs, no error If I use the launcher to access the Dashboard instead of the AC, it works, I can get to the dashboard and it works normally

I know there is an active thread already on this topic with a user who has a new computer. I didn't want the dilute his effort to get it fixed. After reading his thread I clicked on my ISY icon on the computer I used just yesterday to access the AC. The ISY finder opens and it hangs. I had to use task manager to close it. I updated Java, cleared the cache and downloaded a new finder. Same result, it hangs after the ISY finder opens. If I kill it and try again, this time I get an error. Any ideas on how to fix this? Thanks. Note: Firewall is Defender and same result if it is on or off.

@smokegrub, It's actually worse in the window because of the coating on the glass. The signal drops 14dBm when I move the tag manager from outside to inside the glass! I just moved the tag manager outside temporarily to see what happens. It is direct line of sight to the mailbox, I can see the tag, it is less than 100 feet. I'm not sure how quickly the tags drops the power down so I'll let it sit for a while. Right now it's still at 100% power after about 5 minutes and multiple manual updates. When I bring the tag into the same room as the manager the power drops to 1% as you would expect. Update: Solved. It is a tag problem specifically all of my accelerometer tags. I just tried a regular motion tag and it works fine. Bummer because they discontinued the accelerometer tag. I sent all of my tags back recently for a firmware update. I wonder if in that process something got messed up.

@larryllix, how do you have your tags configured to get such incredible range? I can't get the tag at my mailbox to work reliably at ~100ft! The tag manager is up against the front wall of my house, it can't get any closer to the mailbox and still be inside. It's about 8' off the floor. The mailbox tag is on the bottom of a metal box, spaced about an inch off on a wooden block. I use an accelerometer tag so that it triggers from the vibration of the door opening and closing. The tag runs at 100% power so it quickly kills the battery. It didn't use to do that so I thought the tag might be bad. I tried others but the result is the same, 100% power. I have the tag manager mode set for medium, I've calibrated the freq offset at temperature. The tag wireless setting is set to low power mode. I'm beginning to wonder if there is an issue with the radio in the tag manager. Any advice is appreciated, thanks.

https://forum.universal-devices.com/topic/10516-random-all-on-event/

Do you want to know if the fan has power or if the fan is turning? It looks like there is a tachometer terminal on the fan you are showing. No wire attached.

Assuming by "worked fine" you mean the doors actually opened (just checking to make sure the circuit has power) then the most likely cause is interference. Have you added anything new that plugs in? UPS, new brand of LED light bulb, etc, a device with a 'fat' plug?

What you described in an earlier post might not be a factory reset, that's why I included the instructions in case you were not familiar with the process. Do you hear any beeps? You might need to hold set button longer than 3 seconds to hear the beeps when you release it.

What light comes on when you press the set button, the LEDs or the light the switch is controlling? In any event it sounds like there is power at the switch. Try a factory reset. Wall Switches & Keypads Disconnect your Wall Switch or Keypad from power by pulling the set button out Press and hold the set button Continue holding the set button until the beep stops If your device does not beep, hold the set button for ten seconds Release the set button. You should hear two beeps confirming that your Wall Switch or Keypad has been reset

The LEDs you are referring to are on the dimmers correct? Are the 2 dimmers in a 3way circuit? In other words the 2 dimmers are supposed to control the same light? If that's true then the dimmer that is dead maybe controlling the load and while the other is working but unable to operate the light. Are these Insteon dimmers? If so make sure the small button is pushed in and not sticking out. Maybe the circuit breaker is tripped?

PLM's have a poor power supply design that all but guarantees premature failure. Right now there is no other option but the PLM. I would hang on to the failed unit. You cannot buy a replacement right now, out of stock. They have been for sometime. The broken unit can be repaired.

@markv58, You're probably right... thanks, totally missed that in the change over.

@markv58, I was just checking the others and I would say 'sort of'. There are data changes on some but if I query I get a failure. The IP of the Polyglot did change, My whole network went from 192.168.1.x to 192.168.4.x

Thanks @markv58Sorry that wasn't clearer, I have already updated it in two places, within the Polyglot setting and within the virtual NS. The log looks ok, no obvious errors

@markv58, I having trouble getting the nodeserver to communicate with my ISY. Earlier today I had to change the IP address of my ISY. That of course ripples trouble in all directions... I have updated the IP address in the Polyglot settings and the parameter within the node server. I have have restarted the nodeserver and the Polyglot and the ISY but still no luck. From the ISY side the nodeserver reports to be online but when I try to operate and virtual switch ISY comes back with an error, "request failed" I get the same response if I try the button on the controller node, "query", "update profile", etc Any suggestions, Thank you

I think you will need to extend your wait time from 25 second to 55 before you can attempt to trigger again. The 2 variable changes both create 30 second exclusions based on what I saw with the experimental routine I shared with you in the other thread. If you trigger again after the 25 seconds delay the vocal might not happen. This is what I found $sMS_Test_1 = 1 Wait 5 seconds $sMS_Test_1 = 0 Wait 30 seconds $sMS_Test_1 = 1 Wait 2 minutes $sMS_Test_1 = 0 The second voice prompt occurs 60 seconds after the first one. With this setup: $sMS_Test_1 = 1 Wait 5 seconds $sMS_Test_1 = 0 Wait 25 seconds $sMS_Test_1 = 1 Wait 2 minutes $sMS_Test_1 = 0 The second voice prompt never happens.

This now explains why my routines work but not yours. I only use 1 and 0. I got burned a long time ago when I had the variable being assigned other values. Sorry I didn't realize sooner that you were doing that.

@larryllix, I created another test routine that triggers on 'not detected' just to make sure there was no difference in the way that Alexa responds. It seems to operate the same way as using detected. In the process I did discover one surprise. I can fire the 2 programs back to back and I get both voice prompts, one right after the other, no 30 second delay. It seems that Alexa is treating them as independent events with their own 30 second exclusion periods.

I've noticed that events shorter than 3 seconds on the ISY side don't show up in the Alexa app when I watch the device but do trigger the routines.

@larryllix, I played around some more with the delays to see if I could get a better understanding of what is happening. With this setup: $sMS_Test_1 = 1 Wait 5 seconds $sMS_Test_1 = 0 Wait 30 seconds $sMS_Test_1 = 1 Wait 2 minutes $sMS_Test_1 = 0 The second voice prompt occurs 60 seconds after the first one. With this setup: $sMS_Test_1 = 1 Wait 5 seconds $sMS_Test_1 = 0 Wait 25 seconds $sMS_Test_1 = 1 Wait 2 minutes $sMS_Test_1 = 0 The second voice prompt never happens. Here's my theory on what going on. It seems any change to the variable state triggers the 30 second exclusion period on Alexa. If another change comes along before the 30 second has expired, it's put in a queue and is acted on when the 30 second period has ended. Then another 30 second period begins. But the queue is only one deep, if another change comes along before the queue is cleared, it either ignores it or overwrites the queue with the updated value. Either way Alexa misses the next transition so there is no second voice prompt.

I hope you hear back from them, I have made a few requests in the past and been promised follow up but alas still waiting... On the 2nd 30 sec wait, actually it is necessary. If I delete it, I never get the second voice response. If I shorten it to a couple of seconds the 2nd voice response comes about 30 second later. With it set to 2 seconds the voice response was nearly coincident with the variable resetting to 0. I thought I had duplicated your issue until I realized what was actually happening.

@larryllix, that is bizarre. I created a test program on ISY today to play with this: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $sMS_Test_1 = 1 Wait 30 seconds $sMS_Test_1 = 0 Wait 30 seconds $sMS_Test_1 = 1 Wait 30 seconds $sMS_Test_1 = 0 I get two reports from Alexa repeatedly, when the variable is set to 1. I played around with the wait times to see if I could get it to ever trip on the variable setting to 0 but no luck. If I reduce the middle wait to 1 second then I can create the appearance of the trigger on the set to 0 but it's obviously just delayed from the previous set to 1. Hopefully Benoit can shed some light on this for you.