TJF1960

@bconen , Sorry, not to butt in but, what is your IoX and PGx version?

@EWhite, in thinking about it further, if the fan was turned on and you, for whatever reason, rebooted IoX, the variable after IoX came back up would be at 0, the fan could run forever. Simply mark program 3 to run at startup. That way once IoX reboots the program will run else if the variable is 0 and turn the fan off.

@gregkinney, I wish I could trade knowledge with you, I have been banging my head against a brick wall trying to hack some python code together for a node server, lol. @EWhite, my brain is a bit foggy as well, its been a long week but let me give it a go. So, in looking over your programs, I think I understand what you want. It looks to me like if the temp is within range you want the fan to turn on until the temp is out of range. If its too humid, you want the fan to turn on for 5:30 then back off. I kept your same programs, just changed the logic a little bit. The first program sets the var to 2 which turns on program 3 to turn the fan on and at the same time turns on program 4 timing it, at the end of 5:30 the fan will turn off. The second program, when temp is in range, will turn on program 3 only, once program 2 turns false, the fans will turn off. I may have missed something so try at your own risk, but in my hazy state tonight from the long week, I think it should do what you want. -Tim

@gregkinney, I am not sure if when you posted the programs, if something happened and it got corrupted or something. Having a wait with nothing after it does nothing. Besides that, anytime you have a wait, it will stop and start over anytime the program reevaluates. Like if the temp or humidity values change, even by a decimal point, the program will reevaluate, the fan may never turn off, or on, depending. That is the beauty of using a simple state variable. A program can set a variable to 1 multiple times but a program monitoring the variable will run when the variable changes. @EWhite, did you figure out your program or could you use a little help. If you need help, post them again, including any changes you made. -Tim

@gregkinney, respectfully, he will run into a situation where the program will execute the Then/Else with every miniscule change in either temp or humidity. Personally, I do the same thing the OP is doing with variables. Yes, each program changing a variable will run Then/Else with every change in temp. and humid. but its loading effect on the IoX is small and at least its not flooding the powerlines with constant on/off commands (if he is controlling an Insteon switch or whatever). Plus, it has the added benefit of being able to add some hysteresis to the mix. @EWhite, can you post your programs so that we can see what is going on? Also, so I am clear, you want the fan to run if either the temp or humidity is above your threshold, otherwise if both are below the threshold, turn the fan off? And lastly, what is not very reliable, or what are you seeing during the course of operation that is not desirable? -Tim

I have a Honeywell t-stat that is working fine with this plugin. I am replacing it with a new T9. When I log into udi-honeywellhome-auth.azurewebsites.net I get an error message "code": 400, "message": "The redirect URL provided does not match the redirect URL registered for the app." I am not sure who is maintaining this plugin any longer, any help would be appreciated. Thanks! Tim *** Solution ****** Found the error of my ways. If you have an existing account already set up, and it has been a year or more since you set it up, you may be using the OLD Callback Url. If you are trying to replace a Honeywell Tstat, you may need to change/update the "call back url" Open https://developer.honeywell.com Login as normal. Goto "My Apps" Select your app, in my case it was called ISY Nodeserver Hit the pencil edit button. Change the Callback Url from the old one to the new one: https://udi-honeywellhome-auth.azurewebsites.net/auth Once that is corrected you can proceed to add the new Tstat. -Tim

Integer variables will not, by themselves, initiate a change in condition. You need to add something to the If section that will trigger a program evaluation. Like: If $outsideHighTemp > $fanOnTemp and it is 10:00 AM Then Allow the programs in this folder to run.

Awesome! Thank you so much @gzahar! Are these published somewhere that I couldn't find or did you figure it all out? Thank you again! -tim

Hi @Goose66, I am wanting to add name substitutions for the various panel status values for notifications but I have not been able to locate what the various node definitions map to in the admin console. For instance, GVO sends its value to what slot in the admin console on the Alarm Panel page? I have figured out that ST maps to System Alarm State but I could use all the rest. Any help would be appreciated. Thank you, Tim

Hi @TriLife and @sjenkins, You nailed it! Thank you both so much! -Tim

Hi @TriLife, Thank you, that did fix the AC ns pages for each device and I can confirm that the status changes however that did not fix being able to select the status of a switch in programs. The only sonoff status that appears in program condition dropdown is the ns itself. Then it must have been an earlier rev than .35, I am sorry, I have no idea. I generally stay up on updates as they roll out. All I do know for sure is that last week when I updated to .37 is when the status in programs disappeared. Thank you very much again for your help. -Tim

Hello @Michel Kohanim, The youtube node servers subscription is ending tomorrow. When I try to purchase the portal responds with no options to purchase. Thanks! -Tim

Hi @TriLife, Well, shoot, I tried installing V35 again (it does say v40 in the store) but it is not loading IOX properly. this is all I get. The status area is squished down so you cant see the status window and the three buttons on the bottom are missing. Nothing I tried work populate IOX properly. I wonder if its just me or it is a bug?

Hello @sjenkins, Question, is the MQTT in the Non-Production location a revision before the latest changes. I rely on the status of the swtiches for a number of programs and thought I might switch over to non-production in the mean time until you have time to fix. Thanks! -Tim

Hi @sjenkins, Switch status not showing up in dropdown programs is new as of .37 Many of my programs use Sonoff status in order to work and control things. -Tim

Hello @TriLife, I agree with you, version B, back-rev on production. edit: I did try non-prodction but the AC page for all of the devices didn't load all the way, tried numerous closings and openings and reboots. I meant to take a snapshot but forgot. Attached is after reverting back to production. Everything in the red circles was all squished down and the three buttons on the bottom were not visible. Thank you for working on this before your big trip, its the last thing you wanted to do I am sure what with getting ready. Safe journeys! -Tim

I am no expert, this was the first time using explorer so use at your own risk. It worked for me but I may just have been lucky. I deleted everything under "tele" and "tasmota" and 'stat" if I remember correctly. I then installed the ns and configured and it worked. However there is another problem that I found before doing this. In the condition of programs the switches show up under Control but not Status. So you cannot monitor status of a switch in program. Now I don't know if it is just me or if everyone will is affected. This problem presented after upgrading to .37 and unfortunately didn't change after deleting the files in gen.mosquitto. Maybe you can confirm the loss of status in program conditions. -Tim

Hello @sjenkins and @TriLife, Success! I deleted each switch, then deleted the ns. Opened MQTT Explorer, deleted all files I could. Reinstalled ns and configured. All switch status now reports in AC. You guys ROCK! Thank you so much! -Tim

Hello @sjenkins, I was having the IOX status issue as well, in another thread: Just sent you a pm with log. Thank you! -Tim

@maxnorth, thanks for your help earlier. But I didn't get anywhere either, lol. Say, can you tell me how to down grade to v35? I have never done it before. Thanks! -Tim

Thank you. The outcome is the same. I deleted the entire MQTT node servicer. Reinstalled and pasted the devlist back in and restarted. I noticed that the switch that works provides much more detail in the log than the switch that doesn't. -Tim

Thank you, unfortunately no change. Also I forgot to mention that in programs, none of the sonoff switches are shown as available for the "If" section. They all show up in the "Then" section. [ {"id": "sonoff130", "type": "switch", "status_topic": "stat/sonoff130/POWER", "cmd_topic": "cmnd/sonoff130/POWER"}, {"id": "sonoff131", "type": "switch", "status_topic": "stat/sonoff131/POWER", "cmd_topic": "cmnd/sonoff131/POWER"}, {"id": "sonoff132", "type": "switch", "status_topic": "stat/sonoff132/POWER", "cmd_topic": "cmnd/sonoff132/POWER"}, {"id": "sonoff133", "type": "switch", "status_topic": "stat/sonoff133/POWER", "cmd_topic": "cmnd/sonoff133/POWER"}, {"id": "sonoff134", "type": "switch", "status_topic": "stat/sonoff134/POWER", "cmd_topic": "cmnd/sonoff134/POWER"}, {"id": "sonoff135", "type": "switch", "status_topic": "stat/sonoff135/POWER", "cmd_topic": "cmnd/sonoff135/POWER"}, {"id": "sonoff136", "type": "switch", "status_topic": "stat/sonoff136/POWER", "cmd_topic": "cmnd/sonoff136/POWER"}, {"id": "sonoff137", "type": "switch", "status_topic": "stat/sonoff137/POWER", "cmd_topic": "cmnd/sonoff137/POWER"}, {"id": "sonoff138", "type": "switch", "status_topic": "stat/sonoff138/POWER", "cmd_topic": "cmnd/sonoff138/POWER"}, {"id": "sonoff139", "type": "switch", "status_topic": "stat/sonoff139/POWER", "cmd_topic": "cmnd/sonoff139/POWER"} ] -Tim

I Am running: eISY Iox 3.8.0 PG3 3.2.22 with same frontend reported MQTT 0.0.37 I am using all sonoff switches and this has been working fine for 3 or 4 years, pretty much from the start. These are my settings in PG3 MQTT: shortPoll 15 longPoll 60 mqtt_server localhost mqtt_port 1884 mqtt_user mqttuser mqtt_password admin I use devlist which is: What happens is on some devices if I turn on or off the device from the AC, the device will respond but the AC does not update the new status, whether on or off. But the admin console status updates for a few devices. Also, the status value in PG3 node page does not change either. I am not sure which logs you may need. Hopefully it is a config error on my part. Any help would be appreciated. Thanks, Tim

Installation was straightforward and easy. After about 5 minutes or so the playlist from YouTube was available for streaming. Very cool! I am enjoying it. Thank you @Michel Kohanim -Tim

It would be great if a notification was sent from PG3 to UDI mobile when one of the installed plugins had an update available. Similar notification as when one of the plugins fail or is restarted. Thank you for such a great system! -Tim