Hi

I noticed that Venstar 'Space Temp' was added back in an earlier version. Was wondering if the Venstar 'Remote Temp' will also be added back at some point.

Thanks

Gary

Remote temp should now be a sensor node instead of in the main node. If it's not there send me a verbose log from the stat and let me know your firmware version.

 

The changes were made to support the newer Venstar firmwares.

Hi

I noticed that Venstar 'Space Temp' was added back in an earlier version. Was wondering if the Venstar 'Remote Temp' will also be added back at some point.

Thanks

Gary

 

You'll need to press the Install Nodes button to get sensor nodes to appear. The sensor nodes show up as thermometer icons and initially appear near the top of the device tree.

 

Paul

Edited December 28, 20177 yr by paulbates

io_guy

 

Not sure if this is what you are looking for or not. At the moment I am on version 5.0.10E. I don't see the Remote Temp node just the Space Temp node as a separate node.

 

You'll need to press the Install Nodes button to get sensor nodes to appear. The sensor nodes show up as thermometer icons and initially appear near the top of the device tree.

 

Paul

I did the install Nodes and the Space Temp appeared but not the Remote Temp.

Send me the log with verbose enabled on the venstar page. It's likely something with older firmware.

Is this server on the Pi?  system conigured EmonCMS server

?

NodeLink.

2017-12-27 22:35:59 - {"name":"Thermostat","mode":1,"state":1,"fan":0,"fanstate":1,"tempunits":0,"schedule":0,"schedulepart":255,"away":0,"spacetemp":70.0,"heattemp":72.0,"cooltemp":73.0,"cooltempmin":35.0,"cooltempmax":99.0,"heattempmin":35.00,"heattempmax":99.0,"activestage":1,"hum_active":0,"hum":54,"hum_setpoint":40,"dehum_setpoint":99,"setpointdelta":2.0,"availablemodes":0}(G) [ven1]

2017-12-27 22:35:59 - Venstar Info Data - {"name":"Thermostat","mode":1,"state":1,"fan":0,"fanstate":1,"tempunits":0,"schedule":0,"schedulepart":255,"away":0,"spacetemame":"Service","active":false}]} [ven1]

Edited January 2, 20187 yr by garybixler

Perfect. I'll take a look tomorrow and get it fixed up.

Hi

I just installed the 0.8.9 version and am still not able to add the Remote hard wired Venstar sensor. I do get this error however:

2018-01-01 22:32:57 - ISY Error: Status 400 (INVALID_NODE_ADDRESS): ns/2/nodes/n002_ven1_sEX/add/VenstarSensorF?primary=n002_ven1&name=Remote&nls=140VS

 

Thanks

Gary

Hi Gary
I just updated. I don't have hardwired, but had the same log error. I deleted all of the sensor nodes, pushed install nodes for each stat and I was back in business 

 

My nodes returned, working properly, named as  I named them in the AC and in programs correctly

 

Paul

Hi Paul

I have tried that sever times but I always get the Space Temp over and over but can't seem to get the Remote Temp.

Gary

That's my bad. It's the 400 stopping the Remote Sensor. I'll get a new version out ASAP.

Hi Gary

I just updated. I don't have hardwired, but had the same log error. I deleted all of the sensor nodes, pushed install nodes for each stat and I was back in business 

 

My nodes returned, working properly, named as  I named them in the AC and in programs correctly

 

Paul

Careful with that technique. I have done it many times over the years with various devices, but occasionally ISY will show you the same name in the programs but they still won't function.

 

The fix I found to ensue it works is the click on the program line containing that device and then click update to refresh the line. Of course save when done. Combined with a search for that device, is can be done in a few minutes for the whole ISY program system.

Thanks so much io_guy

Gary

V8.10 went well!

 

The auto install Nodes and ISY reboot are excellent. NodeLink reported a superfluous node that I deleted, along with another one. Very nice stuff!!

 

However,

NodeLink installed another node for the Venstar stat again ID = ."n001_ven1_s01 - Ecobee Sensor ©",  Named = "Smart SpaceTemp"

 

I do not have any remote sensors for my Venstar and grouping it in ISY makes it a sub of the Venstar stat.  This was happening before v8.8 also.

 

Thanks io_guy!!!

 

I haven't had time to investigate the ecobee (smart1,2,3) climate stuff yet.

Edited January 3, 20187 yr by larryllix

Not sure what you're saying. There's no chance an ecobee sensor got installed under the venstar.

 

A log is worth a thousand words.

Not sure what you're saying. There's no chance an ecobee sensor got installed under the venstar.

 

A log is worth a thousand words.

 

When you look at the venstar sensors in the ISY at the top when selected, they're node name labeled as ecobee. I chalked that up to code re-use copying/pasting at some level, and didn't worry about it. Its definitely not a functionality problem and I wouldn't suggest investing time changing

 

Paul

Ahh, gotcha.  Just a typo in the nodedef file - it's always been in there.

 

Larry,

In that case I'm guessing you meant "Space Temp" not "Smart Temp".  Space temp is some new Venstar firmware thing - I believe it's the actual thermostat temp, where the main node thermo temp is the controlled average.  Dunno but it's supposed to be there.

Currently Space Temp and the Temperature Node are always the same. However:

• Spacetemp should always be what the thermostat is sensing
   
• The temperature value returned by previous APIs should now return the average of the thermostat and its sensors, depending how its configured

The new drop down dashboard shows that difference, but the API isn't returning it correctly. 

 

I do use this for fan cycling. If the difference between the 2 actual sensors, un-averaged, is greater than 2 degrees, I switch from from intermittent fan cycling to full fan on until they're back within 2. Not a huge deal, but its not reporting properly. Handling it this way does float the next HVAC call out a little bit.

Venstar has this API bug logged, so eventually the 2 will be different, but for now, they're the same.

 

Paul

Edited January 3, 20187 yr by paulbates

Ahh, gotcha.  Just a typo in the nodedef file - it's always been in there.

 

Larry,

In that case I'm guessing you meant "Space Temp" not "Smart Temp".  Space temp is some new Venstar firmware thing - I believe it's the actual thermostat temp, where the main node thermo temp is the controlled average.  Dunno but it's supposed to be there.

Yes.

My mistake. It was "Space Temp". The ecobee thing was just as Paul stated. No big deal.  I don't have one but it installs the Venstar  node anyway.

 

 

When I remove the superfluous node that NodeLink complains about I get this continuously

 

2018-01-02 21:12:16 - ISY NodeLink Server v0.8.10 started

2018-01-02 21:12:16 - Mono version: 5.2.0.215 (tarball Mon Aug 14 16:25:12 UTC 2017)

2018-01-02 21:12:16 - ISY resolved to 192.168.0.161

2018-01-02 21:12:16 - Web config server started (http://192.168.0.175:8090)

2018-01-02 21:12:16 - ISY Node Server config detected (profile 1)

2018-01-02 21:13:05 - ISY Error: Status 404 (FAILED): ns/1/nodes/n001_ven1_s00/report/status/ST/21.0/14

2018-01-02 21:13:35 - ISY Error: Status 404 (FAILED): ns/1/nodes/n001_ven1_s00/report/status/ST/21.0/14

2018-01-02 21:14:06 - ISY Error: Status 404 (FAILED): ns/1/nodes/n001_ven1_s00/report/status/ST/21.0/14

2018-01-02 21:14:36 - ISY Error: Status 404 (FAILED): ns/1/nodes/n001_ven1_s00/report/status/ST/21.0/14

2018-01-02 21:15:06 - ISY Error: Status 404 (FAILED): ns/1/nodes/n001_ven1_s00/report/status/ST/21.0/14

2018-01-02 21:15:36 - ISY Error: Status 404 (FAILED): ns/1/nodes/n001_ven1_s00/report/status/ST/21.0/14

 

When I install the node I get this

 

2018-01-02 21:16:37 - ISY Error: Status 404 (FAILED): ns/1/nodes/n001_ven1_s00/report/status/ST/21.0/14

2018-01-02 21:16:45 - ISY Error: Status 400 (NODE_ALREADY_EXISTS): ns/1/nodes/n001_ven1/add/VenstarC?primary=n001_ven1&name=Venstar&nls=140

...and then this after reboot

2018-01-02 21:17:54 - ISY NodeLink Server v0.8.10 started

2018-01-02 21:17:54 - Mono version: 5.2.0.215 (tarball Mon Aug 14 16:25:12 UTC 2017)

2018-01-02 21:17:54 - ISY resolved to 192.168.0.161

2018-01-02 21:17:54 - Web config server started (http://192.168.0.175:8090)

2018-01-02 21:17:55 - ISY Node Server config detected (profile 1)

2018-01-02 21:17:56 - ISY Warning: Duplicate node names exist on the ISY (Space Temp)

2018-01-02 21:17:59 - ISY Warning: Stale node exist on the ISY (n001_ven1_s00)

 

Edited January 3, 20187 yr by larryllix

Update:

 

(Ignore the incorrect manufacturer name in the node address. It has been noted and insignificant in this )

 

NodeLink creates a "Space Temp" node for the Venstar stat named "n001_ven1_s00 - Ecobee Sensor ©" This node is active and updates to the temperature of the stat with a duplicate report. I have no external sensor on the Venstar stat.

 

If I reboot NodeLink it will automatically install another node named "n001_ven1_s01 - Ecobee Sensor ©". This new node will become active (updates to main stat temp sensor) and then deactivate the first node ".....s00 - ....."

Now NodeLink complains about a stale node on the ISY (see above post).

 

This process can be repeated every time it is tested. No third node is ever created by rebooting.

 

When the nodes are deleted the  404 errors is generated and NodeLink stops updating two  ecobee stats and the Venstar stat. The heartbeats do not change until the Node(s) is reinstalled.

 

I have had many other random events during this process. My garage door has notified  open and then closed again without any record in the logs or events of a status change, over the last few days. My three stats ( 2x ecobee + 1 x Venstar) notify of  comm failures at random about once per day, each. My ecobee4 stat was set to hold at 16 degrees today as well as other temperatures on the previous few days. I am not sure any of this is related to this problem.  These ISY programs have worked without problems for the last year or so.

 

I am contemplating factory resetting my ISY, as this has cured problems like this in the past, when nodes were installed and/or removed without success the first attempt.  ISY and NodeLink have both been reset many times without any improvement.

Edited January 3, 20187 yr by larryllix

I feel like a broken record...  How about a log?

 

Yes updates will stop, it's all the same buffer to the ISY that is failing.  Stop resetting shit and just give me a proper log.  Verbose Venstar & ISY enabled with it creating s00 and s01 (or whatever it is you are describing above).

I feel like a broken record...  How about a log?

 

Yes updates will stop, it's all the same buffer to the ISY that is failing.  Stop resetting shit and just give me a proper log.  Verbose Venstar & ISY enabled with it creating s00 and s01 (or whatever it is you are describing above).

Please see this thread for my log  capture where Bipto has the same situation. Thanks

 

https://forum.universal-devices.com/topic/23294-missing-venstar-tstat-outdoor-temp-after-upgrade/?p=230038