Touchscreen Interface for Vera...download

[Henk]

@Tim

Feedback on version 1.0015

General remark, most functionality bigs seem to be solved.
There are some inconsistencies on viewing tabs and control tabs
Also some views are "out of sync/range"

Il try to do a categorized overview below:

----Charts---
Digital charts:
- settings are not saved
- Chart help is empty field

Analog charts
- settings are not saved
- various buttons and associated borders are not aligned
- scroll and graph buttons write through chart descriptions

----Controls----
- Setup control tab text runs out of assigned field size
- no setup on/off option for thermostats (compare dim/switch tab)
- Security sensor shows green OK button (whats the function, my sensor has setting bypassed atm)
- clicking the same button changes nothing
- when scenes are added/removed, saved settings do not persist

----Devices----
- raw data tab has no header row describing the colums value

[TimAlls]

----Charts---
Digital charts:
- settings are not saved
- Chart help is empty field

Saving Chart defaults will be next....
I find them a very useful tool, what do you think?
Chart Help......wooops...I will fix it!

Analog charts
- settings are not saved
- various buttons and associated borders are not aligned
- scroll and graph buttons write through chart descriptions

I think I am having font and scaling issues....can you capture the screen and send it to me?

----Controls----
- Setup control tab text runs out of assigned field size
- no setup on/off option for thermostats (compare dim/switch tab)
- Security sensor shows green OK button (whats the function, my sensor has setting bypassed atm)
- clicking the same button changes nothing
- when scenes are added/removed, saved settings do not persist

Screen shot?
Thermostat setup coming on next update.
Security, I will allow it to be turned off on next release. It is a great visual for those of us monitoring doors and window, it has nothing to do with arm, disarm, bypass. It just reports the current status, Open or Closed. From a security standpoint this is wonderful to have at a glance. When you are getting ready to leave home you know instantly to close the window upstairs....or whatever. It also records the information....

EG I wish I had this when my kids were teens.....I would have know they were slipping in and out through the window late at night!
I will check on the scenes....

----Devices----
- raw data tab has no header row describing the colums value

I call it raw data because it is not formatted....it's just the way Vera reports it. As such Vera mixes up all the columns just for the fun of it, so I can't add Headings. It is a good tool to pick out information not seen in the organized table.

For those of you with dimmers give me feedback.....I just reworked them for my touchscreen. That part of the system has to make sense to the wife and kids!

Thanks Henk,
Tim

[Henk]

@Tim,

Screenshots sent.

By the way i do have some remarks on your last post...

1. charts usefull YES (ill have toi see what happens after 24h... problem is id have to leave my computer on... which is a drawback)

2. On security devices... i only get a green OK. Even when the state is bypassed... i can understand that relative buttin names are difficult (to reflect current state, armed, bypassed, tripped etc) but in fact that would be most usefull

3. raw data yes... but theres still a pattern:
f.i.

Column 2 always "name" (prefix for column 3?)
Column 3 always actual  name of device
Column 4 always "altid" (prefix for ALTID #?)
Column 5 always actual altid number/name
Column 1 and 9 always Device ID


In fact column 2 could be used as a header for 3, 4 as header for 5, 6 as header for 7, 8 as header for 1 and 9
and 10 as header for 11. Lastly column 12 could act as header for 13, after that input becomes more random but still reflect "luup variables"

[TimAlls]

Screenshots sent.

Thank you, that will make it easy.

2. On security devices... i only get a green OK. Even when the state is bypassed... i can understand that relative buttin names are difficult (to reflect current state, armed, bypassed, tripped etc) but in fact that would be most useful

The way I have it set up now is ideal for an external alarm system showing multiple zones..
Perhaps I need to rethink the way it displays ZWave motion detectors and similar type devices.

3. raw data yes... but theres still a pattern:
f.i.

I think when you see your system grow you will understand. For me and others with larger systems and lots of scenes the columns get messy.
That is really the purpose of the second device list....to sort it all out.
I will give it some thought....there might be a better way.

Regards
Tim
update tonight with bugs fixed......

[Henk]

@Tim,

Referring to this thread:
http://forum.mios.com/index.php?topic=6770.0

Is it possible to set scenes/rooms/devices to hidden/unhide through your app?
Since you read the status out of the user_data, it should also be possible to inject something?

Let me know if you see options...

[TimAlls]

@Tim,
Referring to this thread:
http://forum.mios.com/index.php?topic=6770.0
Is it possible to set scenes/rooms/devices to hidden/unhide through your app?
Since you read the status out of the user_data, it should also be possible to inject something?
Let me know if you see options...

I have a variable changing routine already written....I will try hiding and unhiding a scene ans see what happens.

Here is 1.016 that has your bugs fixed.....scaling is off, so see if that takes care of it.

http://www.box.net/shared/ztne65frs9vt1l77yy39

Regards
Tim

[TimAlls]

1.018....added hide security and save Thermostat and Security info
Latest....http://www.box.net/shared/so30ep0uibzn4sjhipjg

3. raw data yes... but theres still a pattern:
f.i.

Column 2 always "name" (prefix for column 3?)
Column 3 always actual  name of device
Column 4 always "altid" (prefix for ALTID #?)
Column 5 always actual altid number/name
Column 1 and 9 always Device ID

Added column names....this will be ok for new firmware....older firmware the order is totally different!

Regards
Tim

[ballroller]

On the thermo's, set cool is not working. Doesn't seem to do anything. Nor do the fan settings.

[TimAlls]

On the thermo's, set cool is not working. Doesn't seem to do anything. Nor do the fan settings.

You may have told me but what is the brand/model of the thermostats. It is strange that some of the functions work. I need to make sure the commands are the same for all brands....MCV was very consistent on dimmers and switches to use the same commands no matter what the brand was.....I hope this one is the same.
How do your dimmers work.....they have been overhauled!
Regards
Tim

[ballroller]

They are all Trane's- like your picture.

I only have one dimmer but it works perfectly.

Thanks.

[TimAlls]

They are all Trane's- like your picture.
I only have one dimmer but it works perfectly.
Thanks.

I have been testing my thermostat which is a Wayne Dalton and it works fine. I have noticed that the update time on some of the functions can take as long as five minutes. My software sends the commands out and Vera doesn't update the variables until it hears back from the thermostat. The thermostat has timers on turning off the fan that I think slow things down.....
Take a second look and see if the values change over time.
Use my variable watch as well and see what the Vera is reporting.

Regards
Tim

[MNB]

@TimAlls, reading your last update you indicate something about hiding/unhiding for Devices and Scene? I look through all the tabs and could not find any indication of hidden vs not hidden items... am I missing something? Also you indicated that we could change the room titles and sequence is possible and if so how?.

Observations:

• Need some way of indicating fields that are reporting value vs user changeable values denote via color or some other schema. The reason is that in a number of fields the user seems to be able to change values e.g. setup tab but after depressing enter it returns to previous value.
  
• What happen to the scene LUA coding tab?
  
• Setup tab - what is the general path boxes there is an icon two boxes connect, when you fly over the bottom one provide you a selection of valid vs not valid path, whilst the top path does not present me with the choice.
  
• Setup tab - Am able to change Port address using the up/down controls, when I select a different port I get a read error however the read lead still flashes green like its communicating.
  
• Variable watch tab - when moving ones cursor over a field and selecting it the user feed back is that you can change values but can't
  
• Reports tab - seems to go directly to the analog graph, would have expected the first tab reports or last used. What value is the analog graph, since you fixed the digital graph make better sense and more useable.
  Why is Categories and Room tab in the reports tab, would expect it to be with the scene and device tabs in fact since they are all reports maybe they should be in the report tab.
  
• In the report, scene and device tabs seem like there is a blue vertical line in a number of the fields columns, seems to be in different columns in different tables.
  
• Control tabs - the switch, dimmer, scene  and security titles are being truncated, not enough real state.
• Dimmer value allows user to input a numeric value but doesn't take.
  
• Get rid of the Pad how to tab and make like you did the setup-tab "Notes" be consistent.
  
• Digital graph, is there a way of recording the history and being able to play it back would be good for trouble shooting LUA code interactions.

Definitely looking better... currently the only tab that can be inter acted with is the controls tab. Would like the ability to sequence the report tables by selecting a column and having it sequence A-Z or Z-A.

[MNB]

@TimAlls, I noticed that your "Touchscreen for Windows" post seems to be void of observations for the past two days. Me thinks that the move from "Scene Scripting" to "Remote Control" has caught most folks by surprise as there isn't anything within the "Scene Scripting" folder indicating that your subject was moved and "Remote Control" which in my humble opinion is not the most intuitive location. Mike

[TimAlls]

@TimAlls, I noticed that your "Touchscreen for Windows" post seems to be void of observations for the past two days. Me thinks that the move from "Scene Scripting" to "Remote Control" has caught most folks by surprise as there isn't anything within the "Scene Scripting" folder indicating that your subject was moved and "Remote Control" which in my humble opinion is not the most intuitive location. Mike

Hi Mike,
I am not ignoring you .... we are trying to get a 92 foot yacht ready to sail......been tied up. I knew the move would be confusing....I have put code generation on hold until I am done with the current project of touch screen control. I need to get the final done so it can be installed on our latest yacht. All of the reporting functions etc. were laying the foundation for the Control Point interface. I am also going to be adding camera control which is going to be a challenge but I have the basics working. I will be adding a tab that displays 4 cameras in each tab and the camera will pan to a location that you touch....very nice. All panasonic cameras right now and very fast since they go straight to the cameras!
More to come....I hope others will find me here.
By the way, I have found a way to trigger vitual switches in Vera from VISUAL motion detected by the panasonic cameras.....it works with sound as well!
Regards
Tim Alls

[MNB]

@TimAlls,  I wasn't implying that your ignoring me, we all have real lives other than our hobby VERA . My only point is that you were getting inputs from several other folks and with the move it seemed to drop to nil. I'm excited about the Panasonic camera feature as all of my camera's are the same, I'm assuming that your using the camera's capability for visual/sound detection? Will await your future updates. Out of curiosity your boat or business related? Mike