paulbates

Let's start by seeing if its ISY wide, or just the portal. Assuming you have an NTP server configured; open the admin console, go to the configuration tab and click "Synchronize Now" under Clock. Try the "Test" button under Email/Groups Did those work? Yes-Its portal specific, I would submit a ticket to UDI for help No- Something in the new router is not letting the ISY "dial out" Paul

Hi Tim There is a known bad interaction between wireless sensors like motion sensors, ISY programs, and what you are describing... the vernacular is an "ALL ON". Start with this and see if some of the problems go away. Take a look at this thread and specifically things to look at in your programs that respond to motion sensors Paul

Renato Wanted to double check, you did a "restore device" after the factory reset? Not restoring after the reset would give those symptoms Paul

I would recommend you try the factory reset suggested earlier. I have older togglincs that "lose it" after a few years of continuous use, and then behave normally once reset. It only takes a few minutes to try and costs nothing if it doesn't work Paul

Hi Renato Can you confirm: You have an intermittent problem with one switch The scene turns the light on, but the admin console shows it as off Also, did it always work correctly in the past and this is a new observed behavior? If that's right, I would suggest Leave the switch configured as normal in the ISY Go to the switch and factory reset it From the admin console, 'right click' on the switch and pick "Restore device" Give that a try for a few days and see if it fixes it Paul

Flagging @InsteonNut, the mobilinc author, to see if he has suggestions Paul

It was right to suspect the PLM, but since everything is working in the admin console, that rules the PLM out as a problem. Paul

Hi David It doesn't say for sure in your write up, does the device status show correctly in the admin console? If you turn devices on and off the admin console updates appropriately? Paul

I would try rebuilding a scene. Pick one of the devices in a scene. Right-click on it, and pick Restore Device. Retry the scene afterwards If that doesn't work, you might have to rebuild the scenes, unfotunately Paul

Hi- there are a few things, try these ideas Unplug and replug the PLM, retry Try "Restore Modem" from the file menu in the admin console (you may have to visit wireless devices like motion sensors and put them in linking mode) If those don't work, how old is the PLM, this is the symptom of a dead PLM (> 2 years)? Paul

Here is a top level wiki page that references the various portal related topics http://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Portal:_Integration_with_Amazon_Echo.2FGoogle_Home.2FIFTTT The two at the bottom of the list might be of the most interest to you; Admin console and mobilinc Paul

Larry, Originally I had the the "Repeat every XX minutes" in the program above. You pointed out run-time problems with timing when using the Repeat statement this way. I experimented and switched to the the "Repeat While $True = $True". The problem was timing related, and I can't remember the specific behaviors now, but this way has worked more predictably. Paul

Hi MJsan, welcom to the UDI forums! I don't use a switch to turn this on, but the 'then' of the program will give you what you are looking for in terms of cycling until the program's If logic becomes false HVAC Cycle US Fan - [ID 0030][Parent 0017][Not Enabled] If 'HVAC / Upstairs' Heat/Cool State is Idle This stops cycling if the system has been normally heating/cooling And 'Attic / Attic- Damper Control-Relay' Status is Off If our attic damper / fan is on, don't cycle as outside air is moving through (you could put your switch command here instead and/or call the program from the portal/alexa) Then Wait 22 minutes When the AC has run, this give the condenser time to drain and not blow the moisture back into living space Repeat While $True is $True True is variable that is set to 1, eg run forever (unless program If logic becomes false) Set 'HVAC / Upstairs' Fan Mode On How I turn my fan on $V_US_Fan_Cycle_Sequence += 1 I keep track of how many cycles, for reporting, not necessary Wait 10 minutes I turn on and off every 10 minutes Set 'HVAC / Upstairs' Fan Mode Auto How I turn my fan off Wait 10 minutes Pause 10 minutes in "off mode", then the repeat starts again Else Set 'HVAC / Upstairs' Fan Mode Auto Make sure fan is shut off on the way out This program cycles the fan when nothing has run to filter the air. The heat and cool commands are controlled by Nodelink

Hi Colin Welcome to the UDI forums! Some questions: In your SMTP settings on the ISY, are you using "default", or did you configure your own. If your own, which one? The default server is not recommended, and its recommended you use something else gmail as an SMTP provider is well documented / popular You most likely did this, but did you test the group separately from the ISY using: another outlook account on your server? from a regular internet email account? security related software on mail servers sometimes decides it does not a particular sender Paul

6 or 8... doesn't matter. It takes a little care, sometimes the switch plate gets in the way. I've used a very small screwdriver to lightly pull back on it from the bottom. (If it was an 8 and changed to a 6 in the past, it will become an 8 again. I can help with that, but lets see if its a problem first) Paul

I have them "lose their marbles" sometimes. Sometimes powerline problems can confuse them. Try this Leave them configured in the ISY Factory reset them: Pull the tab at the base out for 10 seconds Push it all the way until it beeps, then hold it for 3 more seconds Release the tab From the Admin console Find the device 'Right click' on it Select 'Restore Device' Wait for the messages from the ISY to finish (If any wireless insteon devices are involved in scenes with the switch (motion sensor), they may have to be put in linking mode) Test the device again Paul

To add to Larry's comments: Something else to look at is the internet speed provided at your remote site. Usually internet service is asymmetric: One faster speed for download and slower speed for upload. That works great at the site, but is a limiter for times like this.... wherever you are running the admin console remotely, you are constrained by the speed which the remote site can upload data across the internet - like loading the admin console remotely. The admin console loading can be a big job... typically we don't feel it as the ISY is right there by our home computer with few network constraints, but over an internet link its a different story, and made worse by a limited upload speed from the remote site. In contrast, Mobilinc is sending and receiving small individual messages for each device, its load is not a great as the admin console starting up. What type of service do you have at the ISY's location? (Cable, DSL, ...) Do you know what your upload and download internet service speed is at the ISY's location? My recommendation would be to try again; login to the Admin Console, but let it sit for 10 minutes or so before trying to do anything, then try clearing the messages. Paul

Hi Eric One of the things that the Network Module does is exactly that; program controlled network calls in various formats. You can either buy the network module outright, or its included as part of the ISY Portal subscription. Its in the Admin Console under Help/Purchase Modules Paul

Hi Chuck You'll need 2 recipes and 2 ISY portal entries, one each for setting the variable to 1 and 0 Name the two events: (InGeofence . OutGeofence.... something like that) Pick the geofence state variable (Same name in both) Set one to 0 and one to 1.. whatever logic works for you In Maker and the geofence, one recipe for in and one for out For each recipe, paste the URL 0 or 1, you want in the URL box for Maker "make a web request" Be sure to set the Method to "Post". It won't work otherwise You don't need to change the other settings Paul

Hi No, there is no intrinsic blink function in the keypad, you'll have to do it with ISY program statements as you've done. Depending how busy your ISY is with other things, a second may be a little tight timing for a regular, consistent blink. Something else I do periodically to signal an event or draw attention to the keypad is use the "beep" function. If the garage door is up and its later in the evening, I have it beep periodically. Version 5 of firmware (which is in alpha/beta) offers more sophisticated logic with the Repeat statement. Paul

Robert Hmmm. You maybe looking at a rebuild, if no other suggestions come. You can go to the support link on the main udi page. Write a brief summary and a link back here. They are great about responding Paul

Robert Try this test: For a few of the devices, right click on them, one at at time, and pick restore device. Rerun the test for status updates. If it works, you'll need to go through all of the devices, one at a time, with that procedure. Wireless devices need to be put in linking mode before using restore device. Its also possible that some devices won't cooperate with this procedure and will need to be deleted and reinstalled. Paul

It did what it said for me, shorter range and no delay. Mine is on the corner of the house... half of it covers the back , half of it covers the front yard and driveway. The problem with no jumper is that people walking by on the sidewalk, or some cars on the street would set it off and I didn't want that. They jumper simply "brought in" the detection field. It works great now.

One possibility is sensitivity. Screens, even glass, don't matter, the MS sees heat. Any cooler conditions... cloudy, night, makes heat signatures more visible to the MS. I added jumper 1 to my MS which reduces its sensitivity 33%. That has got rid of my false triggers and is pretty easy to do. You can also try mounting it higher and pointing it lower. Paul

Hi Can you confirm if you followed the procedure identified in here? http://forum.universal-devices.com/topic/19331-my-plm-died-and-i-bought-a-new-one-what-should-i-do-next/ It sounds like you need to perform a "restore modem" Paul