ST-NuHeat Node Server UD Mobile issue

[steve-elves]

I managed to install the Node Server easily, and it found all my thermostats.  From the ISY screen on my PC I can write to setpoints on individual thermostats; programs can change setpoints as well.  The issue is with the UD Mobile app on my Samsung phone.  I can see the individual thermostats and all their data, but when I try to access any to change the setpoint, I get an error message (see attached).  Anyone got any ideas?

[Javi]

Hi @steve-elves,

It's an error with the Node Server profiles,  the node server dev will have to fix this issue. 

Notes: There appears to be an init value of "1" and no status value to match.

https://wiki.universal-devices.com/index.php?title=UD_Mobile#Node_Status_Relation_Cursor_is_empty

 

[steve-elves]

Thanks for the explanation.  I figured there was a piece missing somewhere! 

Do you have contact information for the node server dev handy?

[simplextech]

14 minutes ago, steve-elves said:

Do you have contact information for the node server dev handy?

You rang?  I can take a look but I don't use UD mobile nor even aware if it's available for iOS so it will be difficult to test.  I'm also not sure what piece is missing so I'll have to investigate.

[Javi]

Hi @steve-elves,

Please send me a private message with the UD Mobile back so I can help find the the location of the error.

[steve-elves]

I'm not sure what you mean by the "UD Mobile back"?  Do you mean a backup?

Also, please excuse my ignorance, but how do I send you a PM?

[steve-elves]

Also, thankyou to Simplextech for responding!  I'm sure we can get to the bottom of this.

[Javi]

Yes, backup.  I sent you a PM, it should show at the top of the forum in the mail icon.

[simplextech]

3 hours ago, steve-elves said:

Also, thankyou to Simplextech for responding!  I'm sure we can get to the bottom of this.

The nodedefs file for the NS has been updated which should correct the UD Mobile error.

A new package has been released to the NS Store and should show and update available.  Please keep me informed.

[steve-elves]

Got the update from the Node Store (v.1.0.2) but now it won't start from Polyglot 3 - I click "Start", it shows as starting, but then immediately shuts down.  I have rebooted both the ISY and Polisy Pro to try to resolve the issue, but no luck yet?  Is it possible that the fact I'm on day 2 of a 7 day free trial is causing the issue?

[simplextech]

7 hours ago, steve-elves said:

Got the update from the Node Store (v.1.0.2) but now it won't start from Polyglot 3 - I click "Start", it shows as starting, but then immediately shuts down.  I have rebooted both the ISY and Polisy Pro to try to resolve the issue, but no luck yet?  Is it possible that the fact I'm on day 2 of a 7 day free trial is causing the issue?

I don't think the trial has anything to do with it.  Or I would hope not.  There nothing in the code that defines the trial or difference in functionality that's all part of the PG3 Store.

There are instances where a NS does not stop correctly and then will not start up again but this is resolved by killing the old process or by rebooting which you did.  So this isn't the issue.

Before I pushed the update to the store I removed and re-installed my local version and I did not have any problems.  If the update process is not working for you then please try a delete of the NS and then fresh install of the NS.  If this works I'll have to go back and install an older version and try the update and if there's a problem with the update I'll work with UD.

[steve-elves]

Success!  Removing the previous instance completely and reinstalling it seems to have worked perfectly.

It took a little while for UD Mobile to catch up, even after re-sync.  I also notice that the setpoint values appear "sticky" in the mobile app - if I bump up the desired temperature by a couple of degrees, the new SP shows up directly on the thermostat and on the device page in the ISY Admin console, but it takes over a minute for the newly-entered SP to reflect accurately in the device details on the mobile app.  I'm thinking this is a "feature" of the polling timing, and isn't really a bug.  I'm content to be able to practice being patient.

Thank you for your efforts in resolving this.  I will be purchasing the NS when my free trial runs out - it's worth it!