MrBill

Again, I would just make 3 scene's. None of which have Adjust scene as a component. Then the programs will just do one thing.. turn on the appropriate scene at the appropriate time.

@Michel Kohanim so my take is that it seems this long running problem that we've never nailed down is the result of some error in the ISY that results in confused subscriptions, and agave and ekeypad both seem immune, or actually can help resolve the problem. to recap: Generally after the error has occurred mobilinc pro users will see "Mobilinc Disconnected... attempting to reconnect", upon subsequently attempting to open the admin console they will get the "Already Subscribed" dialog box from the admin console, there is no obvious way around that error short of rebooting ISY. Rebooting the ISY cures all, until the error happens again. @TrojanHorse first reported here, that ekeypad could be used to create a "fix". I later did the same thing with agave, however I only used one phone (as opposed to his two). Those fixes only worked tho if you didn't try to open the admin console, once you tried that you would enter the "already subscribed" area of the problem. I can't recreate the original problem anymore to test new theories because my ISY pretty much is running error free, and mobilinc works without fail whenever I try it. (at some point last summer I was trying hard to make the Mobilinc error occur, but couldn't because I had addressed the error log issues.) I don't know how relevant this is but: one thing that was contributing to my error log issues (a year ago) was that I was using a wireless tags kumo app at the time to get temp/humidity data into the ISY, moving that component to a Polisy nodeserver I believe got rid of a lot of the errors.

I agree with @Screw Loose Dan , I would not adjust scene, but create multiple scenes. Also I agree that you should post your actual programs rather than type your interpretation of them... But if you knew how to do that you would have done it because its faster and easier..... to copy a program into the forum click the program name, then right click... the very bottom item on the context menu is "copy to clipboard", choose that, then paste it into your post by right clicking and picking paste or just typing control-V.

Please try downloading the file again, its possible the file your loading to the ISY is corrupt. Be certain that you're downloading the correct file for your ISY (PLM vs No PLM), and don't unzip it after download, just upload it to the ISY as is.

Right Click "My Programs" There are options to find devices, scenes, variables, etc.... note that Raw Text is case sensitive. TO my knowledge yellow hi-lited programs do not run. I've only seen them twice tho, once when I upgraded to 5.x and recently when i did actually delete an Insteon module by mistake.

Actually Mobilinc Pro does work with iOS 14.3 I've mostly moved on to other methods but do on rare occasions open Mobilinc Pro to do something that hasn't been planned for. For example, after midnight last night when we got in bed I realized I had over ridden outside lighting to the 'early evening' scene and needed to move it back to the 'late night' scene, I did use Mobilinc Pro for that, worked fine. When you say "unreliable" do you mean that it works sometimes but then for unexplained reasons you start getting a popup at the bottom of the screen that says something like "mobilinc has disconnected, attempting to reconnect"? At that point it becomes maddening to get mobilinc to re-connect? If so, I've been there, and so have some others in this forum. If you open the admin console at this point in time, do you get an "Already subscribed" dialog box? Then you reboot your ISY and it takes care Already subscribed, and mobilinc also works again.. for awhile? The above described bug was what drove me away from Mobilinc a couple years ago. I can't tell you EXACTLY what fixed it for me, but around a year ago I was having weird ISY issues and discovered a lot of Queue Full Errors and other things I couldn't explain in the ISY error log. I ended up opening a ticket, it was a very frustrating experience, but eventually got it so that there are very few entries in my error log on a daily basis, since that time every time I make many changes I watch the error log like a hawk to make sure I haven't created something that creates errors (the ISY does a fabulous job of recovering from most, but some seem to have lingering effects). Anyway to make a long story short... I no longer have the "Mobilinc Disconnected / Already subscribed" bug. After @TrojanHorse and others revived the topic I began opening mobilinc everyday again, attempting to recreate the issue... I can't anymore. Knowing now that Admin Console "already subscribed" bug I was also attempting on 3 different iOS devices randomly thinking the subscriptions were just getting confused. I could never recreate it... the only thing I can say that was substantially different is that the discovery that I could no longer recreate the maddening Mobilinc bug was right after I attacked errors in the ISY error log.

The method I use is that every controllable plug-in module is labeled (Brother P-touch label maker) with its ISY node name, that makes finding the disabled nodes quick, then if they are repurposed I simultaneously relabel and rename in the ISY. This avoids having to delete and re-add in the ISY. I've also learned (the hard way) to search programs for the devices being renamed. Kasa plug-in modules also have a second label: kasa0, kasa1, .... that corresponds to it's name in the router's DHCP reservation table.

Have you tried a factory reset of the lamplinc followed by a Restore Device from the admin console? You might also try swapping two of the lamplinc's to see if the problem follows. Another issue might be Minimum load "small led Christmas lights" is a very minimal load. what happens if you add to it, temporarily to test... such as a 60 watt incandescent bulb...

To clarify what's been discussed so far. 2842-222 is a version 1 motion sensor, which is what @wdhille has 8 of. The screen shot showing battery level is for a motion sensor version 2 (2844-222) As @larryllix points to monitor or listen for low battery on Version 1 motion sensors you must have a program. I don't have any version 1 motion sensors but it would be very similar to the program below written for hidden door sensors. AllRecessedDoorSW - [ID 0044][Parent 0037] If 'Door Switches / Barn Walk-thru Door / Barn Walk-thru Low Batt' is switched On Or 'Door Switches / Costco Rm NEW - Door / Costco Rm NEW Low Battery' is switched On Or 'Door Switches / Front Door / Front Door- Low Bat' is switched On Or 'Door Switches / Garage to House Door 2 / Garage to House Low Battery' is switched On Or 'Door Switches / Green Rm Closet Door / Green Rm Closet Low Battery' is switched On Or 'Door Switches / Laundry Rm Door / Laundry Rm Door - Low Battery' is switched On Or 'Door Switches / MBR Closet 2 Door / MBR Closet 2 Low Battery' is switched On Or 'Door Switches / Playroom Door / Playroom Door Low Battery' is switched On Or 'Door Switches / Pool Closet - Door Sensor / Pool Closet Door - Low Batter' is switched On Or 'Door Switches / Pushbutton Block / Pushbutton Block.3 - Low Batt' is switched On Then Send Notification to 'Bill' content 'DoorName' Else - No Actions - (To add one, press 'Action') Then for the Custom notification email you would create: using the # replacement for the nodename. Note this works because the default nodename includes the words "low battery".

Click on Network or ISY at the top of the tree on the Main tab of the admin console. THEN in the right window click the column header for ADDRESS to sort by that column. EDIT: I was wrong... Click NETWORK, not either.... I didn't look closely enough at the folder structure.... I made a bad assumption...

Depends on how good you are with a soldering iron. I would tack on two more wires right there at the fan where you see the red and black wires attach. Probably the simplest way is to use some type of wire tap like this: https://www.amazon.com/Nicelux-Electrical-Connectors-Connection-Self-Stripping/dp/B07ZC4CTLW which crimps on.

https://www.amazon.com/HiLetgo-Channel-Module-Isolation-Support/dp/B00LW2H5GC/

What new thing have you plugged in recently? It's likely something that generates noise. If you can't think of anything unplug everything else on the circuit and try. IOlincs are not dual band so the powerline must be clean.

if the fan is 5V why wouldn't you just order the appropriate 5v Relay?

using a relay with the same coil voltage that the fan operates on. the contacts of the relay are 'dry contacts"

Observations: It sounds like you have connectivity via the portal. It also sounds like you have an old port forward but DHCP has changed the IP. Since it's been several years It's likely to assume that your ISY is running a v4.x firmware. There are a few methods of launching the admin console. Installing the correct version on your desktop is one, the Launcher which is newer is another. These are different methods. I would recommend making certain you are using The Launcher, for that follow the instructions in the link below, the Launcher will often times locate your ISY on the network, but not always. If Launcher can't find the IP of your ISY then most routers usually have a clients table although they all seem to name them a little bit differently. I would look further through the router interface to see if you can locate the correct IP. If you can't find it tell us the model of your router and we might be able to help figure out what to click on. Also tell us if your doing this on Window10 or a Mac, and if Mac which generation of MacOS.

in addition to what @Screw Loose Dan mentions.... The Launcher uses the internet and a UDI server to open the admin console. The purpose is so that you always open the correct version that matches your firmware version of the admin console. The Launcher is not required tho, you can use other means to open the correct version without that dependency... uses the launcher is just easier for most people.

If you were using the ISY's default mail server to send the message out to @vtext.com then contact support@universal-devices.com to get credentials to use UDI's mailserver. Or switch to another outgoing mailserver. Edit : quoted the wrong message in that thread. The whole thread is on topic tho. Basically Spammers found a server they could use without credentials and began using it.... so now credentials are required. Same thread has instructions for using gmail or other free services.

@lilyoyo1 is sending you to 5.0.16c for a reason. You can't go past that version with your current 300 series z-Wave board. Before upgrading beyond 5.0.16c you must upgrade the z-wave board in your ISY. UDI does have special pricing based on the age of your ISY.

Please study my post. The copy paste was not from a browser, it was from a polisy admin prompt. Then since 302 is the http code for temporary redirect and curl apparently doesn't tell us where to THEN I used a browser to check that.... good eye! Correct: https://pkg.isy.io/script/update121.sh | sudo bash

@ctviggen1 Someone else besides me should be making this comment, because I don't use z-wave and I may not be exactly correct, but in other threads I've seen it suggested that the device needs to be brought within range of the ISY. This suggests to me that Z-wave doesn't adopt well over its mesh network and needs to speak directly to the ISY. Some people have removed the device and hooked it up with a temporary plug-in cord and positioning it right next to the ISY. Perhaps a post in one of the Z-wave sections of the forum would get better attention than in this firmware release thread.

There have been default mail server issues. According to this post the server is back online, but now requires credentials.: Contact support@universal-devices.com as I believe they are issuing the required credentials on an as-needed basis.

likewise: [admin@polisy ~]$ curl https://pkg.isy.io/update121.sh <html> <head><title>302 Found</title></head> <body> <center><h1>302 Found</h1></center> <hr><center>nginx/1.18.0</center> </body> </html> [admin@polisy ~]$ Since 302 is a temp redirect, I checked and https://pkg.isy.io/update121.sh in a browser seems to redirect to https://www.universal-devices.com/ Whatever is happening it does seem to be @ the server.

You pass the motion detector and it does in fact trigger the first program, the next thing that happens tho is that you turn the switch off, at that moment in time the motion detector is likely still on, and program 1 becomes disabled, this ignoring anymore status changes. Once you've turned the switch off you've also disabled the motion program. And of course if you turn the switch off first, then motion is triggered nothing happens. Edit to add: Another point to remember is that Insteon communication is serial in nature. It doesn't transmit/receive two signals at the same time, whichever insteon device started transmitting first wins the powerline until it's finished speaking, then the next device begins speaking.

Because STATUS is being used, Program 1 doesn't know the motion detector is "on", Program 1 only knows what the motion detector last told the ISY, about its status. This is a troubling point for most new users, but Status means "what the ISY thinks the status is". The motion detector only sends it's status to the ISY when it turns on, or turns off. There is not a continuous update of status occurring-- the motion detector turns on, sends ON to the ISY, the ISY changes the status flag to ON, nothing else happens until the motion detector turns off, then it sends OFF and the ISY changes the status flag to OFF. In some cases (such as noisy power line) the status in the ISY can become confused because it missed one of the the communications. How CONTROL differs from STATUS is that control is actually watching for those signals being transmitted from the devices. So in the second program we are actually watching for the arriving signal to the ISY that says the switch has been turn off (which also updates the status flag in the ISY to off. Status = what the ISY was last told about the status Control = Actual incoming control signals regardless of current status.