Jump to content

NodeLink v0.6.0


larryllix

Recommended Posts

Thanks for the dehumidify addition!

 

The web interface won't hold the ISY password.

If I retype my password into the box and hit set Nodelink appears to do one refresh from ISY and the rest of the System Config page fills in with parameter information and boxes.

 

Then it fails again and when refreshing the page it becomes short again. I can repeat this as often as I like and the same thing happens every time. Simultaneously the Node device pages refuse to show data with only

"Not authorized - Please setup valid ISY password"

2016-09-06 03:04:55 - ISY NodeLink Server v0.6.0 started
2016-09-06 03:04:56 - Web config server started (http://192.168.0.175:8090)
2016-09-06 03:04:56 - ISY resolved to 192.168.0.161
2016-09-06 03:04:58 - ISY Node Server config detected (profile 1)
2016-09-06 03:05:03 - Auto-Update: Checking for program update...
2016-09-06 03:05:04 - Auto-Update: No web update available
2016-09-06 03:05:08 - ISY Error: Login failure (verify ISY password on the system config page)
2016-09-06 03:05:38 - ISY Error: Login failure (verify ISY password on the system config page)
...
2016-09-06 03:09:12 - ISY Error: Login failure (verify ISY password on the system config page)
2016-09-06 03:09:42 - ISY Error: Login failure (verify ISY password on the system config page)
2016-09-06 03:10:13 - ISY Error: Login failure (verify ISY password on the system config page)

It would be nice if the nodesetup.zip files had the version in the filename and a link to it was made available with the other downloads. I find it each time by opening the instruction.pdf and clicking on the link wondering if I have downloaded an old version if trouble happens.  I cannot tell if the .pdf was upgraded for a newer NodeLink version either when things didn't perform as expected.

 

Since I cannot see the lower parameter boxes on my T7900 device pages with my usual computer screen, I could not even verify the Dehumidification box was added.   ISY format problem, not NodeLink's.

 

Thanks io_guy!

Link to comment
Share on other sites

Temporarily loaded v0.5.12 back in, and parameters are reporting fine again in ISY, until the NodeLink password instability can be sorted.

 

I see I was fooling myself with thinking that the humidity setpoint was functioning before. It wasn't in v0.5.12 either. Apologies for the confusion this may have caused.

I was falsely basing programs on the humidity setpoint value.

Link to comment
Share on other sites

Can you enable the verbose ISY log in NodeLink.  I have my doubts it's an actual login error.

 

I've run into a number of issues lately where the ISY is sending back a 401 when it shouldn't be.

I have v0.5.12 running now just fine.

 

Perhaps tomorrow I can do the report after reloading v0.6.0. Too late.

 

When I retype the password and hit set the forms fill in and it appears to communicate once and then fails again and device pages clear out.

 

Strange thing is when I first installed it  I was sure I saw the new  dehumidity_setpoint update  for a few seconds on the ISY screen but after that it was blank and never filled in again.

Link to comment
Share on other sites

It's likely what I said above. Same issue I've seen with others. NodeLink will essentially shut down on login failures, and there's times when the ISY will incorrectly send a 401 (like if you write to the wrong node profile for example).

Link to comment
Share on other sites

It's likely what I said above. Same issue I've seen with others. NodeLink will essentially shut down on login failures, and there's times when the ISY will incorrectly send a 401 (like if you write to the wrong node profile for example).

OK.  Enabled auto-update and it installed v0.6.0 again.

 

Compared before and after config.xml encrypted password = no change.

 

Here is the verbose report from NodeLink web page monitor.

 

NodeLink log.txt

Link to comment
Share on other sites

OK

 

Nodelink  v0.6.1 loaded automatically. = no luck

 

Verbose was only enabled after initial linking.

2016-09-07 02:09:59 - ISY NodeLink Server v0.6.1 started
2016-09-07 02:10:01 - Web config server started (http://192.168.0.175:8090)
2016-09-07 02:10:01 - ISY resolved to 192.168.0.161
2016-09-07 02:10:02 - ISY Node Server config detected (profile 1)
2016-09-07 02:10:38 - ISY Error: Login failure (verify ISY password on the system config page)
2016-09-07 02:11:08 - ISY Error: Login failure (verify ISY password on the system config page)
2016-09-07 02:11:39 - ISY Error: Login failure (verify ISY password on the system config page)
2016-09-07 02:11:55 - Web Request: /general.css
2016-09-07 02:12:06 - ISY: Variable utilstat-GV2 replaced in queue (Val: -1, QS: 17)
2016-09-07 02:12:09 - ISY Error: Login failure (verify ISY password on the system config page)
2016-09-07 02:12:21 - ISY: <?xml version="1.0" encoding="UTF-8"?><nodes><root></root><folder flag="0"><address>11805</address><name>Garage</name>
            <snipped lists>
1</link><link type="32">1A DA 2C 1</link></members></group><group flag="132"><address>ADR0001</address><name>Auto DR</name><family>5</family><deviceGroup>16</deviceGroup><ELK_ID>A01</ELK_ID><members></members></group></nodes>HTTP/1.1 404 OK
Content-Length: 105
Connection: Keep-Alive
WWW-Authenticate: Basic realm="/"
Content-Type: text/xml; charset=UTF-8
Cache-Control: no-cache
EXT: UCoS, UPnP/1.0, UDI/1.0
Last-Modified: Tue, 6 Sep 2016 22:10:9 GMT

<?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="false"><status>404</status></RestResponse> (nodes)
2016-09-07 02:12:21 - ISY: Variable gthrnstat-GV2 replaced in queue (Val: 1, QS: 17)
2016-09-07 02:12:22 - ISY Error: Error getting device list () - expected '>' (3E) but found '<' (3C)  Line 1, position 44601.
2016-09-07 02:12:40 - ISY Error: Login failure (verify ISY password on the system config page)
2016-09-07 02:12:41 - Web Request: /index.htm

Link to comment
Share on other sites

0.6.1 only included Honeywell Alarm fixes.

 

Think I found the error, it's a bug on my side. I'll cut a new release tomorrow.

 

(It actually has nothing to do with a login failure, V5 just returns terrible http codes)

 

Nice to hear. (fix, not the http codes)

 

My playing around just set my humidity setpoint to a higher setting and my dehumidify setpoint to 99% on the stat.

Weird. I didn't ever set any setpoints from anywhere that I remember.

 

With v0.5.12 now I am getting humidity on humidity and setpoint is not updating in ISY.

 

Thanks again!!

Link to comment
Share on other sites

Thinking about all this Venstar parameter mix-up.

 

Is it possible to just let the humidity parameters come through as labelled (read only) and let ISY users sort out what to use in their own programs?

 

Then, If and when Venstar ever straightens the mess out, changes only have to be made inside user ISY programs, and not inside Nodelink.

 

Also, different Venstar models that return different confusions (I understand), can just deal with it inside their own ISY programming by selecting the incorrectly labelled parameter to test for, in their ISY logic.

 

Or is more complicated than that with controls going the other way?

Link to comment
Share on other sites

Is this not what I'm already doing? If you want to swap just use dehumidifier for him and vise versa in your programs.

99% is the default if you don't set up a dehumidifier.

I have always used the humdity level from the sensor and it was per the stat reading.

 

It is not transmitted as humidity in the returned http query. I listed the actual response in the other thread. The 3 actual values are just shifted one to their titles.

Link to comment
Share on other sites

I am not sure what that means and confused by your repsonse.

 

Does the humidity not go in this sequence?

 

Humidity Sensor -> stat CPU -> response to NodeLink poll -> ISY device node - ISY programs and logic.

 

I have been using the T7900 humidity, from what I believe to be, this info-path, via NodeLink, in the humidty parameter. (NodeLink must be correcting placement)

 

My stat sends back this to my browser query:

"hum":0,"hum_setpoint":46,"dehum_setpoint":38,"hum_active":42

 

These values are all just shifted one label to the right and should have read:

"hum":46,"hum_setpoint":38,"dehum_setpoint":42,"hum_active":0-1?

by testing and varying the values sent from the stat.

 

My question/suggestion was. Can the parameters not just be sent through to the ISY node with the wrong assignments, and let each user sort them out with the incorrect labels inside ISY? All the info is there except I don't know what "hum_active" is. I suppose a boolean.

 

 

Does NodeLink not use this same poll response? What am I missing? Are we seeing different things for different models/versions?

Link to comment
Share on other sites

As for the shifting, again, that's your setup. I'm not violating a published API based on one data point.

If you can tell me this works in every combination than that's different. Meaning heat, cool and auto modes; humidifier enabled, dehumidifier enabled, both enabled and disabled, setpoint higher than target, lower, etc.

 

Last time I spoke with Venstar they indicated this was not a simple shift fix.

Link to comment
Share on other sites

As for the shifting, again, that's your setup. I'm not violating a published API based on one data point.

If you can tell me this works in every combination than that's different. Meaning heat, cool and auto modes; humidifier enabled, dehumidifier enabled, both enabled and disabled, setpoint higher than target, lower, etc.

 

Last time I spoke with Venstar they indicated this was not a simple shift fix.

I see where you are getting the sensor humidity from now.... a different poll response that appears to be labelled correctly. Thanks!

 

If you read the thread you pointed out again, you will see Paul and I are pointing out the same thing. (He didn't call it a shift :) )The data is labelled wrong for four parameters only. They are each shifted visually to one later in the query response, not the whole response, just the humidity and dehumidity parameters.

 

 

I wasn't asking you to change/shift  but something much simpler and in line with what you have done so far. Exactly what you are getting back, only to send it all through and let the ISY users sort it out, in their ISY programs.

 

This would entail creating a "hum_active" point in  ISY Venstar Node and sending what you get back from the response through to the three fields.

  • "hum" is already sent from the sensor response and completely correct values.
  • "hum_setpoint" is already being sent from the Info response
  • "dehum_setpoint" should be sent though to ISY. (I think you  already did this for v0.6.0)
  • "hum_active" would need an ISY point created,  and value received be sent through ,as received.

 

This way, ISY users can see the Venstar parameter confusion, use it as desired in programs, and straighten out their programs if and when Venstar ever corrects their end.

NodelInk doesn't need to be involved again on this matter at that time.

If different people's Venstar stats are reporting different parameter messes, it can all be re-handled by ISY user programming and change if and  when their stat firmware correctly updates.

 

Paul and I can both tell what data is what,  as reported in Paul's thread and this one.

 

Hope this makes sense.

Thanks a million!

Link to comment
Share on other sites

In the last post of the link I think Paul found an issue with the "decoder ring", mainly the humidity setpoint of 10%.

It appears to me he just got frustrated with the confusion.

All these setpoint, hum, dehum and attempting to cross relating things gets very hard to relate to others. LOL

 

Reading his post again I did pick up one thing he said and didn't know before...maybe.

The four confused parameters are rotated through the four spots.

...this is based on the "hum":0 is really the "hum_active" parameter...maybe. I haven't experimented with that yet. I didn't realise what it meant until reading the posts again.

 

Paul has a bit of an  "out", for his purposes, with the weather module that he uses.

Link to comment
Share on other sites

If you can confirm the 0/1 active is on hum, and give me the dump of your Venstar calls (I already have Paul's), I'll spend some time to try and put together a solution that works for all our stats (try to figure out why mine doesn't behave the same as you guys').

Link to comment
Share on other sites

If you can confirm the 0/1 active is on hum, and give me the dump of your Venstar calls (I already have Paul's), I'll spend some time to try and put together a solution that works for all our stats (try to figure out why mine doesn't behave the same as you guys').

After experimenting with no success for the last half hour I realised I was addressing the wrong stat! grrrrr... lOL

 

Yeah, I can confirm that "hum":1/0 means humidifier On/Off, so the four parameters on Paul's and mine are just rolled to the right with the "hum_active": being shown as "hum" (rotated back to the beginning of the four.

 

Where would you like the dump from?

 

http://192.168.0.170/query/info (stat= humidifier=off, sensor=45, setpoint=38, dehum setpoint=42)

{"name":"MAIN 0.000000LOOR","mode":2,"state":2,"fan":0,"fanstate":1,"tempunits":1,"schedule":1,"schedulepart":2,"away":0,"spacetemp":24.5,"heattemp":22.5,"cooltemp":23.5,"cooltempmin":1.5,"cooltempmax":37.0,"heattempmin":1.50,"heattempmax":37.0,

"hum":0,"hum_setpoint":45,"dehum_setpoint":38,"hum_active":42,

"setpointdelta":2.0,"availablemodes":0}

 

http://192.168.0.170/query/info (stat= humidifier=on, sensor=45, setpoint=52, dehum setpoint=55)

{"name":"MAIN 0.000000LOOR","mode":2,"state":2,"fan":0,"fanstate":1,"tempunits":1,"schedule":1,"schedulepart":2,"away":0,"spacetemp":24.5,"heattemp":22.5,"cooltemp":23.5,"cooltempmin":1.5,"cooltempmax":37.0,"heattempmin":1.50,"heattempmax":37.0,

"hum":1,"hum_setpoint":45,"dehum_setpoint":52,"hum_active":55,

"setpointdelta":2.0,"availablemodes":0}

Link to comment
Share on other sites

I got a quick response back from Venstar support (12 hour turnaround) today and the tech said he would pass it through to the department that created the local API and a fix would be issued ASAP.

 

I copied the two poll responses from my post #2 above to exemplify the problem.

 

This sounded positive but we'll see.

 

At least I didn't get the, "This is the first we have heard about it" response. LOL

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...