DrLumen

One thing to keep in mind is that humming is not always a property of the bulb. Zero crossing dimmers that do not have chokes will cause bulbs to hum. Back when I was doing stage lighting I found that using cheap dimmers would make the high wattage bulbs not just hum but SING.

Hell, a few years back, the little C7 night lights were drawing 7 watts. Now LED's can light a room with 7 watts.

I got the cheap generic (probably chinese) LED bulbs and have no real issues with them. They don't smoothly dim from about 5% to off or from on but no flickers or hum that I have noticed.

Just for a +1, the total fan run time would be better for determining filter changes. All the cloud stuff bothers me too. I have a similar issue with my solar inverter data. It is all stored in the cloud. While it does prevent needing to store all the data locally (which I still do), one never knows when that cloud may evaporate due to company bankruptcies or mergers or ...

Cool. That is from the cloud?

I haven't found any tracking info that is exposed or documented; yet. It has various filter change reminders that you can set for x run time days or months so it has to be tracking run time at some level. It also has what they call an automatic recovery to anticipate run times based on temperature deltas. So, they have to be calculating some type of temp rise/drop coefficients but again nothing documented other than they have it. There are registers that they call ISU's that range from 120 to 1425 but only document about 60. I have tired querying others and get values back but no way to know what they represent. As I just got it I'm working on getting it set up and integrated and have not had time to start hacking or looking into some undocumented stuff yet. It supports 3H/2C. I'm using it for a heat pump system so based on what options are selected the trees change as you drill down into the settings. It should be able to handle 2 stage gas (fossil) heat but I can't promise it. Here is a link to the owners manual for the wifi version. https://s3.amazonaws.com/s3.supplyhouse.com/product_files/Honeywell-TH6320WF2003-Install-Instructions.pdf

I recently replaced mine with a Honeywell TH6320ZW2003/U. It is local and ISY sees some of the common settings in the admin console. It also has a web phone app. I don't use it so I cant comment there. It allows setting the low and high set points but they are still limited to 50/90 at min/max. Still trying to get the hang of using it from Alexa. So far I don't like that part but maybe after I get the hang of it. I really like the backlight setting (from a config call). The backlight can be off during the day and at levels 1-5 at night. They have them as dumb, ZWave (mine) Wifi and Lyric. Not sure about Zigbee.

Next week is the use of arrays and pointers. Oops, not in ISY - nevermind.

If it works for you without variables and you don't ever see that the conditions or actions will be 'variable' then what you have is best. No need to over complicate things. FYI, you are already using variables. The descriptions you are making for your motion sensors and switches are technically variables. They change to on/off (Boolean true/false or 1/0). Can hold changing integer values like levels. And in some cases hold floating point values, perhaps like temperature. The only real difference is you can change the values for the variables you create instead of them being tied to the status of a device. You don't have to send them to a device (ie levels) to change them.

Maybe if you were exposed to different ways of using variables. ISY is very limited as it tries to make it simple and idiot proof so they have it locked down. In a way it keeps it safer but sometimes causes many more steps than are necessary in other languages. In the hopes this will make more sense. Other programming languages have some form of For loops (among many other things). they are like this (in basic) total=0 'reminder that the next line is the beginning of the loop For count=1 to 5 total=total+count Next count 'end of loop total will equal 15 This will go from For to Next 5 times. At each time through the loop (iteration) it adds the current count value to the total so the first time the count will be 1 and the total will be 1. 2nd time through the loop, count is 2 and the total is now 3 (1+2). 3rd time through and the count is 3 and the total is now 6 (1+2+3). 4th time the count is 4 and the total is 10. 5th time the count is 5 and the total is 15. Note that the total was set to 0 initially but could be any value. If total=10 at the start, at the end of the 5 cycles the total would be 25. Not sure if this helps or makes it more confusing... PS: Found a bug

It depends on what you are wanting it to do. Yes the last line will set the level back to the whatever value it found on the right side of the = in line 3. If all you want is to return it to whatever it was @ line 3 then the next to last line is not needed. But, personally, I flash the certain lights for various things throughout the day so I'm not sure if the next to last line was intentional. Line 4 is kinda questionable as well but maybe 'ON' will be at different levels. If it is on, why do you want to turn it on again in line 4? No damage, just overkill.

Ok. If it was on @ line 3 then it will return to that with the last line. In this instance, and that is the action you want, then the next to last line is redundant as it is immediately countermanded to whatever is stored in the variable. Unless you want it to flash off then back on?

Depends on the initial value of $lamp.level1% from the 3rd line (1st of then). It could turn it back on if it was not 0%.

Back on point... I don't know of a way to comment variables other than in the programs. I just try to create variable names that are fairly obvious. Then, in 6 months I wonder what the hell they mean,

Variables allow some flexibility in your programs. For example, say you have 4 bath exhaust fans that you want to run for 10 minutes whenever the bath light is turned on. You could write 4 separate programs that state something like if light is switched on set bath exhaust timer for 10 minutes. If you want to change that 10 minutes to say 20 you would have to go in and change each of the 4 programs to 20. Or, you can define a variable, say, as 10 and replace the hard coded 10's in your 4 bath exhaust fan programs to the variable name. If you want to change it to 20 later you would only need to change that time variable to 20 and it would automatically be replaced in your programs wherever is it used. You could also change that time variable by another program if you wanted and it would be in effect for your bath fan timers.