"Else" portion of program

[larryllix]

3 minutes ago, lilyoyo1 said:

MS's are great for a lot of things. I use zwave and Insteon sensors. Speed has never been an issue even though i use programs for everything. 

I have them hidden to turn the underbed lights on late night. Late night, they will turn lights on to a very dim level just enough so you can see. If you need more light, you can hit the switch which will turn them on to 50% if you need more but not full on (unless you double tap)

I also use my sensors to turn lights and stuff off in rooms/areas that are unoccupied. For example, if no motion is sensed on my patio for an hr and the tv or music is on, itll automatically shut everything down. This only happens at night as we could potentially be in the yard away from the sensor during the day. 

My zwave MS's have lux sensors built in. I use this to adjust lighting in occupied rooms vs using only sunset +/- to trigger stuff. On a cloudy or rainy day, those options do not work well which can leave you sitting in the dark or needing to physically turn on the lights (whether its remotely or by touch). By looking at the amount of light in the room, the lights will turn on by themselves. Sometimes it

I use the average of the square root of two CAO Wireless Tags lux output to control my gathering room lights on automatic. They each update only every 30 minutes so the lighting level corrections only average about every 15 minutes (time clock drifts). This lighting uses 4 Insteon controlled ceiling bulbs and 9 WiFi bulbs around the perimeter.

[MrBill]

6 minutes ago, larryllix said:

You must turn off the battery writes option. ISY turns it back on upon rebooting. UDI has just reported it has fixed this in the next release.

I'm aware, I've been in many of those threads and tracking that bug for a very long time.  I was always finding battery writes back on even without rebooting too.   I know the focus has been on Z-wave certification but I had about given up on that 2 year old bug ever getting fixed given the disfavor that Insteon/smarthome has fallen into.

[larryllix]

2 minutes ago, MrBill said:

I'm aware, I've been in many of those threads and tracking that bug for a very long time.  I was always finding battery writes back on even without rebooting too.   I know the focus has been on Z-wave certification but I had about given up on that 2 year old bug ever getting fixed given the disfavor that Insteon/smarthome has fallen into.

ISY needs to go back to the old scene modification. MSes never need to be modified for lighting changes, anyway. When the battery writes are blocked, the cache fills up with a dangerous waiting Insteon traffic jam, ready to pounce at the first opening, that will bog your Insteon down to a 2-3 minute response to events.

[lilyoyo1]

11 minutes ago, larryllix said:

I use the average of the square root of two CAO Wireless Tags lux output to control my gathering room lights on automatic. They each update only every 30 minutes so the lighting level corrections only average about every 15 minutes (time clock drifts). This lighting uses 4 Insteon controlled ceiling bulbs and 9 WiFi bulbs around the perimeter.

Mine adjust when the light falls below a certain point. it doesnt trigger right away but waits about 10 minutes as it could be a passing cloud that makes temporarily dark. The same for turning off. A temporary moment of "enough light" will not trigger it to turn off.

[PB11]

On 1/14/2021 at 7:55 PM, kclenden said:

So if you have enough devices, and use enough scenes, eventually you'll run out of links in the PLM table.

Is there a number for these links and how do I know if I've exceeded this number?

I'm seeing this error in my Summary tab.

 

[Bumbershoot]

31 minutes ago, PB11 said:

Is there a number for these links and how do I know if I've exceeded this number?

I'm seeing this error in my Summary tab.

 

I think the PLM table can maintain something on the order of 1000 links, though I'm not entirely certain.

These errors may not mean that you've exceeded the number of links.  Folks who've recently migrated to a recent firmware version who've used the "adjust scene" functionality in programs run into this as well. You can try to open one of the affected programs, inspect it and re-save it.

[larryllix]

On 1/15/2021 at 10:37 AM, lilyoyo1 said:

Mine adjust when the light falls below a certain point. it doesnt trigger right away but waits about 10 minutes as it could be a passing cloud that makes temporarily dark. The same for turning off. A temporary moment of "enough light" will not trigger it to turn off.

That would give me about 10 minutes more of unwanted darkness in the room. Ideally, I wanted instant updating for the analogue lighting levels in order to compensate. My thoughts are I would be able to compensate for a 5 minute cloud darkness in the room, or a rest of the day cloud/overcast.

In real life, I don't want my CAO wireless Tags to update more than 15-30 minutes to conserve battery life. A delay for my system would just add a delay to the 15-30 minutes already incurred. The difference is I am using a formula to calculate how much additional lighting is required to the outside levels coming into the windows, not just On or Off.

[lilyoyo1]

7 minutes ago, larryllix said:

That would give me about 10 minutes more of unwanted darkness in the room. Ideally, I wanted instant updating for the analogue lighting levels in order to compensate. My thoughts are I would be able to compensate for a 5 minute cloud darkness in the room, or a rest of the day cloud/overcast.

In real life, I don't want my CAO wireless Tags to update more than 15-30 minutes to conserve battery life. A delay for my system would just add a delay to the 15-30 minutes already incurred. The difference is I am using a formula to calculate how much additional lighting is required to the outside levels coming into the windows, not just On or Off.

It works for us, because I don't want the lights cycling on/off and there's no delay in reporting. If it happens to get too dark, the delay is overridden 

[kclenden]

4 hours ago, PB11 said:

Is there a number for these links and how do I know if I've exceeded this number?

The PLM has a 1000 link limit.  If I recall correctly, the non-Pro versions of the ISY limit nodes to something like 255, but I don't know if that includes links.  You can see how many links are currently being used in the PLM by going to Tools->Diagnostics->Show PLM Links Table, and then clicking the "Start" button.  You should run that a couple times as it can be interrupted by powerline activity.  Here's a link to a really old forum discussion on how to estimate the number of links a system will use:

 

 

[kclenden]

4 hours ago, PB11 said:

I'm seeing this error in my Summary tab.

 

As @Bumbershoot mentioned, that error often is a result of doing a firmware upgrade (especially from v4 to v5).  What happens is that some of the commands in the earlier version don't translate to the new version so you have to open the program and minimally save it, but sometimes you actually have to make a change in the program (even if just in a comment) before you save it.

Another thing that sometimes causes this error is a mismatch between the Firmware and UI versions.  You can go to Help->About to see version numbers.