I have been using the ST-NuHeat Node Server flawlessly for years. I have the Node Server running on a POLISY which talks to my ISY994. After a reboot the ST-NuHeat Node Server doesn't seem to authenticate to the NuHeat API any more? I know the NuHeat API changed recently for the Signature Series Thermostats, not sure if that has something to do with it, would seem to be? I know my credentials are correct as I can log in via the NuHeat iOS App? @simplextech any ideas, I assume you can recreate the issue?

Edited August 31Aug 31 by jwagner010

@simplextech isn't around anymore and isn't maintaining his plugins. He passed them all over to me and I do my best to maintain them.

I don't have any way to reproduce this issue as I don't have the hardware or an account. But if you can switch the logging level to debug, restart the plugin, download the log and send it to me (a PM is fine), I'll take a look at it.

Thanks Bob, sent you a PM.

looks like there is a now authentication needed

Changelog - OpenAPI

I have the same issue BTW

The node server is no longer supported by the original developer and @bpwwer had agreed to maintain it, but appears this would be more of a re-write, a lot more than maintaining the node server. So I suspect we are out of luck unless there is some else that has the time and knowledge to do a re-write of the node server.

i have contacted nuheat to see if I can get the credential to access to thermostat. If i get it I'll take a look how big an effort it will be to rewrite it

Thank you. Appreciate you taking a look.

@Panda88 If you figure anything out, let me know. The plugin interface does have the ability to do oauth authentication which is what the new API needs, I believe.

will do - looks like some of the API calls also changed, but likely minor

Bob,

I seem to have lost the email you sent me - can you send it again - I am getting the ids needed from Nuheat

15 hours ago, Panda88 said:

Bob,

I seem to have lost the email you sent me - can you send it again - I am getting the ids needed from Nuheat

Umm, I seem to have lost the memory of sending you an email. I'm a bit confused.

It was regarding using the intern Oauth service - I think I got it

I did finally receive the credentials for the Nuheat - I'll start looking at it soon

Christian

if you go to the polyinterface github, there are instructions in the Oauth2.md file on how to add oauth2 support into a plugin.

https://github.com/UniversalDevicesInc/udi_python_interface.git

except that the Nuheat plugin is written in javascript and I don't think the javascript interface got any of the updates for oauth2. It does have some basic support, but it's not documented.

I think @simplextech was really the only developer that created plugins using javascript so that interface isn't nearly as well supported as the python interface. If the plugin needs a re-write anyway, maybe it makes sense to switch to python.

Do you have a Nuheat thermostat? Or were you able to get credentials without one?

I do have a nuheat - I think there is a python version under siimplextech github - I forked that to start from

GitHub - simplextech/udi-poly-nuheat: NuHeat Signature Thermostat Polyglot Nodeserver · GitHub

I was going to ask an AI to perform the changes and see where it gets me :-) - I believe it is doable without too much effort - no need to reinvent the thing from scratch

Not sure how to release this (assuming I get it to work) - I assume you have the ability to update the PG3x store to point to a new version - or can it be handed over (if I am to support going forward)

Edited Thursday at 08:49 PM5 days by Panda88

He has 3 different Nuheat plugin repositories. The python one is at least 2 years older than the two javascript based versions. The version I've been maintaining is based on the private version and I've made updates to it since then.

Oh, looking at the python version more closely, that looks like a PG2 node server, not PG3.

Yes, I can update the store entry/db or if you want to take it over, UDI can switch the developer field in the database to you.

Thanks - I'll see what the AI agent can do first :-)

I am through the authentication process - moving the python code base I have - to PG3x

Can somebody remind me the current functionality of the node - I am using a very old version as reference - I can no-longer run the node - and I do not remember what the latest functionality is

This one is reporting of power consumption per day/week/year - Anybody using this?

Edited Saturday at 01:06 AM4 days by Panda88

For me I only used the node server for the basics, current temp, heat set point and mode. It would be nice to have more, but in the past I have just used the NuHeat app to look at energy consumption history.

I added a new node server to test in the beta (non-production) store - can you give it a try

it is called NuHeat_v2

You will need to redo the programs as I may have changed some values - for sure the commands are changed

Your should only need to login to your nuheat account once requested (after pressing Authenticate during start up) and then accept the different scopes. I believe this is sufficient, but cannot test if the credentials I got only cover my account of if all users can use it (I hope this is the case)

Once it is working - I'll do a full release. I am working with UDI to see if they can move licenses from the old to the new plugin

Edited yesterday at 01:05 AM1 day by Panda88

I still have an ISY 994i and my Node Servers run on a POLISY that connects to the ISY994i. Looking at PG3 I see the nodes and their values and that seems to be working fine, but the nodes in the ISY 994i are empty, ie it creates the Controller Node and the Main Node for the thermostat in the ISY994i but they have no values. Will pull the log when I get home later tonight and PM you.

@bpwwer Do you know what could be causing this? Is the PG3x/udi_interface version too new - I just made the version I currently use the requirement

@jwagner010 Just to be 100% sure - you were able to press authenticate and then log into your account and then you see data in the Polisy with same values as the app - can you also change temps etc? If that is the case, we just need to understand why you do nto see the same in the ISY994. BTW - is there any special reason for not moving to run on the polisy?

Edited yesterday at 03:41 PM1 day by Panda88

Yes was able to authenticate. Just sent you a PM with log and screenshots. Cannot change temp as there is no temp setting in the node.

Re: Moving to POLISY, I have a large Z-wave base (already installed on ISY994i) and do plan to move to EISY eventually, but I have been putting it off as I have a very large amount of programs also and I know when I upgrade it will take me a few days (week) to get it all functioning properly and I just dont have the time, so looking to migrate (hopefully) at the end of 2027.

Edited yesterday at 04:44 PM1 day by jwagner010

@jwagner010 Are you running PG3 or PG3x on the Polisy? I know that none of the changes being made for eisy-ui are being tested on PG3. I'm also pretty sure that nothing is being tested with an ISY994i and it's firmware version. They aren't intentionally trying to break that setup but it could happen.

My current plug-in development environment is still PG3 based so I can test on that if needed.

POLISY: PG3x Version 3.4.18 (front end version: 3.4.18)

ISY 994i: IOX 5.3.4

PS. all other Node Servers work fine and the nodes show correctly in the Admin Console

PPS. When I change the Heat Seat Point on the thermostat either manually at the thermostat or via the NuHeat app the setpoint value in the PG3x Node server changes. It just doesn't show in the admin console, the two main nodes show in the Admin console but each of them is empty.

Edited 23 hours ago23 hr by jwagner010

You can set the temp using perment hold (I guess I should rename it to permanet set) - but it looks like you do nto see that in UDmobile

I am using dynamic parameters in this node, and I wonder if it could be caused by that - it does require a newer version of the udi_interface