The Vera Community forums have moved!

General => Remote Control => HomeWave (iOS) => Topic started by: intveltr on July 16, 2012, 03:58:03 pm

Title: Beta started!
Post by: intveltr on July 16, 2012, 03:58:03 pm
The beta testing for HomeWave has started.  Those who have accepted the TestFlight invite (or sent me their UDID) should have an email, and should be able to download & install the app.

A couple of quick tips to get started:
- The settings for HomeWave can be found in the Settings of your iPhone (not in HomeWave itself)
- If you run HomeWave on your home LAN, it will likely detect your Vera automatically (and inform you).  If you use multiple Veras, go into Settings and enter the IP address manually
- To use HomeWave in combination with MIOS, enter your MIOS username, password and device ID in the Settings screen.  Note that the device ID will be filled in automatically, if you have already set up some controls in HomeWave (see also Shortcomings below).
- Device rotation is respected, but it works by rotating individual controls. This is intentional.  The setup windows / popups only work in Landscape mode.

Known issues
- Loading the device config / starting the app can be slow on older iDevices.  This is due to a resource intensive XML decoding library.  This will be replaced by a custom decoding routine with better performance.
- HomeWave does not run on iOS 3.x devices.  If possible, the app will be made compatible with this iOS to support older hardware.
- Swipes that start on a dimmer / thermostat control are not recognised as such.  This is because the control "steals" the swipe action and thinks it is supposed to spin up/down.  No easy/logical fix found as yet.

Additional features (To be added after the beta)
- Custom messages for popups.
- The buttons on the Home screen are a bit limited.  Icons and custom colors will be added to these.
- Support for controlling multiple devices with a single control (for example: multiple dimmers)
- iPad support
- Location-based triggers
- Push messages for alarms, etc.
- (optional) battery level indicator.
- Arm/Bypass control for binary sensors.
- Support for arbitrary plugins.
- Loading, saving and sharing of configurations (individual screens and full configs)
- Remote configuration management
- Option to lock the complete app based on the state of a Vera Switch (for example: caretakers can only access the app when the house is in "Away" state, for your privacy)

Unsupported devices (To be added "soon")
- Door locks (pin code management)
- Power Meters (separate power meters are supported)
- Blind controllers
- Smart power meter plugin (by bfromdruten)
- Custom devices (from plugins)

Fixed issues
- Attempting to set custom colors in iOS 4.x results in a crash.
- Create a new screen, and then delete it, it is still there if you swipe left/right. Killing the app and restarting fixes this.
- When rotating to Landscape, confirmation popups are not right side up.
- Scenes do not always update correctly after being triggered. 
- Default text for untriggered sensors ("---") is a bit ambiguous, change to "ok"
- Door sensors
- Support for Fortress WWA02 temp/water sensor
- Off text field sometimes cannot be tapped and edited.  Workaround: tap the On text field first, then the Off field.
- Add temperature readout in Fahrenheit
- CT30 Thermostat ,3M-50 Thermostat plugin
- Virtual Switch & combination switch plugins
- Choice between swiping or buttons to switch between screens (or both) 
- Device list comes up empty if there is no room defined on Vera.  Workaround: add a room.
- Support for Cameras.
- Support for Thermostat mode, fan setting and cooling setpoint. 
- Camera pan/zoom
- Camera image sometimes blanks out for no reason.
- Vera IP address is assumed to be fixed.  This means the app will always switch to MIOS even when on the LAN, if Vera got a new IP address.  Startup process will be changed to always execute the Vera discovery process, and correct the IP if necessary.
- Optional timer to automatically return to the default screen.
- Locks (basic open / close, experimental)
- Issue with some thermostats
- Localisation   (Framework + English / Dutch
- Door locks do not respond to HomeWave commands
- Thermostat control to display "(off)" instead of 0 when the thermostat is in "off"mode.
- Power Meter support
- Display thermostat mode (heating, cooling, idle)
- Refresh button / poll device
- PIN code to protect the app (on 3G and/or WiFi), certain screens, or specific controls.
- add info screen
- lock out edit mode if a pin code is set
- instructions (on web site)

Last build (TestFlight #20): 15 aug
Next build: none (unless a major bug comes up)


When testing the app, please add any findings, problems or suggestions in this thread or in a separate one.
Title: Re: Beta started!
Post by: TommyE on July 16, 2012, 04:05:38 pm
Helllo

Had the chance to play with the app for 30 minutes now, and I must just say thank you for creating something like this. It is just what I wanted, and for once I have had some luck with the timing, beeing a VeraLite owner for only three days now :)

I've found one possible bug.

I you create a new screen, and then delete it, it is still there if you swipe left/right. Killing the app and restarting fixes this. Not a big thing though...

Thank you again for a great and promising new app.

Regards
TommyE
Title: Re: Beta started!
Post by: TommyE on July 16, 2012, 04:07:45 pm
A quick question.

Will IOS 3.x be supported at some point?

I have an old Ipod touch lying around, would be cool to use it for something.

Regards
TommyE
Title: Re: Beta started!
Post by: intveltr on July 16, 2012, 04:21:59 pm
Will IOS 3.x be supported at some point?

I'm currently looking into that.  The minimum iOS version is now 4.0, but being able to use this app on older devices is certainly an ambition.  However that does require a number of code changes.
Title: Re: Beta started!
Post by: frichter09 on July 16, 2012, 06:10:42 pm
Thanks!
Just downloaded it and will start experimenting when  I get home from work :)


BTW, whats the best way to sent you feedback? This forum or email?

Flo
Title: Re: Beta started!
Post by: jtmoore on July 16, 2012, 06:13:07 pm
Beta testing is good for me so far on Vera Lite.

One question... My device names are quite long and don't display well in HomeWave. My device names are long so that I can clearly identify them in Vera when creating scense etc. Is there a way to show a shortened version in HomeWave, perhaps denoted by some kind of delimiter in my naming device convention? For example, show only the text suffixed after the underscore _  ?

Does anyone else have comments on sensible recommendations for device naming conventions that they find useful? Thanks.

jtmoore.
Title: Re: Beta started!
Post by: Intrepid on July 16, 2012, 06:23:54 pm
Got the bet installed, it instantly found my Vera2, and I quickly set up a dimmer and a fan switch.  Very simple and works well so far. 

Once I got the hang of the slider/dimmer mechanic, I kinda like it!  Spin clockwise, the % displays and increases.  Then a tap toggles on/off to the % dim.

What does the red blink with the wifi icon mean?  That it is communicating, but not a problem?
Title: Re: Beta started!
Post by: intveltr on July 16, 2012, 07:24:50 pm
BTW, whats the best way to sent you feedback? This forum or email?

Either is fine, but I prefer this forum so that others can benefit from this feedback.

Is there a way to show a shortened version in HomeWave, perhaps denoted by some kind of delimiter in my naming device convention? For example, show only the text suffixed after the underscore _  ?.

Once you have added a control and linked it to a Vera device, you can change the name by selecting (highlighting) control, then tapping the setup button (the wrench). This brings up a screen where you can edit the control's properties, including the name. 

What does the red blink with the wifi icon mean?  That it is communicating, but not a problem?

The icon turns red when it fails to communicate with Vera, or when the connection times out.   On your LAN, the default timeout is 3 seconds which should be sufficient.  You could try to increase the timeout in the app's settings, and see if the red blinking stops.
Title: Re: Beta started!
Post by: davidd1205 on July 17, 2012, 04:45:45 am
hello
 very good job this app is fantastik
the application is very simple to use but very powerful

against by the spm103 are not considered as sensors against the sp103 work very well and the ezmotion

and it's possible to personalyze the message in the ask control ?

waiting for the camera and it will be the best application jute ios for me
a question for me would be the ultimate weapon, provides you a geolocation to start a scene at a particular location

thanks for your excellent job  :)
Title: Re: Beta started!
Post by: intveltr on July 17, 2012, 07:01:03 am
against by the spm103 are not considered as sensors against the sp103 work very well and the ezmotion
Do you mean that the SPM103 does not appear in the list of sensors in HomeWave?  What kind of sensor is this, I could not find any reference to it?

Quote
and it's possible to personalyze the message in the ask control ?
Good suggestion, I'll add it to the to-do list.

Quote
a question for me would be the ultimate weapon, provides you a geolocation to start a scene at a particular location

I'm currently looking into the options for keeping iPhone apps awake in the background to do this sort of thing. 

Thanks for the feedback!
Title: Re: Beta started!
Post by: TommyE on July 17, 2012, 07:07:10 am
Hello.

I tried it today on the road with 3g, the icon changes to a cloud, and it just works. Very nice.

One feature that could be of interest would be to have some kind of password/swipe pattern when on 3g. ( or selectable for wg/wifi)
This to have an extra barrier if you loose the phone and people open the garagedoor. (of course I would take other meassueres if I loose the phone, but it would nice to have.)

Regards
Tommy


Title: Re: Beta started!
Post by: Intrepid on July 17, 2012, 07:21:15 am

What does the red blink with the wifi icon mean?  That it is communicating, but not a problem?

The icon turns red when it fails to communicate with Vera, or when the connection times out.   On your LAN, the default timeout is 3 seconds which should be sufficient.  You could try to increase the timeout in the app's settings, and see if the red blinking stops.

I only noticed it a couple of times briefly while editing the app setup.  Haven't seen it today.  [edit]  the red wifi does seem to show when i'm making a light turn on/off quickly.  I changed the setting to 5 and will see how it goes.

I also just figured out the swipe down to get back to the main screen.  This was not obvious to me at first.

This works nicely in landscape mode and rotates the control text when the phone is rotated.  I noticed the menu bar or whatever it's called (wrench, home, wifi) stays in the same place when rotated to landscape view (bar stays on native top of phone screen). 

Very nice!  This thing is ultra-quick!
Title: Re: Beta started!
Post by: intveltr on July 17, 2012, 07:39:41 am
One feature that could be of interest would be to have some kind of password/swipe pattern when on 3g. ( or selectable for wg/wifi)
This to have an extra barrier if you loose the phone and people open the garagedoor. (of course I would take other meassueres if I loose the phone, but it would nice to have.)

Good idea, I'll add it to the list.  a PIN could be added to the whole app, or a certain screen, or to specific controls (similar to the current optional confirmation popup).  What do you think would be best?

I also just figured out the swipe down to get back to the main screen.  This was not obvious to me at first.

Any ideas to make this more obvious?  It's mentioned on the little help screen that appears the first time you run the app, but that's easy to miss I suppose.

Quote
This works nicely in landscape mode and rotates the control text when the phone is rotated.  I noticed the menu bar or whatever it's called (wrench, home, wifi) stays in the same place when rotated to landscape view (bar stays on native top of phone screen). 

That's intentional... in landscape mode, vertical screen real estate is somewhat limited so I preferred to keep the menu bar vertical and to the side.  Perhaps this can be made optional.

Thanks for the feedback!
Title: Re: Beta started!
Post by: Intrepid on July 17, 2012, 07:54:48 am
No changes needed based on my comments.  You made the right decisions and it works perfectly.  Just observations from my first use.

Great job.

Keep this thing lean and simple.  The greatest thing to me is the speed with which I can start it up and control my most-used devices.
Title: Re: Beta started!
Post by: teonebello on July 17, 2012, 08:12:47 am
VEry nice application!

Quite every things is working, but I cannot see working my door sensor (eversrping) and my windows sensor (AEON). I can just see a '--' in the status.

Thanks, waiting for camera support and PIN lock

Title: Re: Beta started!
Post by: intveltr on July 17, 2012, 08:28:06 am
Quite every things is working, but I cannot see working my door sensor (eversrping) and my windows sensor (AEON). I can just see a '--' in the status.

Alarm sensors (motion, water, smoke, doors etc) show "---" when not tripped, and "tripped" + a red ring when tripped (see attached image, and yes, I have water in my crawlspace :( ).  Perhaps "ok" would be a better default.

Note that you can change this yourself: select the control and click the spanner, then modify the "text shown when off" field.
Title: Re: Beta started!
Post by: TommyE on July 17, 2012, 09:07:38 am

Quote from: intveltr
Good idea, I'll add it to the list.  a PIN could be added to the whole app, or a certain screen, or to specific controls (similar to the current optional confirmation popup).  What do you think would be best?


At first I thought of the whole app beeing protected by a PIN, but when you mention it, I can see that all three possibilites would have different uses, and if one can wish I'd pick all three. :) If only two then app, and then specific controls. If only one then the whole app.

I also saw you mention more custom graphics for the buttons. Don't know if it would be possible to enter an URL in the app and then have the app fetch the custom graphics from the desired URL?

Regards
TommyE
Title: Re: Beta started!
Post by: davidd1205 on July 17, 2012, 09:41:27 am
against by the spm103 are not considered as sensors against the sp103 work very well and the ezmotion
Do you mean that the SPM103 does not appear in the list of sensors in HomeWave?  What kind of sensor is this, I could not find any reference to it?

Quote
and it's possible to personalyze the message in the ask control ?
Good suggestion, I'll add it to the to-do list.

Quote
a question for me would be the ultimate weapon, provides you a geolocation to start a scene at a particular location

I'm currently looking into the options for keeping iPhone apps awake in the background to do this sort of thing. 

Thanks for the feedback!

i'm confused
that's a SM103
http://www.domadoo.fr/produit,1908,1,EVERSPRING--Capteur-d-ouverture-Z-Wave-SM103.htm

my five sm103 not appear in the list of device

thanks David
Title: Re: Beta started!
Post by: teonebello on July 17, 2012, 09:49:33 am
Quite every things is working, but I cannot see working my door sensor (eversrping) and my windows sensor (AEON). I can just see a '--' in the status.

Alarm sensors (motion, water, smoke, doors etc) show "---" when not tripped, and "tripped" + a red ring when tripped (see attached image, and yes, I have water in my crawlspace :( ).  Perhaps "ok" would be a better default.

Note that you can change this yourself: select the control and click the spanner, then modify the "text shown when off" field.

I have just seen the 'Tripped' status. Zes, I believe that a green ok will be much better.

Thank you for the prompt feedback
Title: Re: Beta started!
Post by: frichter09 on July 17, 2012, 10:31:56 am
Hi!

First of all, thank you very much for this excellent app.
I have been using Automator and iVera.
Anyways, this is what I think about HomeWave so far:

The app works great over WIFI and 3G, the app seems to be running very stable. One of my biggest suggestions is about the color scheme. I know that you just released a new version to address this however I do not see any possibility to also change the background color in your app. Black is just a little bit tot dark :) Do you think you can add this feature?

Also, I have 3 door locks (actually two Kwiksets and one using the Woobsy Plugin) which are not showing up. Besides my door locks, my thermostat (CT-30) and camera do not show up in the list either.

I love the way you actually swipe the individual controls. However, when sliding from one page to another, I often activate lights, scenes, etc. by accident. I am not sure if other users agree here but it might be helpful to add two little arrows to allow swiping through the individual pages. Or maybe a bar on the buttom of the app that you can click on to get to your individual pages? Or maybe a bar users can activate if they feel they need it? As I said I am activating scenes etc. by accident when navigating through the pages - that is also true for my wife :)

I have a lot of dimmers at home and another thing I am suggesting is to always display the % of load - not only when you are actually  interacting with the app. You could also allow the user to decide what type of info each circle should display when the app is idle. (EDIT: I see this is available in the latest beta - thanks!)

Speaking of the circles, it also might be a good idea to chance the icon for scenes (or let users decide what type of icon to use). In my layout I usually have the dimmers and switches on the left side of the screen and some scenes on the right side. It would be nice if the scene icon would look slightly different so users get a better idea between the actuall physical switch, dimmer etc. and the programmed scene.... just a thought.

Anyways, thanks again for this great app and I am looking forward to testing the upcoming releases for sure. Also, if you need someone in the future  to translate this app from English to German...let me know. :)

Flo
Title: Re: Beta started!
Post by: garrettwp on July 17, 2012, 11:01:02 am
intveltr,

As another developer, I wanted to say great work!

- Garrett
Title: Re: Beta started!
Post by: knewmania on July 17, 2012, 12:42:00 pm
App looks great. I really like the flexibility in setup and configuration. Opens up a lot of possibilities.

-Is the supporting documentation in the works? I would be happy to assist if you need help with that.

-I have several Fortrezz WWA-02 water/temp sensors. Are/will these be supported? I attempted to set these up but they don't appear when selecting either Sensor Indicator or Sensor Measurement.

Thanks for the opportunity to provide feedback.
Title: Re: Beta started!
Post by: intveltr on July 17, 2012, 02:27:45 pm
One of my biggest suggestions is about the color scheme. I know that you just released a new version to address this however I do not see any possibility to also change the background color in your app. Black is just a little bit tot dark :) Do you think you can add this feature?

This is definitely planned, though it may take some time as it requires a nasty extra screen.  Currently, you can specify control colors from a set of predefined "functional" colors i.e. Yes, No, Active, Inactive, Alarm, etc.  In the future, you will be able to change those predefined colors as well.

Quote
Also, I have 3 door locks (actually two Kwiksets and one using the Woobsy Plugin) which are not showing up. Besides my door locks, my thermostat (CT-30) and camera do not show up in the list either.

Door locks & cameras are not supported yet, I'll come to that a bit further on in the pilot :)   The thermostat not showing is a surprise.  Did you check both under Thermostats and Sensor Measurements (for heat setpoint & reported ambient temperature)?

Quote
I love the way you actually swipe the individual controls. However, when sliding from one page to another, I often activate lights, scenes, etc. by accident. I am not sure if other users agree here but it might be helpful to add two little arrows to allow swiping through the individual pages.

Good to know this!  The trick is to make long swipes; if you touch a control and then move off it, the control will not react (except dimmers / thermostats).  But the title bar in Operate mode has enough room for left/right/home buttons, I can add these as an option.

Quote
Speaking of the circles, it also might be a good idea to chance the icon for scenes (or let users decide what type of icon to use). In my layout I usually have the dimmers and switches on the left side of the screen and some scenes on the right side. It would be nice if the scene icon would look slightly different so users get a better idea between the actuall physical switch, dimmer etc. and the programmed scene.... just a thought.

Anyone have a good suggestion for an icon for scene buttons, let me know! :)

Quote
Anyways, thanks again for this great app and I am looking forward to testing the upcoming releases for sure. Also, if you need someone in the future  to translate this app from English to German...let me know. :)

Thanks for the offer & feedback! :)


-Is the supporting documentation in the works? I would be happy to assist if you need help with that.

Should be forthcoming soon.

Quote
-I have several Fortrezz WWA-02 water/temp sensors. Are/will these be supported? I attempted to set these up but they don't appear when selecting either Sensor Indicator or Sensor Measurement.

I'll look into this (I might have a Fortrezz thingy lying around).  Out of curiosity, how does the Fortrezz show up?  Is it a single device, or 2 devices (each with their own Vera device ID)?
Title: Re: Beta started!
Post by: frichter09 on July 17, 2012, 03:22:04 pm
One of my biggest suggestions is about the color scheme. I know that you just released a new version to address this however I do not see any possibility to also change the background color in your app. Black is just a little bit tot dark :) Do you think you can add this feature?

This is definitely planned, though it may take some time as it requires a nasty extra screen.  Currently, you can specify control colors from a set of predefined "functional" colors i.e. Yes, No, Active, Inactive, Alarm, etc.  In the future, you will be able to change those predefined colors as well.
Thanks! I dont mind an extra screen to change the black background color, haha.

Quote
Also, I have 3 door locks (actually two Kwiksets and one using the Woobsy Plugin) which are not showing up. Besides my door locks, my thermostat (CT-30) and camera do not show up in the list either.

Door locks & cameras are not supported yet, I'll come to that a bit further on in the pilot :)   The thermostat not showing is a surprise.  Did you check both under Thermostats and Sensor Measurements (for heat setpoint & reported ambient temperature)?

Just re-checked everything. My T-stat is nowehere to be seen. Also the camera is not working but I think that this is normal at this point, right?

Quote
I love the way you actually swipe the individual controls. However, when sliding from one page to another, I often activate lights, scenes, etc. by accident. I am not sure if other users agree here but it might be helpful to add two little arrows to allow swiping through the individual pages.

Good to know this!  The trick is to make long swipes; if you touch a control and then move off it, the control will not react (except dimmers / thermostats).  But the title bar in Operate mode has enough room for left/right/home buttons, I can add these as an option.

Thanks for the tip. Its just something I might have to get used to :) Yeah, the modified title bar would be nice to have for sure.

Quote
Speaking of the circles, it also might be a good idea to chance the icon for scenes (or let users decide what type of icon to use). In my layout I usually have the dimmers and switches on the left side of the screen and some scenes on the right side. It would be nice if the scene icon would look slightly different so users get a better idea between the actuall physical switch, dimmer etc. and the programmed scene.... just a thought.

Anyone have a good suggestion for an icon for scene buttons, let me know! :)

How about not the round circle but a square around the text?

Quote
Anyways, thanks again for this great app and I am looking forward to testing the upcoming releases for sure. Also, if you need someone in the future  to translate this app from English to German...let me know. :)

Thanks for the offer & feedback! :)

Anytime!


-Is the supporting documentation in the works? I would be happy to assist if you need help with that.

Should be forthcoming soon.

Quote
-I have several Fortrezz WWA-02 water/temp sensors. Are/will these be supported? I attempted to set these up but they don't appear when selecting either Sensor Indicator or Sensor Measurement.

I'll look into this (I might have a Fortrezz thingy lying around).  Out of curiosity, how does the Fortrezz show up?  Is it a single device, or 2 devices (each with their own Vera device ID)?
[/quote]
Title: Re: Beta started!
Post by: frichter09 on July 17, 2012, 03:25:48 pm
I found another thing.

I have some scenes set up with luup code to poll my battery operated devices.

When I execute the scene I do not get any feedback wether the scene ran successfully.
The icon color changes from blue to grey. I assume it should change to white after the scene ran?
Please see attached screenshot.

Flo
Title: Re: Beta started!
Post by: intveltr on July 17, 2012, 04:13:29 pm
When I execute the scene I do not get any feedback wether the scene ran successfully.
The icon color changes from blue to grey. I assume it should change to white after the scene ran?

I noticed that in some cases, scene feedback is a bit iffy.  Not sure if it's a Vera issue or something in my code; I'll investigate. 
The ring turns white if Vera considers the scene to be "active", which usually means that all devices in the scene have been set correctly.  If you have Luup code in your scene, the "active" statue may not be quite what you'd expect (in which case, you can tell HomeWave not to show active scenes, in which case the ring will always be blue or grey).
Title: Re: Beta started!
Post by: knewmania on July 17, 2012, 04:15:36 pm
I'll look into this (I might have a Fortrezz thingy lying around).  Out of curiosity, how does the Fortrezz show up?  Is it a single device, or 2 devices (each with their own Vera device ID)?

The WWA-02 device shows up as a single device in UI5. It shows temperature and has water leak notification options. See attached.
Title: Re: Beta started!
Post by: frichter09 on July 17, 2012, 04:17:33 pm
Thanks!
I might change it to do not show active scene for now.
Flo
Title: Re: Beta started!
Post by: TommyE on July 18, 2012, 06:47:56 am
An idea for the coming camera support.

I have a camera in my garage, and I also have a trigger on the garagedoor so that I can see whether it is open or closed.

What could be nice is to have the sensor information overlap the picture from the camera, or maybe just draw a red or green border around the camerapicture to
show whether the garagedoor sensor is triggered or not.

Also, if you want a Norwegian translation at some point I'm ready.

Regards
TommyE
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 08:01:53 am
New build has been posted.  Please let me know if the following devices now work:
- Fortress WWA02 temp/water sensor: both leak detector and temp reading should work, but you'll need to add two controls to get both.
- CT30 Thermostat (and others): Only supports heat setpoint and current temperature as yet.
- Door sensors (Everspring SM103)

Scene status has been modified slightly: the scene control will go from grey (unknown) to blue or white on <i>any</i> message from Vera about this scene.  Effectively, this means you will get confirmation that Vera received your request to run the scene, not that it actually ran to completion.

The default caption for untripped alarm sensors is now "ok".  This only applies to newly added controls; your existing controls will not be changed.
Title: Re: Beta started!
Post by: Intrepid on July 18, 2012, 08:21:00 am
Great work. 

I've only tested dimmers, switches (physical and binary), and scenes so far.

Regarding the control icons, basically I see blue when off and white when on.

1. switches seem to work intuitively; blue=off, white=on.

2. Scenes toggle between blue and white.  I have an "all inside lights off' scene.  First run, icon goes blue, next run, icon goes white.  The color toggle for a scene does not tell me anything.  Maybe scenes should not toggle their color?

3.  Dimmers keep a 3/4 blue circle all the time.  The left 1/4 is either white for the  partial dim %, or black/blank for the undimmed %.  And seeing the blue ring on the other 3/4 looks like the dimmer is off at a glance.   I don't have an answer, but this piece of UI seems a little confusing.







 
Title: Re: Beta started!
Post by: davidd1205 on July 18, 2012, 08:25:54 am
New build has been posted.  Please let me know if the following devices now work:
- Fortress WWA02 temp/water sensor: both leak detector and temp reading should work, but you'll need to add two controls to get both.
- CT30 Thermostat (and others): Only supports heat setpoint and current temperature as yet.
- Door sensors (Everspring SM103)

Scene status has been modified slightly: the scene control will go from grey (unknown) to blue or white on <i>any</i> message from Vera about this scene.  Effectively, this means you will get confirmation that Vera received your request to run the scene, not that it actually ran to completion.

The default caption for untripped alarm sensors is now "ok".  This only applies to newly added controls; your existing controls will not be changed.

yes i 'have installed and my sm103 works very well
tjhank you

i have a bug sometimes with enter the text on the off label but impossible
my solution enter in the case of the on label and after in the case of the off
Title: Re: Beta started!
Post by: teonebello on July 18, 2012, 08:27:54 am
The version #5 is working correctly.

I didn't understood the support for door sensor. It was not already included with the Status Sensor?

Question: for the door/sensor is possible to see if they are tripped or not. How can I arm and bypass and check the status? Maybe clicking on it?

Thanks
Matteo
Title: Re: Beta started!
Post by: knewmania on July 18, 2012, 08:43:39 am
New build has been posted.  Please let me know if the following devices now work:
- Fortress WWA02 temp/water sensor: both leak detector and temp reading should work, but you'll need to add two controls to get both.

I still don't see either of my WWA-02 devices when using either the Sensor Indicator or Sensor Measurement control.
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 09:04:37 am
2. Scenes toggle between blue and white.  I have an "all inside lights off' scene.  First run, icon goes blue, next run, icon goes white.  The color toggle for a scene does not tell me anything.  Maybe scenes should not toggle their color?

Scenes are white when Vera reports them as "active", which usually means that all devices are set as ordered.  This can be disabled in cases where the "active" state doesn't make much sense: go into the scene's settings and turn "Show Scene State" off.

Quote
3.  Dimmers keep a 3/4 blue circle all the time.  The left 1/4 is either white for the  partial dim %, or black/blank for the undimmed %.  And seeing the blue ring on the other 3/4 looks like the dimmer is off at a glance.   I don't have an answer, but this piece of UI seems a little confusing.

That dimmer gadget works best on large dimmer controls.  You can turn it off: go into the dimmer's settings, and turn "Light level bar" off, then enable "Light level text" if you want to see the power % instead.
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 09:06:35 am
yes i 'have installed and my sm103 works very well
tjhank you

i have a bug sometimes with enter the text on the off label but impossible
my solution enter in the case of the on label and after in the case of the off

Good to hear about the SM103.  I noticed the bug with the Off text field as well, will look into it!
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 09:10:58 am
I didn't understood the support for door sensor. It was not already included with the Status Sensor?

The status sensor supported it, but the filter for the list of devices you can link to it did not include the DoorSensor device type, so these devices weren't selectable.  A simple configuration file change did the trick.

Quote
Question: for the door/sensor is possible to see if they are tripped or not. How can I arm and bypass and check the status? Maybe clicking on it?

Arm/Bypass is not supported yet.  (will add to the list)
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 09:20:40 am
I still don't see either of my WWA-02 devices when using either the Sensor Indicator or Sensor Measurement control.

Strange.  Could you go into the Vera GUI please, and do the following:
1) open the settings for one of the WWA-02 devices.
2) go to the Advanced tab
3) copy the value next to device_type and paste it here.

Thanks!
Title: Re: Beta started!
Post by: knewmania on July 18, 2012, 09:45:37 am
Strange.  Could you go into the Vera GUI please, and do the following:
1) open the settings for one of the WWA-02 devices.
2) go to the Advanced tab
3) copy the value next to device_type and paste it here.

As requested:

urn:schemas-micasaverde-com:device:TempLeakSensor:1
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 10:02:38 am
urn:schemas-micasaverde-com:device:TempLeakSensor:1

Right... the Wiki specifies urn:schemas-micasaverde-com:device:TemperatureLeakSensor:1, which is why the app doesn't pick it up.  Hopefully it will be fixed in the next build.

Title: Re: Beta started!
Post by: Dolphran on July 18, 2012, 10:55:01 am
Just got the beta running.  My first thought is that plugin support will be a key factor for me. Support for the 3M-50 Thermostat plugin, and the DSC Alarm panel plugin would be great.   Most importantly though, I think it needs support for the Virtual Switch plugin.  This would allow an access point to other unsupported plugins via setups on the Vera.  Is this planned?
Title: Re: Beta started!
Post by: frichter09 on July 18, 2012, 11:28:31 am
Gooood morning.
Thanks for the new build.
I can add my CT-30 Thermostat now, however I do not get any info on it.

See attached screenshot.
Any thoughts?

Flo
Title: Re: Beta started!
Post by: Intrepid on July 18, 2012, 03:01:27 pm

Quote
3.  Dimmers keep a 3/4 blue circle all the time.  The left 1/4 is either white for the  partial dim %, or black/blank for the undimmed %.  And seeing the blue ring on the other 3/4 looks like the dimmer is off at a glance.   I don't have an answer, but this piece of UI seems a little confusing.

That dimmer gadget works best on large dimmer controls.  You can turn it off: go into the dimmer's settings, and turn "Light level bar" off, then enable "Light level text" if you want to see the power % instead.

Ahh, I like that better.  Thanks.
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 06:51:15 pm
Just got the beta running.  My first thought is that plugin support will be a key factor for me. Support for the 3M-50 Thermostat plugin, and the DSC Alarm panel plugin would be great.   Most importantly though, I think it needs support for the Virtual Switch plugin.  This would allow an access point to other unsupported plugins via setups on the Vera.  Is this planned?

Did you try virtual switches?  I have several though I added them manually rather than install the plugin, but the end result should be the same.  Vera presents these as real devices, and they should show up as any other swith in HomeWave.

For any plugin: if it defines the same uPnP interface as regular Vera devices, HomeWave won't know the difference.  I am planning support for devices that fall outside the regular Vera definitions (by allowing you to add custom definitions); the supporting framework is there in the software, but there's no GUI for it yet. 
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 06:56:20 pm
Gooood morning.
Thanks for the new build.
I can add my CT-30 Thermostat now, however I do not get any info on it.

Not sure why that is... perhaos there's a slight difference between the data structure of device:HVAC_ZoneThermostat:1 and device:Heater:1 (the latter is what I have).  Both are defined in the uPnP standard so I can look it up even without having access to an actual thermostat like yours.  If that doesn't give me a clue, I'll add a simple debugging window to the app to log what is going on, so you can send me those details.

By the way, did you try getting the temperature measurement from the thermostat (using a "Sensor measurement" control)?

That reminds me... I need to add a Fahrenheit readout to this thing :)
Title: Re: Beta started!
Post by: frichter09 on July 18, 2012, 07:08:08 pm
Yeah, i tried everything and I am not able at getting a temperature measurement.
Let me know if and how I can sent you any log files if needed.

Flo
Title: Re: Beta started!
Post by: jtmoore on July 18, 2012, 07:21:08 pm
Looking good so far with tstat, temp, humidity, and door sensors. Arm/disarm would be useful addition.
1). Plugins for virtual switch and conditional switch (from mios Apps) don't show up. I would love to see support for those please.
2). Swiping left and right is difficult without accidentally moving the dimmer settings. Any way to improve this?
3). On the Control Screen, can I only have 6 panels? I'm using one per room and I need more than 6 rooms. Perhaps I am not using it correctly.
4). Would also be good if I could display the text from the Variable Container plugin too.

Many thanks.

Jtmoore
Title: Beta started!
Post by: Dolphran on July 18, 2012, 07:43:06 pm

Did you try virtual switches?  I have several though I added them manually rather than install the plugin, but the end result should be the same.

Mine definitely don't show up.  What do you mean to add them manually?
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 08:04:43 pm
Mine definitely don't show up.  What do you mean to add them manually?
My virtual switch didn't come as a plugin from the MIOS store, but as a couple of files someone posted here some time ago.  I uploaded these files to my Vera to create the switch.

I will try adding a virtual switch and some of the other plugins, and check how Vera exposes them on her web interface.
Title: Re: Beta started!
Post by: intveltr on July 18, 2012, 08:12:21 pm
1). Plugins for virtual switch and conditional switch (from mios Apps) don't show up. I would love to see support for those please.
2). Swiping left and right is difficult without accidentally moving the dimmer settings. Any way to improve this?
3). On the Control Screen, can I only have 6 panels? I'm using one per room and I need more than 6 rooms. Perhaps I am not using it correctly.
4). Would also be good if I could display the text from the Variable Container plugin too.

1, 4) I will look into supporting specific or even arbitrary plugins.
2) Not easily.  It is possible to make the app cancel a dimmer move once you leave the dimmer control with your finger, but it will be annoying to have the dimmer snap back to the old value if that happens, rather than stay on the last valid value.  I could also cancel the dimmer action once a swipe is detected.  I'll experiment a bit with these options.
3) Select (highlight) one or more panels by tap-and-dragging, then hit the Grid button.  You can then change the nr of panels on the selected area, allowing you to have more than 6 controls. For example, select 2x2 panels, then tap the grid button and change it to 3x3. You end up with 9 smaller controls instead of the original 4
Title: Re: Beta started!
Post by: frichter09 on July 19, 2012, 12:50:32 pm
For this one:
2) Not easily.  It is possible to make the app cancel a dimmer move once you leave the dimmer control with your finger, but it will be annoying to have the dimmer snap back to the old value if that happens, rather than stay on the last valid value.  I could also cancel the dimmer action once a swipe is detected.  I'll experiment a bit with these options.

maybe implement arrows on the top bar to switch between different screen.

Flo
Title: Re: Beta started!
Post by: jtmoore on July 19, 2012, 04:05:37 pm
Regarding my reported difficulty swiping left and right without accidentally altering the dimming setting... As a personal work round, I could just learn to position my finger to start the swipe inside the dimmer icon, rather on its edge. So, I can live with this limitation if there is no easy solution. I just need to teach my wife to do the same....

I've been testing via 3G connection and I can report that this works ok. I've increased the time out a little, as some times it would not respond.

I really like the Sensor icon and configuration, with ability to change the text and colour depending on current state.  I have some binary switches (real and virtual) that I would like to use as though they were Sensors.  Would it be possible if HomeWave could have option to display the switch as a sensor?  Anyone else think this could be useful option, or just me?  ;-)   Thanks.

jtmoore.
Title: Re: Beta started!
Post by: frichter09 on July 19, 2012, 04:17:09 pm
For me if I start swiping inside the dimmer switch I get the problem that sometimes the dimmer gets turned on...
So I d still prefer some type of arrows etc. Maybe user configurable so people can turn it off if not needed.

Anyways +1 on fading color option. I really enjoy this feature!!!

Flo 
Title: Re: Beta started!
Post by: intveltr on July 19, 2012, 04:18:26 pm
I really like the Sensor icon and configuration, with ability to change the text and colour depending on current state.  I have some binary switches (real and virtual) that I would like to use as though they were Sensors.  Would it be possible if HomeWave could have option to display the switch as a sensor?  Anyone else think this could be useful option, or just me?  ;-)   Thanks.

You can configure the switch to look exactly the same :)  Just set the on/off colors and labels, and disable the ring for the off state.  Then (if desired) disable user interaction so it's display only.
Title: Re: Beta started!
Post by: jtmoore on July 19, 2012, 04:32:24 pm
You can configure the switch to look exactly the same :)  Just set the on/off colors and labels, and disable the ring for the off state.  Then (if desired) disable user interaction so it's display only.

Perfect! Many thanks.
Title: Re: Beta started!
Post by: intveltr on July 19, 2012, 05:59:16 pm
New build has been posted, mainly having to do with Thermostats and Plugins.

Please note: If you have any Thermostat or Linear Sensor controls configured in Homewave, please go into edit mode, select the control, click the Link button (the little chain) and re-link the control to the right Vera device.  This ensures that the new configuration settings of this build are carried over to your existing control. 

Please also do the same for any Fortrezz temp / water sensor (both the temperature readout and the water indicator), and let me know if the device still works as expected.

This build should now support regular thermostats as well as the 3M-50 plugin, but keep in mind that only heat setpoint and ambient temperature are supported as yet.

You can also switch to Fahrenheit readout.  After making the change in the app settings, you'll have to return to the HomeWave home screen for the changes to take effect.
Title: Re: Beta started!
Post by: frichter09 on July 19, 2012, 06:08:08 pm
Thanks intveltr,

it seems to recognize my ct-30 now... however it shows 70C. This cant be right (I hope)....
How do I switch it to F?

Flo
Title: Re: Beta started!
Post by: frichter09 on July 19, 2012, 06:13:48 pm
Also, my Evolve relay switch is now showing up!
Great work.
Title: Re: Beta started!
Post by: knewmania on July 19, 2012, 06:17:59 pm
My WWA-02 devices now appear as well as my Virtual Switch.

Title: Re: Beta started!
Post by: intveltr on July 19, 2012, 06:25:09 pm
it seems to recognize my ct-30 now... however it shows 70C. This cant be right (I hope)....
How do I switch it to F?

That'll be 70F :)  The only thing that actually changes is the unit label. 

Go into the app's Preferences (via your iPhones Settings thingy); you'll find a setting for the temperature unit.
Title: Re: Beta started!
Post by: frichter09 on July 19, 2012, 06:27:19 pm
it seems to recognize my ct-30 now... however it shows 70C. This cant be right (I hope)....
How do I switch it to F?

That'll be 70F :)  The only thing that actually changes is the unit label. 

Go into the app's Preferences (via your iPhones Settings thingy); you'll find a setting for the temperature unit.

Haha...
that makes more sense:)
For a moment I was like: wait..what??? :)

Thanks!
Title: Re: Beta started!
Post by: frichter09 on July 19, 2012, 06:34:47 pm
So the thermostat displays the set point for heating right?
Is there any way how I can toggle between the heating and cooling setpoint?

Title: Re: Beta started!
Post by: intveltr on July 19, 2012, 06:41:25 pm
So the thermostat displays the set point for heating right?
Is there any way how I can toggle between the heating and cooling setpoint?

Not yet.  I hope to fix that in the next build, but it requires some GUI work which is always a bit of extra work.
Title: Re: Beta started!
Post by: frichter09 on July 19, 2012, 06:44:26 pm
So the thermostat displays the set point for heating right?
Is there any way how I can toggle between the heating and cooling setpoint?

Not yet.  I hope to fix that in the next build, but it requires some GUI work which is always a bit of extra work.

NP, thanks for the quick replies!
Title: Re: Beta started!
Post by: Intrepid on July 20, 2012, 07:42:07 am
I had to reflash my vera and am taking the opportunity to start over, adding devices as new and recreating scenes.  Now the app does not see the vera, and shows an emply list to select for devices and scenes.  I checked the app settings, and it shows the correct LAN IP and vera unit#.  I do not have the MIOS login set in the app.

My vera is working fine on my LAN and via MIOS.

Is it not refreshing something properly?

Title: Re: Beta started!
Post by: intveltr on July 20, 2012, 08:01:06 am
I had to reflash my vera and am taking the opportunity to start over, adding devices as new and recreating scenes.  Now the app does not see the vera, and shows an emply list to select for devices and scenes.  I checked the app settings, and it shows the correct LAN IP and vera unit#.  I do not have the MIOS login set in the app.

Is HomeWave connecting to your Vera (showing a white WiFi icon in the top right corner, not a red one)?
Did you try the Refresh button when the (empty) list of devices comes up?

Two other things you could try:
- Kill the app (double click the phone's Home button, tap-and-hold HomeWave, and stop it), and restart Homewave.
- Go into the app's settings and clear the device ID and IP address.  Kill the app, and restart.    Check if HomeWave finds your iPhone on the LAN.
Title: Re: Beta started!
Post by: Intrepid on July 21, 2012, 10:07:06 am
I had to reflash my vera and am taking the opportunity to start over, adding devices as new and recreating scenes.  Now the app does not see the vera, and shows an emply list to select for devices and scenes.  I checked the app settings, and it shows the correct LAN IP and vera unit#.  I do not have the MIOS login set in the app.

Is HomeWave connecting to your Vera (showing a white WiFi icon in the top right corner, not a red one)?
Did you try the Refresh button when the (empty) list of devices comes up?

Two other things you could try:
- Kill the app (double click the phone's Home button, tap-and-hold HomeWave, and stop it), and restart Homewave.
- Go into the app's settings and clear the device ID and IP address.  Kill the app, and restart.    Check if HomeWave finds your iPhone on the LAN.

Backstory, my rebuild is a result of my schalge battery replacement and my poking around trying to get the lock re-recognized.  Somehow I lost z-wave communication.  So I reset and restarted (Vera 2, UI4, 1362).  After excluding and including most of my devices, I'm back up and running.  mios.com works, automator app works.

Back to homewave, I cleared the device settings and restarted the app.  it found vera, and the wifi icon is white.  However, when I try to add a scene or a dimmer, the 'select' list is empty. 

I uninstalled/reinstalled homewave, and I still cannot see any devices or scenes.  Refresh in the 'select vera device' does not help.  The unit is found and the wifi icon is white.
Title: Re: Beta started!
Post by: intveltr on July 21, 2012, 12:34:44 pm
Is that the same UI version as before?

Another thing you could try is to fill in your MIOS details and remove the ip address, or disable wifi, then try again via MIOS.

When you refresh the list, do you get the spinny thing, and does it keep spinning or does it disappear quickly?
Title: Re: Beta started!
Post by: Intrepid on July 21, 2012, 12:54:55 pm
Is that the same UI version as before?

no, newer version. 

Quote
Another thing you could try is to fill in your MIOS details and remove the ip address, or disable wifi, then try again via MIOS.

When you refresh the list, do you get the spinny thing, and does it keep spinning or does it disappear quickly?

I entered my mios login.  same result.  turned off iPhone wifi, same result.  The spinner stays on the screen about 1/4 second.

I'm sure this is due to my rebuild.  I wouldn't suspect the home wave app if automator and cp.mios.com weren't working, but they are.



Title: Re: Beta started!
Post by: Minnies on July 21, 2012, 12:58:05 pm
Not able to get temps to change to F. I changed it in the setup. Turned off HomeWave and went back to the main screen. What am I doing wrong.

PS any timetabe for adding energy monitors?
Title: Re: Beta started!
Post by: jtmoore on July 21, 2012, 03:12:32 pm
PS any timetabe for adding energy monitors?

+1 on the energy monitors. Thanks.
Title: Re: Beta started!
Post by: intveltr on July 21, 2012, 03:43:03 pm
Not able to get temps to change to F. I changed it in the setup. Turned off HomeWave and went back to the main screen. What am I doing wrong.

PS any timetabe for adding energy monitors?

After the last update, something changed in the thermostat related controls so they need to be re-configured.  You can do this by going to edit mode, selecting the thermostat control, and clicking the Link button (the little chain).  Pick the same Z-wave thermostat from the list and click save, that should fix it.  If not, delete it completely and re-add.  (This is just because of the patch that added fahrenheit, and needs to be done only once for controls added before this patch).

As for energy monitors, what do these things looke like (in the Vera interface)?  I don't have one and I'm not sure what they look like. :)
Title: Re: Beta started!
Post by: jtmoore on July 21, 2012, 03:56:18 pm
Regarding energy monitors, I have an Everspring AN158 and an Aeon Micro Energy Switch. Both appear in Vera as D_BinaryLight1.xml and I think MCV have built in the capabilities to display the Watts.  I don't (yet) have any clamp type units that monitor energy.

When playing around with lua code, the values from my switches are queried with the following example. I'm not sure what code would be used to get total KWh consumption etc.:
Code: [Select]
local watts    = luup.variable_get("urn:micasaverde-com:serviceId:EnergyMetering1", "Watts", measuredevice)

Hope that helps.
jtmoore.
Title: Re: Beta started!
Post by: Minnies on July 21, 2012, 05:10:17 pm
I have the Aeon HEM. In UI it looks like a motion sensor except the figure is replaced with a lightening bolt. It shows the current wattage and KWH. It also shows clamp 1 and clamp 2, but they are not very important.

In addition to the data point "watts" indicated above the KWH is in "KWH"
Title: Re: Beta started!
Post by: intveltr on July 21, 2012, 06:26:03 pm
I entered my mios login.  same result.  turned off iPhone wifi, same result.  The spinner stays on the screen about 1/4 second.

I'm sure this is due to my rebuild.  I wouldn't suspect the home wave app if automator and cp.mios.com weren't working, but they are.

Thanks for mailing your JSON dump.  I noticed you have no rooms set up on your Vera, and that is indeed what bugged HomeWave.  The next build will fix this, in the mean time you can just add a room to continue working with the app :)
Title: Re: Beta started!
Post by: frichter09 on July 21, 2012, 07:27:31 pm
Inveltr,

Am I supposed to turn on and off the thermostat?
If I click on the item nothing happens.
Not sure if that is supposed to behave like this....

Flo
Title: Re: Beta started!
Post by: intveltr on July 22, 2012, 05:29:06 am
Turning the thermostat on/off is not supported yet.  Thermostat and fan mode will come as separate controls.
Title: Re: Beta started!
Post by: Intrepid on July 22, 2012, 08:04:00 am
I entered my mios login.  same result.  turned off iPhone wifi, same result.  The spinner stays on the screen about 1/4 second.

I'm sure this is due to my rebuild.  I wouldn't suspect the home wave app if automator and cp.mios.com weren't working, but they are.

Thanks for mailing your JSON dump.  I noticed you have no rooms set up on your Vera, and that is indeed what bugged HomeWave.  The next build will fix this, in the mean time you can just add a room to continue working with the app :)

Ahhh, correct, I have not setup any rooms.  Glad we caught this, as I'm probably an oddball with no rooms on a new build.

edit:  I added a room without moving anything into it and the app works.
Title: Re: Beta started!
Post by: frichter09 on July 23, 2012, 06:40:31 pm
Thanks for the new build!
My D-Link wifi camera is working perfectly.
What is the refresh interval on the cam?

Also, thanks for putting the arrows in the top bar, navigating is much easier now!

If only my locks were supported  ;)

When are you planing to release this version?
Title: Re: Beta started!
Post by: intveltr on July 23, 2012, 07:26:56 pm
The cam thumbnails refresh once every minute; this interval can be changed in the app settings.  The fullscreen view refreshes continuously.

The plan is to submit Homewave to the app store at the end of August, but the way things are going, I think I will bring that date forward.  The next few builds will wrap up camera support, support for locks, and full support for thermostats.  After that it's mostly polishing and localization.
Title: Re: Beta started!
Post by: Minnies on July 23, 2012, 07:42:44 pm
+1 on the arrows.

Still not able to change from C to F. Do I need a thermostat or someting installed?
Title: Re: Beta started!
Post by: intveltr on July 23, 2012, 07:47:57 pm
Still not able to change from C to F. Do I need a thermostat or someting installed?

Which devices for displaying and/or setting temperatures have you currently added to HomeWave?  And have you tried re-linking these controls to their corresponding devices in Vera, or tried to delete them and add them again?
Title: Re: Beta started!
Post by: Minnies on July 23, 2012, 08:00:56 pm
Relinking did not work. deleting and reinstalling does work. I have a bunch from 3 way sensors to pool temp sensors to Google. Thanks!
Title: Re: Beta started!
Post by: frichter09 on July 23, 2012, 09:23:04 pm
The cam thumbnails refresh once every minute; this interval can be changed in the app settings.  The fullscreen view refreshes continuously.

The plan is to submit Homewave to the app store at the end of August, but the way things are going, I think I will bring that date forward.  The next few builds will wrap up camera support, support for locks, and full support for thermostats.  After that it's mostly polishing and localization.

I should really start checking the app settings with each new build :)
Concerning your timeline, I agree that this might be pushed forward giving how well things are moving....
Flo
Title: Re: Beta started!
Post by: knewmania on July 24, 2012, 11:03:27 am
All 4 of my Foscam camera's are working with the update. Very nice.

Under the Applications Setting, what does the 'Keep iPhone on' feature do?
Title: Re: Beta started!
Post by: intveltr on July 24, 2012, 11:33:12 am
Under the Applications Setting, what does the 'Keep iPhone on' feature do?

If you enable that, your iPhone will never go to sleep while the app is running.  It's meant for wall-mounted iDevices being used as permanent control panels.
Title: Re: Beta started!
Post by: intveltr on July 24, 2012, 05:46:50 pm
Small detail to keep in mind: the app currently assumes that Vera has a fixed IP address.  In normal installations this will often not be the case.  The next build will verify the IP address on every startup.  In the mean time, if the app does not connect to your Vera (or uses MIOS even when on the LAN), then clear the IP address in the settings, and restart the app.
Title: Re: Beta started!
Post by: intveltr on July 27, 2012, 01:34:13 pm
A new build has been sent out!   This one adds support for camera panning, as well as support for thermostat cooling setpoint, fan modes etc.

Please test the thermostat stuff thoroughly :)  I don't have a full feature thermostat to try this on.

A few notes on adding the new thermostat controls:
Title: Re: Beta started!
Post by: knewmania on July 27, 2012, 02:19:13 pm
The horizontal panning for my Foscam camera's are reversed using the App. Right moves the camera left, etc. The vertical movement is correct.
Title: Re: Beta started!
Post by: intveltr on July 28, 2012, 06:18:03 am
The horizontal panning for my Foscam camera's are reversed using the App. Right moves the camera left, etc. The vertical movement is correct.

Is anyone else experiencing the same?  My camera works correctly; it's on the foscam plugin but the cam itself is some weird Chinese knockoff. Maybe they got their wires crossed (literally).
Title: Re: Beta started!
Post by: Intrepid on July 29, 2012, 07:16:01 am
The thermostat 'set setpoint' control shows the wrong temp on my Trane.  Left to right on the pic are temperature, fan control, setpoint.  The temp icon is correct 75, the set point temp 55 is incorrect.

Regarding the pulldown swipe to get to main screen, about half the time I end up pulling down the IOS notifications screen instead of the app's navigation to the main screen.  Is it just me or anyone else get this too?
Title: Re: Beta started!
Post by: intveltr on July 29, 2012, 12:41:34 pm
Re. The thermostat set point: did you try deleting and then re-adding the control?  (needs to be done only during the beta when a control undergoes fundamental changes)
Also:
- what happens when you change the temperature on the thermostat, or in Vera's UI; does the control change?
- does the thermostat or Vera's UI change when you change the control? (the thermostat might take a few minutes to change)

Re. The swiping: the solution is to start the swipe a bit lower.  The swiping stuff in general is still a bit troublesome, but I'm not sure how to improve it.
Title: Re: Beta started!
Post by: intveltr on July 29, 2012, 04:10:11 pm
New build posted:
- App now uses Vera discovery process.  Vera's IP will be updated automatically if it changes.
- Default screen timer added: when specified (in the app's Settings), the app will switch back to the default screen after the specified amount of time has passed without any activity.
- Lock support for opening and closing (experimental).  Locks should currently appear as on/off switches.
Title: Re: Beta started!
Post by: Intrepid on July 29, 2012, 05:11:11 pm
Re. The thermostat set point: did you try deleting and then re-adding the control?  (needs to be done only during the beta when a control undergoes fundamental changes)
Also:
- what happens when you change the temperature on the thermostat, or in Vera's UI; does the control change?
- does the thermostat or Vera's UI change when you change the control? (the thermostat might take a few minutes to change)

Re. The swiping: the solution is to start the swipe a bit lower.  The swiping stuff in general is still a bit troublesome, but I'm not sure how to improve it.

On the thermostat:

The app shows the thermostat accurately, 76F right now.  The setpoint control shows 55F.

If I adjust the setpoint via the web UI, the app setpoint does not change.  If I adjust the setpoint on the app, the web UI does not change.

I just downloaded the new app, deleted the set point control and re-added.  let me know what else I can try.

Title: Re: Beta started!
Post by: intveltr on July 29, 2012, 05:40:57 pm
If I adjust the setpoint via the web UI, the app setpoint does not change.  If I adjust the setpoint on the app, the web UI does not change.

Have you tried adjusting the setpoint in the App, then checking the actual thermostat 5-15 minutes later (and perhaps checking the UI to see if Vera tries to transmit something to the thermostat)? 

Can you go into your thermostats settings in the Vera UI, and check a few things on the Advanced tab please:
- device_type
- device_file

Do other apps control the thermostat correctly?  The app uses the standard uPnP variables for the thermostat, and those work well with both the virtual thermostat device and the RTCOA (WiFi thermostat) plug-in.
Title: Re: Beta started!
Post by: frichter09 on July 29, 2012, 07:25:28 pm
If I change the setpoint from within the app it is correctly reflected on the actual thermostat.
I had it once where the thermostat was not reacting but after 1-2 min it was fine...
Title: Re: Beta started!
Post by: Minnies on July 29, 2012, 08:52:53 pm
New build posted:- Lock support for opening and closing (experimental).  Locks should currently appear as on/off switches.

Not sure I understand the lock switch function. It does indeed send a signal to lock or unlock the lock. But the status does not reflect the lock status. It seems to toggle with the lock / unlock command, but not reflect the actial status (sending an unlock command to a Schlage does not unlock the lock, it only allows a person present to manually turn the lock).
Title: Re: Beta started!
Post by: intveltr on July 30, 2012, 05:11:22 am
How does the lock control appear in Vera's UI?  Does it show if the lock is "enabled", i.e. the lock will allow someone to manually turn the knob to retract the bolt, or does it show if the bolt is actually retracted, or both?

Sadly I have no locks to test with, so I don't even know how these devices are supposed to behave exactly

Can you actually unlock the door using the app?  I found that the app is using an incorrect Service URL when sending the lock/unlock commands, at least for Kwikset locks.
Title: Re: Beta started!
Post by: Intrepid on July 30, 2012, 07:02:00 am
If I adjust the setpoint via the web UI, the app setpoint does not change.  If I adjust the setpoint on the app, the web UI does not change.

Have you tried adjusting the setpoint in the App, then checking the actual thermostat 5-15 minutes later (and perhaps checking the UI to see if Vera tries to transmit something to the thermostat)? 

Can you go into your thermostats settings in the Vera UI, and check a few things on the Advanced tab please:
- device_type
- device_file

Do other apps control the thermostat correctly?  The app uses the standard uPnP variables for the thermostat, and those work well with both the virtual thermostat device and the RTCOA (WiFi thermostat) plug-in.

device type
urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1

device file
D_HVAC_ZoneThermostat1.xml

automator app works correctly.

Title: Re: Beta started!
Post by: knewmania on July 30, 2012, 12:00:47 pm
New build posted:
- App now uses Vera discovery process.  Vera's IP will be updated automatically if it changes.
- Default screen timer added: when specified (in the app's Settings), the app will switch back to the default screen after the specified amount of time has passed without any activity.
- Lock support for opening and closing (experimental).  Locks should currently appear as on/off switches.

My Foscam camera issue (reversed horizontal controls) seems to be fixed. Did you make a change to resolve that or was the problem mine?

I am able to add my Kwikset locks, and the correct status is displayed. Trying to unlock the lock does not work. I attempt to unlock the lock and the status in the app will change to unlocked (or locked), but the actual lock status doesn't change (the lock doesn't lock or unlock). When I do this process with UI5 open, I can see that some command is sent to the lock.
Title: Re: Beta started!
Post by: Minnies on July 30, 2012, 12:28:37 pm
How does the lock control appear in Vera's UI?  Does it show if the lock is "enabled", i.e. the lock will allow someone to manually turn the knob to retract the bolt, or does it show if the bolt is actually retracted, or both?

Sadly I have no locks to test with, so I don't even know how these devices are supposed to behave exactly

Can you actually unlock the door using the app?  I found that the app is using an incorrect Service URL when sending the lock/unlock commands, at least for Kwikset locks.

The lock control show a padlock and indicates if it is closed(locked) or open (unlocked). It relects the status of the deadbolt. The UI is similar to a door sensor except it has a lock/unlock button. When the deadbolt is operated manually the status in Homewave does update. However it is not in synch all of the time.
Title: Re: Beta started!
Post by: intveltr on July 30, 2012, 03:58:45 pm
The thermostat 'set setpoint' control shows the wrong temp on my Trane.  Left to right on the pic are temperature, fan control, setpoint.  The temp icon is correct 75, the set point temp 55 is incorrect.

I'm somewhat stumped by this one.   A possible explanation is this: judging from a picture of the Trane thermostat, there is only a single set of up/down buttons for the temperature; the heating and cooling temp are not set by separate buttons.  However, the thermostat does keep separate heating/cooling setpoints internally.

Judging from the Vera config file you sent me earlier, I can see a cooling setpoint in the 70s, heating at 55 (as displayed in the app), and the thermostat in cooling mode.  This could mean that messing with the heating setpoint in the app will not show any change in the thermostat (since it is displaying the cooling setpoint).  Vice versa the same: the thermostat updates the cooling setpoint when you change it, while the app shows the heating setpoint (and doesnt change as a result).  I hope that makes sense...

Can you try the following:
1) Set your thermostat to Heat mode, and change the temperature in the app, as well as in the thermostat itself.
2) Set your thermostat to Cooling mode again, and change the control in the app to control the Cooling setpoint (edit mode, select the thermostat control, click the spanner, click on the blue button next to the "Controlling..." caption.  Then choose Cooling setpoint.  (The displayed setpoint might not change until you touch the thermostat)

In both cases you will hopefully find that the app responds to your thermostat and the other way around.

If so, it might mean that I'll have to add a third option for the thermostat spinner control: one that controls the setpoint according to the heat/cool mode of the thermostat.
Title: Re: Beta started!
Post by: intveltr on July 30, 2012, 03:59:41 pm
My Foscam camera issue (reversed horizontal controls) seems to be fixed. Did you make a change to resolve that or was the problem mine?

I did.  Code-wise it made more sense to reverse the actions, and I am trusting your Foscam more than my own knockoff :)
Title: Re: Beta started!
Post by: intveltr on July 31, 2012, 07:27:22 pm
New build posted:
- Added a lock control that uses the correct Service IDs for locks.  If you previously added your locks as on/off switches, please delete them from HomeWave and re-add them; you'll find a separate control type for them.  Try if the control now correctly opens/closes the lock.
- Added an option for thermostats to control heat/cool setpoint from a single spinner control.  If you wish to try this option, please delete and re-add your thermostat control.  Combined heat/cool setpoint control is the default.

Regarding the new thermostat control: you can now opt to control:
- Temperature (default): this controls the heat setpoint when your thermostat is in heating mode, and the cool setpoint when in cooling mode.  In Auto mode it controls both (not sure that is right, though).
- Heating Temperature: this setting always controls the heating setpoint, regardless of the thermostat setting
- Cooling temperature: the same, but for cooling.

The new "combined" control is available for thermostats, but not for the 3M-50 thermostat plugin.

Please note: Your Vera UI will most likely not reflect any changes in temperature setpoint, until Vera manages to actually transmit the new setpoint to the thermostat.  This can take up to several minutes.  Changes made on your thermostat should be visible in HomeWave as soon as they appear in the Vera UI.
Title: Re: Beta started!
Post by: frichter09 on July 31, 2012, 09:17:27 pm
Hi inveltr,

The new version does not work for me.
The Kwikset locks still show the same behavior as before. If you click on it within the app, the status changes, however the door lock does not do anything. This is also true for my Garage door opener which is in fact a evolve relay hooked up to my opener.
Also, the thermostat (CT30) stays at 0F.  ::)

Flo
Title: Re: Beta started!
Post by: intveltr on August 01, 2012, 05:10:04 am
Re. the locks, this seems to be due to a silly coding error (that's the trouble of not being able to test these things myself :) )   Does that Evolve relay appear in Vera as a lock?

Re. the thermostat: from the screenshot it seems that the thermostat is set to "off"; that would be why it does not show a temperature (perhaps it ought to show --- instead of 0). Try setting the thermostat to heating or cooling; the control should show the corresponding heating or cooling temperature set point.
Title: Re: Beta started!
Post by: Intrepid on August 01, 2012, 07:18:55 am
today's update fixed the thermostat!  it displays proper set point, changes setpoint, and updates setpoint when i change from web UI!  Very nice!
Title: Re: Beta started!
Post by: frichter09 on August 01, 2012, 10:23:10 am
Re. the locks, this seems to be due to a silly coding error (that's the trouble of not being able to test these things myself :) )   Does that Evolve relay appear in Vera as a lock?

Re. the thermostat: from the screenshot it seems that the thermostat is set to "off"; that would be why it does not show a temperature (perhaps it ought to show --- instead of 0). Try setting the thermostat to heating or cooling; the control should show the corresponding heating or cooling temperature set point.
Ah, thanks!
I will try this when I get back home!
The evolve relay does not show up as a lock (which is good because technically its not a lock anyways). It shows up as a on/off switch.
However I am using a plugin to combine my relay and window sensor to a lock. This lock is correctly displayed as a lock in HomeWave...
Title: Re: Beta started!
Post by: knewmania on August 01, 2012, 11:43:06 am
New build posted:
- Added a lock control that uses the correct Service IDs for locks.  If you previously added your locks as on/off switches, please delete them from HomeWave and re-add them; you'll find a separate control type for them.  Try if the control now correctly opens/closes the lock.

I am seeing some oddities with the locks (beyond them not working). I see that locks are now an option to add as a device. When I add the lock their details specify that the lock will appear green when locked and red when unlocked, but when they are added they show up as gray with an unlocked status. At the time of adding the locks, their actual status was locked so the app didn't get the real status. When I actually try to use the lock/unlock function it works similar to what I saw before (and what Flo is reporting). Not sure if these details are helpful, but figured I should report.

Title: Re: Beta started!
Post by: frichter09 on August 01, 2012, 12:09:09 pm
I had the same issue knewmania is reporting as well.
The locks were grey when first added. Just didnt put that info in my first post.  ::)
Title: Re: Beta started!
Post by: intveltr on August 01, 2012, 12:27:42 pm
I am seeing some oddities with the locks (beyond them not working). I see that locks are now an option to add as a device. When I add the lock their details specify that the lock will appear green when locked and red when unlocked, but when they are added they show up as gray with an unlocked status. At the time of adding the locks, their actual status was locked so the app didn't get the real status. When I actually try to use the lock/unlock function it works similar to what I saw before (and what Flo is reporting). Not sure if these details are helpful, but figured I should report.

The grey color indicates that the app hasn't received any info on the device status.  You may still see the color change at some point; the app can figure out the status from the data from Vera in some cases.

While you're messing with locks, could you try the following URL in your browser?  Replace the IP address with that of your own Vera, and the number 57 with the device ID of your lock.  This URL should lock it.

http://192.168.2.13:3480/data_request?output_format=json&id=lu_action&DeviceNum=57&serviceId=urn:micasaverde-com:serviceId:DoorLock1&action=SetTarget&newTargetValue=1
Title: Re: Beta started!
Post by: knewmania on August 01, 2012, 01:00:38 pm
While you're messing with locks, could you try the following URL in your browser? 

I am away from the home for several days so won't be able to try the URL for a while.  :(
Title: Re: Beta started!
Post by: Intrepid on August 01, 2012, 05:43:45 pm
on the thermostat, is it possible to show the STATUS (cooling, heating, idle)?
Title: Re: Beta started!
Post by: intveltr on August 01, 2012, 05:53:48 pm
on the thermostat, is it possible to show the STATUS (cooling, heating, idle)?

Everything is possible :)

Actually, the control already grabs the status when Vera sends it, I could display this info.  Perhaps as a small ice crystal/flame/nothing icon to save space (the control already has a lot of stuff on it)
Title: Re: Beta started!
Post by: frichter09 on August 01, 2012, 05:55:48 pm
Oh, displaying a different icon is a great idea.
Also, maybe you can color code it? red for heat, blue for cooling, grey for idle?
Or maybe let the user choose the color...

Title: Re: Beta started!
Post by: frichter09 on August 01, 2012, 06:03:58 pm
I think I found a bug.
When I re-arrange my home-screen layout (move lights before locks)  this is not reflected on the actual control screens.
the locks will still show up before the lights while swiping...

Flo
Title: Re: Beta started!
Post by: Intrepid on August 01, 2012, 08:02:34 pm
Oh, displaying a different icon is a great idea.
Also, maybe you can color code it? red for heat, blue for cooling, grey for idle?
Or maybe let the user choose the color...

Or a simple H, C, or I.

Or H, C, -



Title: Re: Beta started!
Post by: frichter09 on August 01, 2012, 09:08:24 pm
Or the icons....  :P
Title: Re: Beta started!
Post by: frichter09 on August 01, 2012, 09:24:16 pm
I am seeing some oddities with the locks (beyond them not working). I see that locks are now an option to add as a device. When I add the lock their details specify that the lock will appear green when locked and red when unlocked, but when they are added they show up as gray with an unlocked status. At the time of adding the locks, their actual status was locked so the app didn't get the real status. When I actually try to use the lock/unlock function it works similar to what I saw before (and what Flo is reporting). Not sure if these details are helpful, but figured I should report.

The grey color indicates that the app hasn't received any info on the device status.  You may still see the color change at some point; the app can figure out the status from the data from Vera in some cases.

While you're messing with locks, could you try the following URL in your browser?  Replace the IP address with that of your own Vera, and the number 57 with the device ID of your lock.  This URL should lock it.

http://192.168.2.13:3480/data_request?output_format=json&id=lu_action&DeviceNum=57&serviceId=urn:micasaverde-com:serviceId:DoorLock1&action=SetTarget&newTargetValue=1

This works perfectly fine!
Just tested it!
Title: Re: Beta started!
Post by: intveltr on August 02, 2012, 06:08:43 pm
I think I found a bug.
When I re-arrange my home-screen layout (move lights before locks)  this is not reflected on the actual control screens.
the locks will still show up before the lights while swiping...

Not really a bug :)  The order of the screens is sort of random (it doesn't change though).  Once you start working with different size buttons on the home screen, the relative order of them is kind of hard to work out.  In the future, I may add a feature to specify the sort order and perhaps exclude certain screens from the swipe order.
Title: Re: Beta started!
Post by: intveltr on August 02, 2012, 06:10:29 pm
New build posted:
- Locks should now work (fingers crossed!).  Please delete lock devices and re-add them.
- Thermostat setpoint controls now show "off" when the thermostat is in Off mode.
- Localization added.  Only Dutch & English for now, will send files for translation to volunteers!
Title: Re: Beta started!
Post by: frichter09 on August 02, 2012, 09:47:20 pm
I am happy to report that all my locks are working correctl  ;D ;D ;D ;D ;D

Are you still planing on letting the user choose the overall background color?  8)

Flo
Title: Re: Beta started!
Post by: davidd1205 on August 03, 2012, 03:25:01 am
New build posted:
- Locks should now work (fingers crossed!).  Please delete lock devices and re-add them.
- Thermostat setpoint controls now show "off" when the thermostat is in Off mode.
- Localization added.  Only Dutch & English for now, will send files for translation to volunteers!

yes locks is now good

for french tranlation i can try  :)
Title: Re: Beta started!
Post by: Minnies on August 03, 2012, 09:00:06 am
Yes, locks are now good.

One suggestion. When a switch or device is asked to turn on or change to have status update soon after selection to verify that it was completed. I have found instances where communications did not go through and did not know the action did not occur.

Any news on the Aeon HEM (energy manager)? That is the one thing that causes me to use the Mios web page now.

Thanks,
Ron
Title: Re: Beta started!
Post by: intveltr on August 03, 2012, 09:56:08 am
The problem with status updates is that when a command is sent but not received by Vera, Vera does not send the device's status to the app (since nothing will have changed).  The result is that the device status remains 'unknown'.  It's a tricky condition to work around (and I have seen the same behaviour in other apps); polling the full status after every action would consume too many network and Vera resources.   As far as I know, it is not possible to poll Vera for the state of just a single device.

I have considered adding a Refresh button, so that a full state refresh can be pulled from Vera manually at least.

Re. the Energy manager: this looks like it is a fairly easy device to add.  I have ordered one and will hopefully get it tomorrow or Monday, so I'll have a go at adding it :)
Title: Re: Beta started!
Post by: intveltr on August 03, 2012, 09:57:11 am
Are you still planing on letting the user choose the overall background color?  8)

Not sure if that'll make it into the first release.
Title: Re: Beta started!
Post by: Minnies on August 03, 2012, 11:02:35 am
The problem with status updates is that when a command is sent but not received by Vera, Vera does not send the device's status to the app (since nothing will have changed).  The result is that the device status remains 'unknown'.  It's a tricky condition to work around (and I have seen the same behaviour in other apps); polling the full status after every action would consume too many network and Vera resources.   As far as I know, it is not possible to poll Vera for the state of just a single device.

I have considered adding a Refresh button, so that a full state refresh can be pulled from Vera manually at least.

Re. the Energy manager: this looks like it is a fairly easy device to add.  I have ordered one and will hopefully get it tomorrow or Monday, so I'll have a go at adding it :)

I do poll individual devices by scenes to ensure status are up to date.

luup.call_action("urn:micasaverde-com:serviceId:HaDevice1","Poll",{},72)
Title: Re: Beta started!
Post by: intveltr on August 03, 2012, 05:32:47 pm
Nice, that works over HTTP as well.  I can add an option to issue a Poll action to a device if it is changed from HomeWave.  Not sure if that'll make it into the first release though.
Title: Re: Beta started!
Post by: garrettwp on August 03, 2012, 06:39:07 pm
In my android app (AutHomation) I have the option to poll the device when long pressing the device and choosing the poll option. This can be done as you said over http.

- Garrett
Title: Re: Beta started!
Post by: frichter09 on August 03, 2012, 07:21:09 pm
Be able to poll the device is for sure a feature that should be added :)
Flo
Title: Re: Beta started!
Post by: knewmania on August 04, 2012, 09:26:03 am
New build posted:
- Locks should now work (fingers crossed!).  Please delete lock devices and re-add them.
- Thermostat setpoint controls now show "off" when the thermostat is in Off mode.
- Localization added.  Only Dutch & English for now, will send files for translation to volunteers!

Excellent!

I have a couple of ideas for enhancements:

-The ability to change the size of the webcam view (pinch method).

-Support for camera presets.

-The ability to set/modify lock PIN codes.

-The ability to manually trigger scenes.
Title: Re: Beta started!
Post by: Intrepid on August 04, 2012, 09:32:01 am

-The ability to manually trigger scenes.

Add a scene, click it, it runs in the current version.
Title: Re: Beta started!
Post by: Minnies on August 04, 2012, 09:40:51 am
I forgot where to look as to how to configure if you have more than 1 home/Vera module.
Title: Re: Beta started!
Post by: intveltr on August 04, 2012, 03:34:07 pm
I have a couple of ideas for enhancements:

-The ability to change the size of the webcam view (pinch method).

-Support for camera presets.

-The ability to set/modify lock PIN codes.

Do you mean the ability to zoom the full-screen camera view?
Camera presets and lock PINs will come after launch!
Title: Re: Beta started!
Post by: intveltr on August 04, 2012, 03:35:27 pm
I forgot where to look as to how to configure if you have more than 1 home/Vera module.

Go to your iPhone's Settings thing, and scroll down to the HomeWave app, then click that.  You can manually specify the device's IP there. 
Title: Re: Beta started!
Post by: intveltr on August 04, 2012, 07:16:00 pm
New build posted:
- Added an indicator for heating / cooling for thermostats.  You'll find a new setting to enable this feature in the thermostat control's preference screen, if supported  (the Wifi Thermostat plugin does not seem to support this).
- Added support for Energy Meters (tested on the Aeon Labs Home Energy Meter).
- Fixed a few minor issues with localization.

The last thing to be added to the pilot will be an option to poll individual devices, an information screen (pointing to the website with instructions), and the option to lock controls using a pin code.
Title: Re: Beta started!
Post by: intveltr on August 05, 2012, 12:38:51 pm
In my android app (AutHomation) I have the option to poll the device when long pressing the device and choosing the poll option. This can be done as you said over http.

Hmm, it seems that Vera does not transmit the device's state after a poll, if the polled value is not different from the value currently held in Vera.  So I still need a way to pull the status of an individual device from Vera in case the comms between Vera and HomeWave failed.  Short of pulling the entire Z-wave net's state, can this be done for a single device?
Title: Re: Beta started!
Post by: garrettwp on August 05, 2012, 01:39:20 pm
Once you do a poll, you'll have to re-pull the data from via. Not sure how you are getting the data, e.g. user_data2 or lu_sdata. You'll have to pull that data with the dataversion and loadtime of the last update to get the difference.

- Garrett
Title: Re: Beta started!
Post by: intveltr on August 05, 2012, 02:01:08 pm
Once you do a poll, you'll have to re-pull the data from via. Not sure how you are getting the data, e.g. user_data2 or lu_sdata. You'll have to pull that data with the dataversion and loadtime of the last update to get the difference.

I use user_data2 with dataversion.  The problem is that after polling the device, Vera compares the polled value against the value she already had, and considers the device to be unchanged if the values match.  Therefor the value will not be included in the subsequent user_data2 dump.

This means that if HomeWave did not get the status update after a change due to a comms error, the only way to manually get Vera to re-send the current device state to HomeWave is to issue a user_data2 request for the full status (all devices).
Title: Re: Beta started!
Post by: Intrepid on August 07, 2012, 08:12:27 am
I finally got my foscams set back up.  They work great!

I noticed that if I change the name of a camera in the web UI (renamed the device), the name in homewave does not change, but it continues to work properly.  If I delete and re-add, it picks up the new name.  No biggie.

Title: Re: Beta started!
Post by: intveltr on August 07, 2012, 08:37:33 am
I noticed that if I change the name of a camera in the web UI (renamed the device), the name in homewave does not change, but it continues to work properly.  If I delete and re-add, it picks up the new name.  No biggie.

That's as intended: in many cases you might want to give controls (and cameras) a different name in HomeWave than they have in Vera.

Note: there's a small bug in the camera app; if you open the detail view and then close the app (sned it to the background), the camera control will be unresponsive when you open the app again (and it may crash the app when tapped).  After stopping the app (or after it crashes :) ), it'll work again.
Title: Re: Beta started!
Post by: jtmoore on August 07, 2012, 11:28:29 am
Hi intveltr.
Regarding energy usage support. I don't have the clamp based monitors, but I do have appliance module Everspring AN158 and an Aeon Labs Micro Energy Switch (MSES?). Neither of my devices show in the list when trying to add Energy Meter devices. Will support be added for these please? Thanks.
jtmoore.
Title: Re: Beta started!
Post by: intveltr on August 07, 2012, 04:50:12 pm
These will be supported; the energy readout will be added to the button/dimmer control.  Not sure if it will make the first release, though.
Title: Re: Beta started!
Post by: intveltr on August 09, 2012, 03:52:57 pm
Posted new build:
- Added poll / refresh option: tap and hold >3s on a control will issue a Poll command for that device, and causes HomeWave to reload the state of all controls from Vera.
- Support for PIN code: set it in the Home Screen's help window.  Option to protect buttons, scenes and locks with this PIN.  Delete your lock / button / scene control and re-add to enable this feature for that control.
- Minor bugs and localisation issues
Title: Re: Beta started!
Post by: M2MExpert on August 09, 2012, 04:58:24 pm
The beta testing for HomeWave has started.  Those who have accepted the TestFlight invite (or sent me their UDID) should have an email, and should be able to download & install the app.


 I'd be interested. Is it too late to buy in?
Title: Re: Beta started!
Post by: intveltr on August 09, 2012, 05:21:02 pm
It is too late to join the beta, but the app will most likely be sent to Apple this weekend. Then it's another two weeks or so before it hits the app store
Title: Re: Beta started!
Post by: electricessence on August 09, 2012, 05:46:19 pm
Exciting!
Title: Re: Beta started!
Post by: Intrepid on August 09, 2012, 07:36:52 pm
Intveltr,

Just wanted to say great app!  It is quick and is easy to set up. 

I'll be using it daily for quick control tasks.  Within 5 seconds I can load it, swipe to the screen, and send a command.

 I also use Automator app when I need full control (another great app).

Great job!!


Title: Re: Beta started!
Post by: jtmoore on August 09, 2012, 09:06:45 pm
Great app. Definitely has a high wife approval factor (WAF).
I can't wait for it to appear in the UK app store so I can install it on her iPhone.
Title: Re: Beta started!
Post by: intveltr on August 11, 2012, 03:26:58 pm
New build posted:
- Info screen added
- Moved the buttons for setting the PIN and default screen to the info screen
- Setup button asks for the PIN if one has been set\
- Some minor bugs fixed
Title: Re: Beta started!
Post by: frichter09 on August 11, 2012, 08:38:06 pm
Hi Intveltr,

Would it be possible to implement some kind of visual feedback after a device was polled manully?
Lets say, device turns green for a sec if poll was successful?  8)

Flo
Title: Re: Beta started!
Post by: intveltr on August 12, 2012, 04:30:13 pm
New build posted, with French and German localization
Title: Re: Beta started!
Post by: intveltr on August 14, 2012, 10:07:49 am
Would it be possible to implement some kind of visual feedback after a device was polled manully?
Lets say, device turns green for a sec if poll was successful?  8)

This involves monitoring messages about pending jobs for devices (and scenes), and requires some additional code.  It could be added at a later time (similar to the thingy in UI5 that indicates success / failure to poll or send messages to the device)
Title: Re: Beta started!
Post by: jtmoore on August 16, 2012, 01:47:04 pm
Hi intveltr.

Is there a way to clear the configuration. The Home screen has gone wrong and I've got unwanted control screens of odd sizes that keep shrinking when I try to move them. I've got 13 controls I want to keep and 3 weird ones that I can't control. I think I need bite the bullet and clear the whole configuration and start to configure again. I'll try an attach screen shot to better explain what I mean.

Can you suggest the best way to clear the configuration (e.g. delete and reinstall the app), or do you have a way to remove or resize and reposition the erroneous controls?

Thanks.

jtmoore.
Title: Re: Beta started!
Post by: intveltr on August 16, 2012, 02:19:02 pm
Heh, how did you manage that?

There was a bug that caused this, but only with certain Z-wave controls.  Not sure how it can happen on the home screen.  Unfortunately there is no way (yet) to restore these buttons to their proper function, you'll have to delete the app to wipe the settings.  I recommend that you pull the latest build from Testflight before rebuilding your config (seems you're a few versions behind); the fix that I applied earlier might prevent the issue from occurring on the Home screen as well.
Title: Re: Beta started!
Post by: TommyE on August 29, 2012, 05:18:25 pm
Hello

I'm wondering if you can elaborate on one thing?

When I go out the house and switch from wifi to 3g it takes a little while for the app to 'understand' that is is on 3g.
This is probably 'normal', but I have the feeling it was much faster at doing this in the first betas?

Also:
I have opened my firewall on port 3480 for vera and put in official ip adress in HomeWave settings.

But after a while the settings in homewave is set back to Vera's LAN ip adress.

I would love Vera to connect to my ip and not thru any MIOS services.

Is this possible?

Regards
Tommy
Title: Re: Beta started!
Post by: Intrepid on August 30, 2012, 06:19:58 am
... and the DSC Alarm panel plugin would be great. 

I second this request for DSC alarm panel plugin support. 

And thanks again for this app!
Title: Beta started!
Post by: teonebello on August 30, 2012, 10:23:48 am
... and the DSC Alarm panel plugin would be great. 

I second this request for DSC alarm panel plugin support. 

And thanks again for this app!

Will be' great also the supporti of Powermax alarm plug in!

Thanks
Great app
Matteo
Title: Re: Beta started!
Post by: simdude on August 31, 2012, 05:26:24 pm
Any word from Apple on approval time? I know 2-3 weeks has been normal but I was hoping they improved this a bit.


Edit:

Never mind. It was just released!!!
Title: Re: Beta started!
Post by: sdittoc on August 31, 2012, 08:28:15 pm
The app looks great it is so nice to be able to customize the screens to fit your needs.   I have the Honeywell YTH8320ZW1007 thermostat.  I have noticed that when i change the temperature the unit stops following the schedule.  I can turn the unit on, off, and set to auto but, nothing I do puts it back on schedule.  Any help or suggestions would be great.

thanks,
Title: Re: Beta started!
Post by: sdittoc on August 31, 2012, 09:16:08 pm
Not sure if we should post questions about the app in the beta area now that the app is out....  When I use the app to unlock my Schlage door lock it unlocks and after 5 seconds locks (which is normal for the schlage locks).  Just wanted to note that the app status shows the lock unlock within a couple of seconds.  It takes another couple of minutes to show that it is locked. 
Title: Re: Beta started!
Post by: electricessence on September 01, 2012, 01:24:02 pm
See my comments here:
http://forum.micasaverde.com/index.php/topic,11135.msg82958.html#msg82958
Title: Re: Beta started!
Post by: intveltr on September 01, 2012, 01:35:01 pm

When I go out the house and switch from wifi to 3g it takes a little while for the app to 'understand' that is is on 3g.
This is probably 'normal', but I have the feeling it was much faster at doing this in the first betas?

Also:
I have opened my firewall on port 3480 for vera and put in official ip adress in HomeWave settings.
But after a while the settings in homewave is set back to Vera's LAN ip adress.

I would love Vera to connect to my ip and not thru any MIOS services.

I did make a change at some point in the way the app figures out if it's on the LAN or on 3G. I'll have to take another look at this bit of code; I feel it can be improved further (and connection speed is certainly a top priority).  Network state machines (the bit of code that tracks what kind of connection you have and figures out what to do in case of errors) are notoriously tricky. :(

HomeWave will update the IP address when the MIOS discovery thingy reports a different one.  This is done because in most cases Vera won't have a fixed IP address on the LAN.  I'll add an option to suppress this
Title: Re: Beta started!
Post by: intveltr on September 01, 2012, 01:36:38 pm
Now that the app is released, please post any issues or requests in separate threads on this board. Thanks!