jwagner010

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.

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.

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.

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.

Thank you. Appreciate you taking a look.

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.

Thanks Bob, sent you a PM.

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?

Not sure it helps, but the HushJet is supported through the libraries here within HA: https://github.com/cmgrayb Not sure if that helps as they all seem to originate from the original libdyson

I now have a HushJet Purifier Compact HJ10: https://www.dyson.com/air-treatment/air-purifiers/hushjet/black-teal Tried all the various model numbers but no luck. Any future plans to support this model fan? Have to help with any testing. Thank You

@Javi I know this one is on the to do list. Any best guesses when we may see it in the wild? Is it something that will happen in 2026? As always your and UD's work is always appreciated. Thanks

For what it’s worth I periodically have issues with Alexa+ that pop and then resolve themselves. For example this happened last night, I have a light with spoken of ‘Dining room light’ and another device called ‘Living Room Shades’. Last night when I would say ‘Alexa turn off Dining Room Light’ instead of the dining room light going off the living room shade would go down. Checking / changing / refreshing the UD portal and everything else does nothing. It’s an Alexa+ issue, how do I come to that conclusion, when I say ‘Alexa turn off Dining Room Light’ to an old (cannot be upgraded to Alexa+) echo device the dining room light goes off, when I say ‘Alexa turn off Dining Room Light’ to one of my newer echos upgraded to Alexa+ the living room shade goes down. I think Alexa+ is Amazon’s version of AS (artificial stupidity) versus AI. Anyway this morning things are back and working as normal, just another glitch, there will be more with Amazon Alexa+ AS.

Hi, is the Roomba node server compatible with the Roomba 205 DustCompactor Combo Vac and also the Roomba Max 705 Vac?

I have iOS 18 and don’t see how to add faceid to open the app. Can you provide instructions?

Same on iOS, can lock edits, looking for a pin/Face ID to open the app given some of things that are controlled by the app.

Can we look to have a pin/faceID to open the UD Mobile app in the future as an option for those that want a greater level of control and security over the app?

Ok. Pity, but understand the rationale. Perhaps a GenAI powered ticket system and a GenAI powered forum can remove these costly tickets from the need for UD humans to respond to them. 😀

Is it possible to hide a controller on the home screen? I know it was possible in earlier versions, I have multiple controllers and would be helpful to be able to hide an entire controller from the homescreen.

Curious, the web server available through the admin console under the configuration and networking tab, (I have a POLISY), am I able to add php scripts that I can call remotely on the polisy web server?

Would be nice if you could select a different attribute for the advanced config than what is displayed in the tile. So you can show for example the temp in the tile but change the icon color if the hvac is actually cooling, heating or idle.

@JaviIf its not already on the list, would it be possible to have a selectable filter when looking at the All Devices and Scenes view, where you can select only On or only Off (or variations of that) devices and scenes to show? Would be handy to be able to see all Devices and Scenes that are on quickly for example. Similar to email I guess where you can just see your unread emails.

Back. Thanks UDI.

5/2/24 @ 9:20AM ET still unable to connect remotely via UDMobile. @Javi

@Michel Kohanim @Javi I hope everyone is well. Would it be possible to get an update and target date/time for when things may be restored for users affected by this OAuth error? Thanks for all the hard work and support.

@btreinders It only charges you after the 1,000 calls have been made at that rate. You can also put a.limit on your plan of 1000 calls and it will reject (not process the call therefore no bill you) should you go above the 1000 in case you accidentally configure things that way.