Nuheat Devices not recognized due to change in application

Nuheat changed their application and the old Nuheat Signature app has been disabled along with the mynuheat website. The new website is at IdentityServer4. I don’t know if they’ve updated their API, which is at https://api.mynuheat.com/

Has anyone been able to get this working again?

There is a button in the docs link you posted above to look at issues for this integration.
I suggest clicking that and seeing if this has been reported and add a thumbs up if it has, add the issue if it hasn’t.

Yes, facing the same issue. Emailed the manufacturer, haven’t heard back.

I came across this Homeseer thread which includes an update from Nuheat in their newsletter: https://forums.homeseer.com/forum/hs4-products/hs4-plugins/lighting-primary-technology-plug-ins-aa/mcsmqtt-michael-mcsharry-aa/1741284-problems-with-nuheat/page6#post1755862

TLDR - they planned a week long migration to move older Signature thermostats into a single 'Conductor ’ app along their newly released Nuheat Conductor thermostat.

During the week on July 6th, 2026 all Signature thermostats will migrate onto the Conductor server architecture.

Timing and support:
The migration will start today and will be finalized on Tuesday (7th of July).
There can be some hiccups during these 2 days, but in principle, once the migration is finished, all thermostats will be back online.

They also included this blurb about their 3rd party / API integration support

What about the connectivity features and the 3 rd party API?

  • Like the thermostats, all 3rd party API are migrating at the same time as the thermostats.
  • It is possible that some of the integrations will have some issues in the first 1 or 2 days, but eventually Wednesday, all issues should be resolved

It’s now Thursday EOD in the US/Canada and even though the new Mobile App started working correctly and shows all migrated thermostats correctly as of Wednesday (during migration, random thermostats would drop in and out of the new app…) www.mynuheat.com doesn’t resolve… so I wonder if the 3rd party / API migration is actually done, and if these 3rd party integrations are expected to make any changes to accommodate, or if it should be invisible.

I’ve never heard a service with thousands/tens of thousands/hundreds of thousands of devices/users taking a whole week of going offline and breaking existing user functionality for so many days as being acceptable. Imagine if Google Nest did this to migrate… Then again, looks like NuHeat as a company has been thrown around amidst a bunch of acquisitions over the years, first to Nvent, then to Chemelex (their current owners)…

Nuheat also boasts Crestron/Control4/… integrations, and I can’t imagine homes/owners with those systems being OK with such a long outage, and having to call up their Crestron/Control4 integration company and pay hundreds to update…

I tried to file an issue but didn’t have Github permissions. In any case looks like someone already filed NuHeat integration now broken after Chemelex LLC migrated to new phone app (NUHEAT Conductor) with new API · Issue #175923 · home-assistant/core · GitHub and it is actively being investigated. They think it’ll be major changes which makes me double down on what on earth Nuheat is thinking breaking everyone including those on Control4/Crestron/…