Jump to content

ISYLogger - Nodelink v4.0


larryllix

Recommended Posts

I am trying to build a monitor program to watch the change of setpoint from ISY => NodeLink => T7900.

 

I am not sure exactly what I am monitoring and at what point changes should occur. I discovered process success errors in my setback programs and have gotten a few notifications complaining of failure. This was due to my changing my RPi IP address and not changing the NodeLink setup in my ISY to hook it together. IIRC I may have got a notification about the T7900 comm failure and ignored thinking it was from other experimenting I was doing.

 

The object is to monitor the end to end success of changing a setpoint on the T7900 by a simple program that will time out in a few minutes if a setpoint change is not incurred during the Wait timer.

 

This program is enabled first and run (then) each usage. The triggers are to detect an actual change occurred and cancel the notification..

Venstat.watch - [ID 0112][Parent 0104][Not Enabled]

If
        'Gathering Room / GathRm VenStat' Heat Setpoint > 35.0°
    And 'Gathering Room / GathRm VenStat' Cool Setpoint < 15.0°
 
Then
        Wait  5 minutes 
        Send Notification to 'Text  Larry' content 'Venstar T7900  Setting Failure'
        Wait  2 seconds
        Run Program 'Venstat.watch' (Else Path)
 
Else
        Disable Program 'Venstat.watch'
 
Any setpoint change will cancel notification

I am not sure if the immediate  change in setpoint status will be due to ISY thinking it set the stat and an update will change it back later or if NodeLink will  reflect the actual setpoint regardless of asking it to change.

 

In each case a different timing mechanism would be required. I have run some testing but can't isolate all the factors in my real life situation and haven't really got this through my brain how the NodeLink flow mechanism works.

 

Any clarification and ideas would be appreciated to shortcut this brain clog.

Link to comment
Share on other sites

Hi Larry

 

I think the program will run every time the temperature changes within the range.

 

Rest calls from ISY->nodelink->stat are instantaneous. However, Nodelink polls the thermostat, so there will be a 0 - poll time delay in the ISY seeing changes from the stat. By default, that's 30 seconds.

 

This can also be tracked regularly by assigning it to a variable and then tracking that variable with ISY logger

 

One other suggest for the 'Then', you run it with a Repeat. Create a state variable called True. 

Repeat While True = True

 

The If statement becomes untrue, it will stop.

 

Paul

Link to comment
Share on other sites

Hi Larry

 

I think the program will run every time the temperature changes within the range.

 

Rest calls from ISY->nodelink->stat are instantaneous. However, Nodelink polls the thermostat, so there will be a 0 - poll time delay in the ISY seeing changes from the stat. By default, that's 30 seconds.

 

This can also be tracked regularly by assigning it to a variable and then tracking that variable with ISY logger

 

One other suggest for the 'Then', you run it with a Repeat. Create a state variable called True. 

Repeat While True = True

 

The If statement becomes untrue, it will stop.

 

Paul

Thanks Paul but I don't see how that would detect an ISY setpoint change failure.

 

The idea of the program is to detect a change in setpoint and cancel the notification.

 

The problem is, I am sure whether the setpoint change reflected in the stat's status in ISY is phoney, similar to other Insteon devices.  and just something that ISY thinks should be happening in the real world instead of actually happening.

 

I need to know more about the comm process to know when to detect a change. Immediately or wait for the next expected NodeLink update or perhaps I have to actually check for absolute numbers later. In that case if NodeLink isn't working no accurate feedback will happen anyway.

Link to comment
Share on other sites

There's no standard rule for NodeLink devices since they all communicate differently.

 

In the case of Venstar, the change you see in the ISY comes from the thermostat.  When you change a value in the ISY, it sends the request to NodeLink.  NodeLink sends the command to the Venstar and then immediately polls thermostat status and writes it to the ISY.

Link to comment
Share on other sites

There's no standard rule for NodeLink devices since they all communicate differently.

 

In the case of Venstar, the change you see in the ISY comes from the thermostat.  When you change a value in the ISY, it sends the request to NodeLink.  NodeLink sends the command to the Venstar and then immediately polls thermostat status and writes it to the ISY.

Thanks io_guy!

 

To reiterate and confirm

 

Unlike  Insteon devices, with ISY, that only send confirmations at low levels of the protocol, and contacts/outputs do not have to change, and devices only have to tell ISY they received the command,

 

 an ISY using NodeLink to a Venstar node, complete verification of control is done at the highest level of the communication protocol so that...

 

if the ISY change setpoint command  did not change the stat, at any point, anywhere, at any level in the protocol, the setpoint value in ISY  won't change, or even to change temporarily and then correct itself on the next poll.

Link to comment
Share on other sites

I can't comment on the ISY V5 workings. I don't know whether the ISY triggers a status change when you change the value in the ISY, or if it waits to get it from NodeLink.

 

It would be easy to test - just unhook NodeLink and change a value in the ISY and see if it triggers a program.

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...