TJF1960

I did some renaming of the custom params between v1.0.1 and 1.0.2, did you upgrade from a previous version or did you install fresh the 1.0.2 version? -Tim

Sorry, not following. Can you Screenshot. I am not seeing double inputs in the config setup in PGx.

Awesome! Good to know. Thank you!

I had a lot of trouble with uploading the files to the beta store yesterday and again this morning. But everything should be good now. I just double checked and I see 43 plugins in the beta store, 2 of which are mine. You will want to delete both instances in pgx and reinstall fresh. If you do not see it in the beta store, hit refresh. Let me know if that works.

I have been testing it here on both my eISY's, wanted to make sure it was good to go before contacting you. So far its good for me too. There was a snafu with the zip folder when it was uploaded to UDI's servers, but all good now. Thanks for letting me know! -Tim

Odd, when I get home I will check to see what is going on and get back to you. -Tim

Hi @dbwarner5, please give 1.0.12 a go. -Tim

@dbwarner5, I will look over the NLS file and update it, I may not get it done until this weekend but I will try for sooner. I will update the store when complete.

Hi @Javi, thank you. Question, why might my UDM is not reporting the errors as well? I presume @dbwarner5 are on the same fw levels.

No, I don't think so. 1 of mine in both eISY's also do not have a Json file. I just resync'ed again, no errors. Do all of your temp data jive with the admin console or the webcontrol console? Is the heartbeat switching between -1 and 1 every shortPoll? Does the time/date update also every shortPoll? I quess it would be easier to have asked, is the plugin working fine in UDM, just with the errors?

I ran sync yesterday after updating all four plugins I have running on each eISY I have and didn't get one error. I am at work now but ran sync again, still no errors. I'm not saying there isn't anything wrong with the plugin, but I can't reproduce it here. Maybe @Javi can help?

@dbwarner5 version 1.0.11 is available. Please give it a try. Custom Port now persists reboots, starts and restarts.

For some strange reason, this time when stopping and restarting, the port did not persist thru restart. Looking into it. My apologies.

I just switched one of my instances on each eISY over to port 84. I set the first one, then the other, both instances took to the new port right away. I will let them run and monitor them for glitches or fails and report back. Very strange. -Tim

Hi @dbwarner5, Very strange. It looks like it took the port for a short time but then reverted back to 80. It is strange that the other instance of webcontrol is working fine. I remember you mentioned that you had problems with one of the plugins accepting the new port at first. Was it this plugin by chance? I wonder if something may have happened that was quirky during install. I would delete the plugin and reinstall. Once it is reinstalled try changing the ip, port, username and password (unless they are default user/pass) then pressing save to see if there might be any difference. -Tim

WebControl8 is for use with the CAI WebControl 8 I/O board. This plug in offers all 8 temperatures, 3 Analog Inputs, 8 digital inputs, 8 outputs, 1 Humidity, Freq., and Counter. The plug in also has a dedicated heartbeat along with the NodeServer Connected field. The Heartbeat switches from 1 to -1 with every successful poll. Polls are set by shortPoll in seconds and will only update values which have changed since the last poll. longPoll is also in seconds and will force a full update of all values. A query is also included and will force a longPoll when pressed. I have included a text field in PGx which will allow you to enter a JSON formed single line text to rename all or some of the nodes. This way you can rename "Temp1" to a friendly name such as "Outside." This way you can save the Json for future use. The alternative is to painstakingly change each node name in IoX. Although this plugin is in non-production, it has been working fine for me on both my test bed and my main eISY for weeks now. I am currently running 4 instances on 4 WebControl 8 boards with no issues. This plug in is being offered for free, but use at your own risk. I originally set out to see if I might be able to create a plugin, with the valuable help of many devs on this forum, @Michel Kohanim, @bpwwer, @Goose66, @Jimbo.Automates, and JR on discord (I am sorry I don't know your username here on the forum) I was able to succeed! Thank you all for your patience and help these last couple of months, if it weren't for you this would not be possible. -Tim

@EWhite, giving it some thought, I think you can simplify since you don't need the 5:30 wait. Try this at your own risk, I think this will work.

@Kentinada, I to have been using the Yolink system for almost a year now. They have been rock solid for me as well. So much so as I branched out to using their remote switches for some doors and the fridge and freezer doors, motion sensor as well as their temp sensors. All have been one of the best purchases I have made in a long time (with exception to my UDI products of course). They are very responsive, and quick to report in IoX thanks to the plugin. Yes, that link is that you attached is correct. -Tim

@EWhite, Please post your current programs. -Tim

@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