MrBill

I don't know if you're asking about an indoor soffit or outdoor soffit, and either way I have no specific product to recommend. However if outdoor I would absolutely use some type of RGBW fixture and control it via some other method.

As mentioned the boot process of the ISY is such that the PLM must be answering queries before the point in the boot process that the ISY asks the PLM for its (the PLMs) Insteon address. Normally it's suggested to plug the PLM in ahead of the ISY by a full 30 seconds, however that's much longer than is actually needed. Also missing from this thread is the possibility that somewhere in your system plain old garden variety noise (or signal sucker) has been introduced. this generally comes in the form of something a user plugged in without realizing it the cause.... one example is a battery charger for some new appliance. Two examples I have personal experience with: We previously had a deep fryer that got plugged in about 1 hour per week... during it's use insteon behave very erratically, all returned to normal as soon as it was unplugged. Second, Once-upon-a-time a storm took out the switch I had controlling the attic fan. It caused my entire Insteon system to fail rather dramatically. However once we started turning off breakers we quickly identified first the circuit and then the device that was faulty, once it was removed from the system everything returned to normal.

are you certain the query is tripping the GFCI or is the GFCI tripping at some point and the query is discovering that fact for you?

@dex Keep in mind with wireless sensors traffic is one way, and the sensor decided when to send heartbeat and low battery. Those values will remain unpopulated in the the ISY (or IoP) until the sensor talks. Have you waited 24+ hours for the heartbeat. What model wireless sensor? what heartbeat program are you using? (hint right click the name in the program tree and select "copy to Clipboard" from the the context menu and then paste into a forum post. Asking because there are multiple heartbeat programs used. Some will autostart with the first heartbeat, at least one needs to be manually started.

Polisy likely won't ever be in stock again, due to worldwide hardware availability issues (a.k.a. "the chip shortage") Polisy has been replace in the lineup with "eisy" (all lowercase). Availability was once stated I believe as "mid-September", no idea what the current time projection is tho. Unlike Polisy, I don't believe there was a pre-sale.

NodeLinc has a datalogger. you'll need a pi to run it tho. Home Assistant with the Universal-Devices integration does some logging automatically, I haven't yet figured out how hang onto it, like temperatures that I want to record long term. (haven't spent much time on it yet, but do have it on a list of things to learn/figure out.)

I've been out of the country for a week, so just getting to this, My first steps would be to factory reset the module then use "restore device" from the ISY. If that didn't solve the problem then full delete from the ISY, factory reset the module again, and re-add. with this method you'll also need to recreate scene's and programs.

If you can intercept the line feeding the outdoor outlet you could use an insteon dimming switch and locate it indoors. Technically you're not supposed to dim outlets. At my son's house an outlet was installed at the gutter line just for string lights and it's controlled by an insteon dimming switch mounted high on the wall in the 2nd floor laundry room, the switch was mounted at 6 feet so that people that didn't know its purpose wouldn't try to use it.

@fisix Answering your backup restore questions. Backup the ISY frequently. I keep all backup for around a year or whenever I think to go prune that folder since i never really look at it. (I keep all because in the event of a corrupt backup and can just regress until i find one that works.) In the event that your ISY994 needs to be factory reset, you would do that first. It comes back up with basic boot loader firmware, at which time you refer to the filename of the backup that you want to restore to find what firmware version you were running. Then download and re-install that firmware version, finally restore your backup. Factory reset Install Correct firmware Restore backup

You'll be quite happy with Pushover if you'll just try it. It gives the same type of notification a text gives, with the added advantage of it's faster and it's reliable. There is a basic learning curve, but once you're past that you'll be in much better shape. Additionally you can log all the devices into a single account. No recurring fee, just a one time fee for the app that you only pay once... not per device.

the only way to do this is via the email to text gateway. this has become unreliable because many spammers use it to send spam text. there is no API for send text messages, therefore the only way to do it is via the email to text gateway. this method has been unreliable for a long time, longer with certain carriers than others but it's pretty much not the method to take. I've posted alternatives many many time over the years. One is to use Pushover either via node server or direct from Network Resources, or a combination. Or another is to install a seperate email client such as Spark Mail on your phone just for email messages from the ISY. I have this method set up and actually use the same comcast address for outbound email via the ISY as incoming via Spark Mail on my phone. With any of these alternatives you can have push notifications. What's not reliable and hasn't been for a long time is email to text. I've posted on this subject so many times I'm a broken record I should just start linking to the last time I said it.

off the top of my head, did you try rebooting the ISY? Is your subscription current? Check the expiration date in the portal Select Tool > Information > Portal Access License.

You should upgrade to 5.0.16C. Your 5.0.14 version is a very old beta version (i looked for the release date and couldn't find it), while 5.0.16C is also a beta version is very stable and there were many fixes and improvements between .14 and .16C

sounds like a routing problem. You have communication in one direction but a rule blocking communication the other direction. Don't factory reset the ISY.... it's the NEW router. That's what changed.....

What Z-wave version is displayed in the admin console? (access that from the Z-wave menu on the top line of the admin console.) if version 4.55.00 you have a 300 series Z-wave board. You should upgrade to version 5.0.16C and stop. if version 6.81.00 you have a 500 series Z-wave board (which is what you said above that you have). In this case upgrade all the way to 5.3.4. in any case 5.0.14 is a beta version that’s out of date and should be replaced with either version above.

Fastest solution is open a ticket, support@universal-devices.com sometimes backup fails are delete file, sometimes they are reload the firmware.

This statement is incorrect. You should upgrade the firmware to v5.3.4. 300 Series z-wave does have a firmware limitation, but that is 5.0.16C. You don't need the variable either: If 'Lower Level / Family Room / Family Room Motion Sensor / ZW 018 Motion Sensor 1' Status is On Then Run Program2 (then) Else - No Actions - (To add one, press 'Action') ---- program2 If (blank) Then Disable Program1 Set 'Aquarium Pump' Off Wait 10 minutes Set 'Aquarium Pump' On enable program1

the wait ends when the IF statement retriggers, you need two programs: If 'Lower Level / Family Room / Family Room Motion Sensor / ZW 018 Motion Sensor 1' Status is On Then Run Program2 (then) Else - No Actions - (To add one, press 'Action') ---- program2 If (blank) Then Disable Program1 $FR_Motion = 1 Wait 10 minutes $FR_Motion = 0 enable program1 ---- that said I'd suggest posting about what you're trying to actually accomplish, because you probably don't need the variable at all. Else - No Actions - (To add one, press 'Action')

The link I provided requires editing.. the capital letters must be replaced with an actual IP address. I'm not sure what wiki page has a .jnlp file, could you please link that wiki page?

I agree. I posted something almost identical this post in the early days of PG3.

An ON/OFF plug in module can be added to a scene as a Controller. It doesn't do what OP thinks tho, instead it allows the manual button on the side of the controller to be a scene controller.. (on dimming modules with the "sense" feature for manual control, the sense feature will also update the scene if the module is a controller in the scene.) We need to see your programs related to this, right click the program name, then click "copy to clipboard" (the last item on the context popup), then paste into a forum message. In addition it might be helpful if you click module in the tree and show us the "membership" boxes on the far right side of the screen that show how you scene is setup If you want it prevent it from being on overnight while we are searching for the real problem you could use a new program like this: If From 10:00PM to 7:00am (next day) AND Status 'Amp Module' in not off then Wait 10 seconds set 'Amp Module' off That's just a band-aid until the real issue is discovered.

@NCannata You can avoid using ISY launcher by downloading admin.jnlp from the ISY and launching it each time instead. If you ever do upgrade you need to remember to delete admin.jnlp and clear the java cache manually which are some of the things that ISY Launcher helps eliminate the need for. http://IP.OF.YOUR.ISY/admin.jnlp Save the file, move it to your desktop.

a 300 series z-wave board has a Blue LED that fits into a hole in the case near Port A. a 500 Series z-wave board does not have an LED 300 series z-wave boards report z-wave version 4.55.00 in the admin console. 500 series z-wave boards report z-wave version 6.81.00 in the admin console.

Fastest fix is probably open a ticket, support@universal-devices.com they can also answer the upgrade question. they do answer tickets on weekends... just slower than weekdays.

Correct. From the wiki documentation for Google Home: For Programs: Turn On: “Ok Google, turn on the kitchen light” - runs Then Turn Off: “Ok Google, turn off the kitchen light” - runs Else However, if you wish to test a condition just link to another program. For example make the Then body that google home Runs simply be a single line: AAAADelete - [ID 0135][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'BarnOHD' (If) Else - No Actions - (To add one, press 'Action') You'll actually need to create the second program first, so that it can be included in the Then. Also the second program can be disabled, so that it won't run from any condition in it's IF statement. Disabled programs still run when run by another program.