Cut off display

[garybixler]

Hi

Just wondering if this is normal. Even in full screen I can't get all the Venstar info to be displayed.  

I am on version 5.0.10.

Thanks Gary

[larryllix]

Hi

Just wondering if this is normal. Even in full screen I can't get all the Venstar info to be displayed.  

I am on version 5.0.10.

Thanks Gary

Looks good to me!

You don't appear to have an outside sensor connected or set your humidity setpoints.

 

The heartbeat will cycle 1, -1 repeatedly and you can use that to detect a comm failure before making assumptions with program logic.

 

I also use it to notify myself I have lost my connection after a few more minutes of failure. Requires a program, a variable and a notification message.

[paulbates]

Its a function of a java thick client app (Admin Console) and your systems screen resolution. It all just fits in with 1920 x 1080.  

 

If it doesn't fit, you can still use the scroll bars / arrows on the right side of the windows

 

Paul

[larryllix]

Its a function of a java thick client app (Admin Console) and your systems screen resolution. It all just fits in with 1920 x 1080.

 

If it doesn't fit, you can still use the scroll bars / arrows on the right side of the windows

 

Paul

Oh...I am so familiar with partial screens, I didn;t notice and my only thought he was referring to the parameter values.

On my monitor I can only see about the top half of the parameter boxes and there is no scroll bars on my Windows 7. I have to use another computer when I want to investigate the finer details.

[garybixler]

Scroll bars would solve the issue but they don't appear. I can just barley click on Cool Setpoint. but don't know if there is anything else below.

Win 7

[paulbates]

The up/down arrows in your picture, just left of the word 'Membership' is how you would scroll the list. The only thing in that list are drop down items to control the thermostat manually from the Admin Console. Those are nice to confirm everything's working initially, but probably won't get used that often afterwards, the real power is calling those same items from a program

 

Paul 

 

 

[larryllix]

What was that about a scroll bar?

 

 

 

[garybixler]

Thanks Paul I see that now. I usually don't open full screens for anything so I completely missed that.

[paulbates]

What was that about a scroll bar?

 

 

Are you running that on a palm pilot?

[larryllix]

Are you running that on a palm pilot?

A laptop that doesn't fly some times. It never needs a pilot.

 

But, as you said ...the programs all work just fine.

[SetMonkey13]

On 5/19/2017 at 9:38 AM, larryllix said:

Looks good to me!

You don't appear to have an outside sensor connected or set your humidity setpoints.

 

The heartbeat will cycle 1, -1 repeatedly and you can use that to detect a comm failure before making assumptions with program logic.

 

I also use it to notify myself I have lost my connection after a few more minutes of failure. Requires a program, a variable and a notification message.

Do you have an example of a program that checks the heartbeat to make sure its working?  I'm having a hard time wrapping my head around how to check it.  Thanks.

[paulbates]

Here is what I created. No variables needed:

If
        'HVAC / Family Room' Heartbeat is -1
     Or 'HVAC / Family Room' Heartbeat is 1
 
Then
        Wait  4 minutes 
        Resource 'Pushover HVAC Log - Familyroom Venstar Down'
 
Else
   - No Actions - (To add one, press 'Action')
 

It restarts every time the value swaps. If it stops swapping, something is wrong with Nodelink or the device it supports

The wait time needs to be something that works for you. There can be normal, self-cleaning comm issues that happen within a minute. I set the 4 minutes here to not get "false positives" when in fact nothing is really wrong. 

Paul

 

[larryllix]

1 hour ago, SetMonkey13 said:

Do you have an example of a program that checks the heartbeat to make sure its working?  I'm having a hard time wrapping my head around how to check it.  Thanks.

Here is the one I currently use for my ecobee stats. It allows two missed updates in a row. The cobees are slwo updating at about a 3 minute interval.

I developed this idea when my two Venstar stats were cutting in and out very frequently and I didnt want t be bothered until it became a more permananent problem so I developed a multi stage process. Now the Venstars seldom ever go down and my ecobeess are doing it.

 

 The Integer variable is set early and can be used by other programs to tell them the stats may be out of date or incorrect. Notifications are issued later.

$Alarm.level = 1 raises an internal alarm at home and level 1 consists of a few beeps of a buzzLinc only.

An email and a text message is then sent after another 30 minutes of continuous failure.

A text message is then repeatedlt sent every 8 hours if vacation mode is not activated. This avoids the nuisance of being away on a cruise for four weeks and getting swamped with mental stress. Around home or town I need to repeatedly know until I fix it or get a workaround for my stat smarts.

If the heartbeat is ever returns, the Integer  variable is set True again so that programs needing it  can respond immediately again.

The program colour indicates positive also. Green for OK (as program is  named) and red for not OK..

Note :"Run at Startup" is enabled and it requires no second program to make it self-start.

This line logs the event in an Internal ISY log. You can forget about it and not use it.

       Send Notification to 'eMail Larry' content 'Logger - HVAC  Entry'

---------

DinRm.Stat Comm.OK - [ID 009B][Parent 00CD][Run At Startup]

If
        'Dining Room / GathRm Stat' Heartbeat is 1
     Or 'Dining Room / GathRm Stat' Heartbeat is -1
 
Then
        $GathRm.stat.updating  = $cTRUE
        Wait  6 minutes 
        Run Program 'DinRm.Stat Comm.OK' (Else Path)
 
Else
        $GathRm.stat.updating  = $cFALSE
        Send Notification to 'eMail Larry' content 'Logger - HVAC  Entry'
        Wait  30 minutes 
        $sAlarm.level  = 1
        Send Notification to 'Text  Larry' content 'Device comm report'
        Send Notification to 'eMail Larry' content 'Device comm report'
        Repeat While $sHouse.vacation is $cFALSE
           Wait  8 hours 
           Send Notification to 'Text  Larry' content 'Device comm report'