apostolakisl

None of what you say has anything to do with the logic of your program. You are using time conditions to set a state variable. 100% of the time, the variable will match the true/false state of the program. Except on a power outage in which case your variable could be wrong whereas the program will be correct. The state-variable will be in the exact same state as the true/false status of the program. End of story. It is fully redundant. It is also a triggering event, the same as the state variable. It is a one-to-one copy. It would be no different than having 2 or 3 or 10 variables that are just copies of the fist one. I don't know how else to say this. All this stuff about what if the lights change or whatever is not setting the variable. That has nothing to do with it.

?? Seriously, that is your defense of your logic?

I was thinking, would there ever be a logical reason to use a Boolean state-variable. At first, I thought, what if you had multiple programs setting that state variable. But generally speaking, still no, because you could just list those programs true/false status in your "if" and connect them with an "or" or "and" statement. There might be some issues with triggering events since your target program would trigger when any of the listed programs changed states whereas the state-variable would only trigger your target program upon it changing, which under certain logical situations would not change when one of the programs that set it changes. But I can't come up with any actual use cases for this sort of logic.

Hands down, this is the best way to do it. It would only be better if it ran on polyglot. I run it on a 24/7 pc and it works perfectly, but it could be run on rpi, if you can find one as they seem to be in short supply. I use it to track temperature and humidity from Inteon thermostats as well as outside temp/humidity at my church. I use that data to figure out algorithms for running the hvac system. It saves the data as a csv file which open in excel or whatever spread sheet you want. You can set it up to follow whichever variables you want.

Being right or wrong isn't something you elect. Successfully defending your answer and refuting mine would make it right.

Variable is not best. There is NEVER a need for a Boolean logic state-variable. NEVER I tell you! 1) A state variable used in a Boolean context will simply mirror the state of the program that sets it. It is redundant at best. 2) It unnecessarily adds to the list of variables that you need to scroll though every time you write a program that uses variables, plus if you forget what it does, you will have to search your programs to find its use. The ISY AC and its dependence on drop downs and mouse clicks makes long lists of variables a PITA. 3) Using a variable will require extra steps to account for power failure. When ISY reboots, the program will init to the correct state all on its own. The variable will not and would require extra steps to ensure it is in the correct state. 4) Program state change is a trigger, same as a state variable. Should you instead prefer a non-trigger situation, then an integer variable would be a consideration, though you would likely be better off using enable/disable program logic. Again, there is never a need for a Boolean state variable.

It isn't about the bytes, it is about useless clutter. The variable is truly useless, it servers no purpose at all. You could add a useless variable or two to every single program using that logic. I recommend putting ISY on a UPS. This doesn't solve all problems, but I think it is better than having ISY reboot on a power outage. Using a variable will not help you here. Initing the variable just means the variable will be wrong if power goes out while the program is in one state and then power comes back on during the time it should be in the other state. You would want to use a "run at startup" on the program to have things be correct at startup, no need to init the variable. But as I said, I would skip the variable as it is useless clutter. The variable status precisely matches the true/false status of the program, it is totally redundant.

No. In the scenario you posted, program 2 would run at both on times. In the scenario I created, program 2 only runs once, the first time program 1 goes from false to true. Program status is a trigger like a status variable. It must change to be a trigger. So when it runs true the second time, it does not change state and thus does not trigger program 2. But with a "run program 2" in the "then" it will run program 2 twice. No different than if it were just one program.

Using a variable as above is ever so slightly more load on ISY than not using the variable, though meaningless so. There is no difference in Insteon traffic.

This works fine. But you have a completely useless variable. The following is the same function and basic construction without the variable. If From 6:00:00PM To 11:00:00PM (same day) Or From Sunset - 30 minutes To 11:00:00PM (same day) Then blank Else blank Program KitchenEvening If program above is true Then Set 'Kitchen RGBW + puck' On Else Set 'Kitchen RGBW + puck' Off Remember what I said, if you have a variable that only has two states, you usually don't need a variable.

Thank you, I see now. Might change instruction to say

I would recommend using the "notes" to write out in plain English how the programs work regardless of how you do it. Of course I like my method better, save yourself a variable. Anytime you need a Boolean variable (2 states), you can always use a program's status to store the two states. True or false, enabled or disabled.

Using @larryllixsuggestion won't help with this issue. To force it to run just once, the first time the conditions are met, you would need two programs. Program 1 If time is from 6 to 11pm Then turn scene on disable program 2 Else enable program 2 turn secne off Program 2 If time is from sunset to 11pm Then turn scene on disable program 1 Elase enable program 1 turn scene off

Running 5.4.3 and I don't see this. Looking under I have a "networking" tab which is the same as it has always been with the web server, network resources, and wake on LAN sub tabs. Using them as pass through switches could be useful if you want to put polisy in a location that has only a single ethernet connection and already has a use for it.

Networking bridging, but I wouldn't think you would want to have polisy be in charge of that. But in my world I do all of that using vlan's and poking holes in the firewalls where something needs access to multiple vlan's. And yes! Why not label the stinkin ports. I had unplugged my polisy for some reason a while back and was like, damn, which one was it again.

It appears they are network ethernet ports. On PG2 you can go into configuration and turn those ports on. At least it looks like you can, I haven't actually done it. But just playing with the settings and not saving them, each of the 3 ports has its own MAC address and can be configured with their own IP addresses. But I can't imagine a use case for multiple networks.

It is actually in the wiki. But seriously, how frustrating to right off the bat not even know where to plug in your ethernet! Back to my question, what is the ultimate purpose of having 3 network adapters (plus wifi)? Connect one end of the included Cat5e cable to Polisy’s Network Port and the other to your network. You must use the port that’s closest to the right most edge of Polisy when the front of Polisy is facing you (closest to the db-9 serial port). Note: the network must initially be DHCP auto enabled

Questions, Why 3 ethernet ports? It is a bit confusing right off since you don't know which one to use without trial and error or reading the instructions. I have not tried changing these settings, but it appears you can turn on multiple ethernet ports at the same time and get different IP addresses. And I guess you can turn on wifi at the same time as well for 4 simultaneous networks?

So what is the behavior you are looking for? Currently the program triggers 3 times. At 6pm, at 30 minutes before sunset (both true) and 11pm (false). Are you trying to only have one true trigger? If so, why? What is the behavior as written that you don't want? Having the program run true the second time each day simply sends a command to turn lights on that are already on . . . effectively doing nothing. The only thing that I can imagine is that you are sometimes manually turning the lights off in between the two on times and don't want it coming back on. And as Larry noted above, the from/to isn't needed for both times. You only need the 11pm off trigger in there once. You can just do if time is 6pm or time is from 30 minutes before sunset to 11pm. This no longer holds true if you have additional triggers, like an outside program that does a "run if" on this one.

found this on reddit. It is a v1 hub, so not that much help. Took a picture of my V2 hub. Lots of header pin locations to choose from.

Do you suppose you could just get one of these: https://www.ebay.com/itm/181006995656?hash=item2a24db90c8:g:4hEAAOSwcgNZD8mI And connect to the rx/tx pads on the hub? The hub actually has a really nice and powerful radio in it so it makes a nice access point.

Use repeat every 1 minute. If the pump changes status it will imediately switch from true to false or vice versa. It will start to run on its own first time pump chages status. Or click run at start up to trigger it at startup.

So, should I scalp all my spare plm's on ebay now?

I saw that, but I can't understand how that applies to that sentence. It sounded like he was saying the parts are no longer manufactured. Where ETL refers to data, not parts.

? sorry not hip to that abbreviation. EOL?