jwagner010

Here is what I see when looking in the ISY under Node Servers -> Configuration -> slot#: I don't see anything change when the PG3 log indicates an "ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10" and the says its installing the node servers again into the ISY 00:21:b9:02:50:a1 = ISY 994i 00:0d:b9:52:c8:10 = POLISY (PG3) 192.168.0.26 = IP of POLISY I have no idea what to do here?

This morning my infloor heating was off, so I checked my ST-NuHeat NS and sure enough its says it has stopped again. My NuHeat account is fine, I can control my thermostat from my phone app or the NuHeat portal. A few strange things (probably more things I don't understand) when looking at the logs: The PG3 Log shows every 5 mins a 'configuration update required', see below. a1 is the ISY and 10 is the POLISY. It then shows a corresponding install of my node servers into the ISY. I run an ISY994i and a POLISY that is just running the Node servers, nothing strange about my setup. 1/27/2023, 05:27:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:27:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:27:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:27:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:27:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:27:46 [pg3] info: [00:21:b9:02:50:a1_9] 'OpenWeatherMap' installed into ISY successfully... 1/27/2023, 05:27:46 [pg3] info: [00:21:b9:02:50:a1_3] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:27:46 [pg3] info: [00:21:b9:02:50:a1_4] 'ST-Nuheat' installed into ISY successfully... 1/27/2023, 05:27:46 [pg3] info: [00:21:b9:02:50:a1_1] 'ST-Sonos' installed into ISY successfully... 1/27/2023, 05:27:46 [pg3] info: [00:21:b9:02:50:a1_2] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:32:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:32:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:32:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:32:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:32:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:32:46 [pg3] info: [00:21:b9:02:50:a1_9] 'OpenWeatherMap' installed into ISY successfully... 1/27/2023, 05:32:46 [pg3] info: [00:21:b9:02:50:a1_3] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:32:46 [pg3] info: [00:21:b9:02:50:a1_4] 'ST-Nuheat' installed into ISY successfully... 1/27/2023, 05:32:46 [pg3] info: [00:21:b9:02:50:a1_1] 'ST-Sonos' installed into ISY successfully... 1/27/2023, 05:32:46 [pg3] info: [00:21:b9:02:50:a1_2] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:37:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:37:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:37:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:37:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:37:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:37:46 [pg3] info: [00:21:b9:02:50:a1_9] 'OpenWeatherMap' installed into ISY successfully... 1/27/2023, 05:37:46 [pg3] info: [00:21:b9:02:50:a1_3] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:37:47 [pg3] info: [00:21:b9:02:50:a1_4] 'ST-Nuheat' installed into ISY successfully... 1/27/2023, 05:37:47 [pg3] info: [00:21:b9:02:50:a1_1] 'ST-Sonos' installed into ISY successfully... 1/27/2023, 05:37:47 [pg3] info: [00:21:b9:02:50:a1_2] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:42:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:42:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:42:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:42:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:42:45 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:42:46 [pg3] info: [00:21:b9:02:50:a1_9] 'OpenWeatherMap' installed into ISY successfully... 1/27/2023, 05:42:46 [pg3] info: [00:21:b9:02:50:a1_3] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:42:46 [pg3] info: [00:21:b9:02:50:a1_4] 'ST-Nuheat' installed into ISY successfully... 1/27/2023, 05:42:46 [pg3] info: [00:21:b9:02:50:a1_1] 'ST-Sonos' installed into ISY successfully... 1/27/2023, 05:42:46 [pg3] info: [00:21:b9:02:50:a1_2] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:44:58 [pg3] info: [00:21:b9:02:50:a1(4)] ISY HTTP Inbound: Received CLISPH for node: 1547108 1/27/2023, 05:45:01 [pg3] info: [00:21:b9:02:50:a1(4)] ISY HTTP Inbound: Received query n004_1547108 1/27/2023, 05:45:01 [pg3] info: [00:21:b9:02:50:a1(4)] ISY HTTP Inbound request ID: 2900 1/27/2023, 05:47:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:47:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:47:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:47:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:47:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:47:46 [pg3] info: [00:21:b9:02:50:a1_9] 'OpenWeatherMap' installed into ISY successfully... 1/27/2023, 05:47:46 [pg3] info: [00:21:b9:02:50:a1_3] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:47:46 [pg3] info: [00:21:b9:02:50:a1_4] 'ST-Nuheat' installed into ISY successfully... 1/27/2023, 05:47:46 [pg3] info: [00:21:b9:02:50:a1_1] 'ST-Sonos' installed into ISY successfully... 1/27/2023, 05:47:46 [pg3] info: [00:21:b9:02:50:a1_2] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:52:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:52:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:52:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:52:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:52:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:52:46 [pg3] info: [00:21:b9:02:50:a1_9] 'OpenWeatherMap' installed into ISY successfully... 1/27/2023, 05:52:46 [pg3] info: [00:21:b9:02:50:a1_3] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:52:46 [pg3] info: [00:21:b9:02:50:a1_4] 'ST-Nuheat' installed into ISY successfully... 1/27/2023, 05:52:46 [pg3] info: [00:21:b9:02:50:a1_1] 'ST-Sonos' installed into ISY successfully... 1/27/2023, 05:52:46 [pg3] info: [00:21:b9:02:50:a1_2] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:57:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:57:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:57:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:57:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:57:46 [pg3] info: ISY node server user configuration update required 00:21:b9:02:50:a1 vs 00:0d:b9:52:c8:10 1/27/2023, 05:57:46 [pg3] info: [00:21:b9:02:50:a1_9] 'OpenWeatherMap' installed into ISY successfully... 1/27/2023, 05:57:46 [pg3] info: [00:21:b9:02:50:a1_3] 'DysonPureCool' installed into ISY successfully... 1/27/2023, 05:57:46 [pg3] info: [00:21:b9:02:50:a1_4] 'ST-Nuheat' installed into ISY successfully... 1/27/2023, 05:57:46 [pg3] info: [00:21:b9:02:50:a1_1] 'ST-Sonos' installed into ISY successfully... 1/27/2023, 05:57:46 [pg3] info: [00:21:b9:02:50:a1_2] 'DysonPureCool' installed into ISY successfully... The ST-NuHeat Log shows limited information but that it is shutting itself down, see below 2023-01-27 03:00:20 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:50:a1_4, processing 2023-01-27 03:00:20 debug: POLY: Log file set to: logs/debug-2023-01-27.log 2023-01-27 03:00:20 debug: NS: Message Received: { query: { address: 'controller' } } 2023-01-27 03:00:20 warn: POLY: Message query ignored: Shutting down Node Server 2023-01-27 03:00:21 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:50:a1_4, processing 2023-01-27 03:00:21 debug: NS: Message Received: { query: { address: '1547108' } } 2023-01-27 03:00:21 warn: POLY: Message query ignored: Shutting down Node Server 2023-01-27 05:44:58 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:50:a1_4, processing 2023-01-27 05:44:58 debug: NS: Message Received: { command: { address: '1547108', cmd: 'CLISPH', value: '78', uom: '17', query: {} } } 2023-01-27 05:44:58 warn: POLY: Message command ignored: Shutting down Node Server 2023-01-27 05:45:01 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:50:a1_4, processing 2023-01-27 05:45:01 debug: NS: Message Received: { query: { address: '1547108' } } 2023-01-27 05:45:01 warn: POLY: Message query ignored: Shutting down Node Server ---------------------------------------------------------- I rebooted the POLISY and the NuHeat Node Server restarted and stayed running on Tuesday per my other forum post and I thought it had been fixed, but today (3 days later) the Noder server has stopped itself again? I again rebooted POLISY and the NuHeat Node Server is running again but not sure for how long? Next time the NuHeat Node Server stops are there other things I can do besides a POLISY reboot to get it fixed properly or get information for other people smarter than myself to figure out what is going on? @bpwwer @simplextech

Just to close this out, multiple reboots and restarts didn't help. So I purposely entered my password wrong in the app multiple times to lock my account out, which generated an email notice that my account was locked. I thought the email would then make me follow a reset procedure I could follow online, the email said to logon to my account to reset my password, pretty useless when I am locked out??????? But good news is there was a support email and phone number in the email that I was able to contact and they were then able to unlock my account. Once they unlocked my account the NS started working again. Not sure why my account became non response/locked on their end before I locked it (I have not needed to enter my account password for over a year) and I never got any emails beyond the one I purposely triggered that someone had tried and locked the account, but before then I couldn't log on from POLISY, APP or Web, I guess its just one of those things and my account became locked on NuHeats end. Once the NuHeat account was unlocked I rebooted the POLISY and all seems to be working now.

So some background, I have 1 NuHeat thermostat that has been running flawless on the node server for a couple of years. I had to restart my POLISY today and the node server will not restart, says its stopped and logs give me the following: The ST-NuHeat PG3 Node server log shows: 2023-01-21 05:50:42 info: NS: Starting Node Server 2023-01-21 05:50:42 info: POLY: Interface starting 2023-01-21 05:50:42 info: POLY: Getting config from environment 2023-01-21 05:50:43 error: POLY: MQTT Error: Connection refused: Identifier rejected The POLISY Log shows: 1/21/2023, 05:50:37 [pg3] info: [ST-Nuheat(4)]: Restarting Node Server 1/21/2023, 05:50:37 [pg3] warn: [ST-Nuheat(4)]: Was not running. Starting... 1/21/2023, 05:50:40 [pg3] info: startNs:: ST-Nuheat 1/21/2023, 05:50:40 [pg3] info: startNs:: ST-Nuheat is valid 1/21/2023, 05:50:40 [pg3] info: checkLicense:: ST-Nuheat Valid perpetual license found. 1/21/2023, 05:50:40 [pg3] info: startNs:: ST-Nuheat finished update check 1/21/2023, 05:50:40 [pg3] info: [ST-Nuheat(4)] :: Starting Node Server - Version 1.0.2 1/21/2023, 05:50:41 [pg3] info: startNs:: ST-Nuheat updating database (enabled, timestarted) 1/21/2023, 05:50:42 [pg3] info: startNs:: ST-Nuheat starting polls 1/21/2023, 05:50:42 [pg3] info: Starting Node Server Info timer 0 1/21/2023, 05:50:43 [pg3] error: MQTTS: ClientID: 00:21:b9:02:50:a1_4 is already connected. Disallowing multiple connections. 1/21/2023, 05:50:43 [pg3] error: MQTTS: clientError: 00:21:b9:02:50:a1_4 Auth Error 1/21/2023, 05:50:43 [pg3] info: [ST-Nuheat(4)] :: Exit cause code: 2 - signal: null So I check the actual thermostat and confirm its on wifi. Login to the Nuheat web portal and it shows the thermostat online and I can control it from their web portal (I did this to double check the ID and password in the node server hadn't expired or changed - all good). Go to my Iphone Nuheat app which was already logged in and can control the thermostat. Go to my iPad which was already logged in and can control the thermostat. So this is were it gets weird, I logged out of the Nuheat app on my iPad and then try to login again on the iPad app and it says 'login failed' now (I know ID and password is correct as I just used them to login to web portal). Its almost like their backend is not allowing any more new logins/connections to my account or limiting the number of total connections? Any thoughts on how to correct it? Are others seeing this issue? I cannot even find a NuHeat support number to call, doesn't appear to be any? @simplextech

Unfortunately I am on the lowest scale windows 10 allows me of 100%. Sounds like there is no solution? thanks all for suggestions and advice.

994 and 5.3.4 Not sure how a node server affects core IOX functionality.

It’s fully enlarged and smallest font (12).

When using the admin console (windows 10) what is the secret for large nodes and being able to see all their attributes and commands at the bottom of the screen? See screen shot, there are attributes at the bottom of the screen (out of view) yet there is no vertical scroll bar on the right of the screen to allow me to scroll down and see them. What am I missing?

Yes, when my SD card started to fail. Would raise a ticket to confirm what is going on with your unit. In my case I needed to replace the SD card and restore from backup.

Had a similar issue. Had to delete then reinstall the NS in the same slot. My programs remained intact but had to edit and save them in the ISY to make them work again.

I am back. Hooray. Thank you.

Thanks @Javiand @lilyoyo1, regarding the question above I get the full range ie 0% 1% 2% ………99% 100%. Regarding all on, when I click it other devices in the network do not respond just this z-wave device.

A couple (probably silly) questions you would think I would know after using ISY for a decade: For my z-wave devices, see the screen shot below of one of my HomeSeer dimmer switches I have On, Fast On and All On as possible commands. I get that ‘On’ turns the light on to the last On level. I also understand ‘Fast On’ turns it on to 100%. But what does ‘All On’ do that is different to what either On or Fast On does? Also I am unable to edit the status to use anything but the default widget. Can widgets only be used for Insteon devices?

Have the same issue with my unit for what it is worth so just watching this thread. I am not too concerned by it however but would be nice to understand the issue.

Synchronization didn’t work so I deleted the node servers in POLISY and added them again which has for now looked to correct the issue. Thanks

Couple of items: In the PG3 Store when I click on the iTach IR hyperlink within the PG3 store to get more info on the Node server it takes me to the 'open sprinkler' repository After I install the Node server and go to configuration a message displays showing "Please set or check open sprinkler password and IP Address"

My Node Servers in my Admin Console are operating correctly, I see the Node Server and its individual nodes and the values within those nodes in the Admin Console (no problems). However, when using UD Mobile, again I see the node server and its nodes in UD Mobile, however all the values within the nodes are blank. This is happening for all my Node servers. My z-wave and insteon devices show correctly in UD Mobile but not the node servers. Have rebooted POLISY and still occurs. Running UD Mobile on iOS.

Does anyone know the voltage requirements for the POLISY? My current POLISY has a 5V 1A power supply, can the POLISY also be powered by the 12V 2A power supply that UDI sells for the 994i?

To summarize advise I got from Michel: From Polisy Admin Console | Configuration tab | Upgrade Packages. Once you hear 4 beeps, reboot Polisy If that doesn’t fix it, SSH in and issue following commands sudo unlink /usr/local/bin/pip3 sudo pkg upgrade udx Reboot Polisy again

This was solution that worked for me. From Polisy Admin Console | Configuration tab | Upgrade Packages. Once you hear 4 beeps, reboot Polisy If that doesn’t fix it, SSH in and issue following commands sudo unlink /usr/local/bin/pip3 sudo pkg upgrade udx Reboot Polisy again

The fix didn't fully correct the issue for me. In my case after running the update above, I also needed to SSH in and execute the following commands (provided by Michel): sudo unlink /usr/local/bin/pip3 sudo pkg upgrade udx

It gets me part way there, the challenge is the Alarm dismiss is not device dependent, so you cannot tell which echo device has its alarm dismissed.

Good to know, I did learn something today !!! Thanks. Perhaps I can send a suggestion to Amazon on it triggering a routine on an alarm activating and wait the 3 years to be implementedd !!!!

Thanks for the reply. re: what I am trying to achieve is when the kids or for that matter my Alarm goes off, certain things happen, HVAC turns on, shades open, certain lights turn on, etc. For most in our family our schedules are not fixed and so the alarm time from one day to the next changes for us all, so I was hoping that the alexa alarm (which everyone sets through the alexa app) could be a trigger for the ISY to do these things. re: Routines I can set a routine in Alexa to trigger at a certain time and play music to wake us, and then to your point change a variable on the ISY that then does those things above. Problem is getting the family to use/update an alexa routine each time they need to change their wake time is next to impossible on my end, its clunky and they just use the Alexa alarm feature instead. I suspect what I am asking for is not possible but thought I would ask in case someone had figured it out. Appreciate you sharing your thoughts

I am pretty sure this is not possible but will ask given I am always surprised with this forum and its ability to come up with solutions. I use Amazon Alexa throughout the house including in family members bedrooms who use their Alexa Echos as their alarm clocks and they use the Alexa app to update their individual alarms. Is there a way for Alexa to update a variable in the ISY when a particular Alarm goes on and off? I know I can use Alexa routines to do this, but the kids will only use Alexa Alarms. Wondering if this is something folks have solved for?