Xathros

Yes! You can use a substitution variable in the email notification to reference the thermostats Status (temp). The would look like: $(sys.node.11 22 AA 1.ST) where 11 22 AA is the addrrss of the stat. That sounds to me like the setpoint. That should be whatever your program had set for a setpoint. Does that change when you press the up or down buttons on the stat? The stat operates independently of the ISY. No program need to execute when the stat calls for heat or is satisfied unless you are logging or taking some other actions based on that data. If the set point is not changing based on your programs, you may have a comm issue between the stat and the ISY. Can you read the current temp from the admin console and can you manually change the setpoint from the console and have those changes reflected at the display on the stat? No problem. Happy to help. -Xathros

Hi Jerry- Yes. Though it will take some effort to set it up. I do something similar with my Pellet stove and Furnace for tracking runtime on a daily and monthly basis. It involves monitoring the status of the Stat and counting minutes while the stat is calling for heat. Something like this: Variable definitions: $i.heat.today - runtime in minutes today $i.heat monthly - runtime in minutes this month. Program 1: If Status Thermostat - Main is Calling For Heat Then Repeat every 1 minute $i.heat.today =+1 $i.heat.monthly =+1 Else You would then add a program to run at 11:59pm to send you the daily stats and reset the $i.heat.today to 0 and the same for the first day of the month for the monthly. The ISY log does show timestamps when the stat calls for heat and becomes satisfied. If you need something more specific, you can use custom notifications to send emails of these events or to write to a custom log file on your ISY's web server. -Xathros

JSP0511- The ISY is not in direct control of the heat - the Thermostat is. If the ISY were to go offline for whatever reason, the stat would continue to maintain the heat at whatever setpoint you had last set. As long as you don't put the thermostat into Off or Cool mode then it will maintain the temp at the setpoint. You can certainly have the ISY notify you if the temp drops below a certain point (heat failure, out of fuel etc) with a fairly simple program and a custom notification. If Status Thermostat - Main < 60 Then Repeat every 30 minutes Notify Me Low Temp Alert Else Along the lines of your thinking, I have a pellet stove that I directly control with my ISY using an IOLinc to simulate a basic mechanical thermostat. I use my Venstar thermostat for temp detection and toggle the stove as needed. In the event of an ISY failure, I have the old mechanical stat in parallel with the IOLinc and set that at 55. This way if the temp drops below 55 the stove will run without the ISY telling it to. Assuming of course that there is still power. To date, this failsafe has nt been needed. Hope that helps. -Xathros

Hi chrsb- The url would be: https://myname.asuscomm.com:33433 If that doesn't seem to work, then test your forwarding using your outside IP address: http://whatismyip.com, https://:33433 If that workss, then try: nslookup myname.asuscomm.com using your command line of choice and make sure it resolves to the outside ip from above. If connecting to the IP directly doesnt work, then there is something wrong with your port forwarding. Did you forward 33433 -> 443 at the ISY IP or 33433 -> 33433? If the latter, did you change the ISY secure port to 33433? -Xathros

Wayne- I believe the ISY has a default 3Mb Log file max size. I'm assuming the error log follows that limit as well but don't know for sure. I usually clear my logs once a month or more frequently if i'm busy building net network resource rules. Aside from a longer delay when exporting the error log, I haven't noticed any downside to allowing the log to grow fairly large. -Xathros

Wayne- Do you use the custom notification system to write to any file(s) on the ISY webserver? Based on your original post and Michel's comments above, I suspect that entry hadn't been flushed yet (9+ hrs after it occurred) and couldn't be at the time you output the first log due to some other file activity. I also suspect that asking for the log twice in a row may have worked as you speculated. -Xathros

Very strange. Backlight level is a device feature not a scene feature. I don't see how this could be scene related. -Xathros

I'm not sure. I usually see more of a response to me net resource rules than what you posted leading me to think that you weren't seeing the whole response. Increasing the timeout should not have caused it to fail so something else may have changed as well. Verify Ip address, username/pass etc. -Xathros

Change the brightness to something like 50. Than after that has been applied, go change it back to 0. The ISY will not send changes if it believes they match the current values. -Xathros

Ferdies- Increase your timeout to 2000ms and see if you get more of a response. -Xathros

WayneW- I do know that the ISY schedules tasks on a priority basis with I believe, Insteon traffic being the highest. I don't know where in the priority list logging comes in but I think it is possible to delay logging and possibly network resources by keeping the ISY busy with Insteon tasks. It may also be possible to delay logging with IP network tasks as well. Michel- Can you comment on this. -Xathros

Is the ISY clock correct? -Xathros

In this case it's ok since the mvar is an integer (not state) the second program does no trigger from the first when set to 0. Instead, I have to call the second program from the first (Run If) -Xathros

Sounds and looks to me like you have a program like: If Control RL2-D is Switched Off Then Set Bathroom Scene Off Else -Xathros

ferdies- No. The If section is looking at $i.internetTestEnabled while the then section is setting $i.InternetTest. Two different variables. -Xathros

it's a very quick ad simple test. Not hard work for the ISY by any means. The enabled mvar is used to enable or disable the test program. The test is initiated by my startup program and then runs on its own from there. -Xathros

Tom- Anytime! Happy to help. It has to be the 2413S. The U will not work. -Xathros

Nice! I nominate this for inclusion in the variables section of the Wiki. -Xathros

Excellent. Thanks for posting back. You should likely add a delay to the nighttime setback as well. Not sure why that worked when the other didn't but would be safer to add the delay to both in my opinion. -Xathros

Hi Tom- Is the 26 still connected to a PLM? If you connect the ISY 26 to your LAN, Connect the ISY 26 to the PLM then plug the PLM into power, wait a few seconds for it to start up, you should be able to log into it at it's old address assuming you didn't factory reset the ISY 26 at all. Also, you want to make sure you are accessing using the correct admin console. Before you try to access the ISY 26, make sure you clear your Java cache. I'm not sure if the 26 worked the same as the 99 and 994 but if so, you should try and access the console at: http://192.168.1.12/admin If that works, make your backup then repeat the process for hooking up and connecting to the new 994 but using it's ip instead. -Xathros

Hi v101- Welcome to the forum and the world of ISY! Thanks for the intro. It sounds very much like my first experience with the ISY 5 years ago. -Xathros

It will help in situations where there is a lot of insteon traffic to prevent missed comms. With wireless devices sometimes having multiple message paths back to the PLM, I have seen odd behavior at times. Not sure this will fix it but I see no other reason that what you are doing would fail. -Xathros

Try adding a 4 second wait between the two set commands and see what happens. -Xathros

Hi davbow- When you select the scene name in the ISY, you are adjusting the scene settings that are used when the ISY is the controller - either activating from the admin console, dashboard, Mobilinc or an ISY program. -Xathros

Sounds like the email is being triggered by the leak sensor heartbeat signals. Post any programs that reference the leak detectors and I'm sure we can get to the bottom of this. -Xathros