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 22 hours ago22 hr 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 :-)