The Vera Community forums have moved!

General => Remote Control => AutHomation (Android) => Topic started by: garrettwp on March 02, 2012, 03:14:56 pm

Title: Public Beta Build of Version 2.0 (Closed: Official Release in Market)
Post by: garrettwp on March 02, 2012, 03:14:56 pm
IMPORTANT: If you are upgrading from 1.3 or older, you will need to remove the previous version before installing.

Everyone, with the new public build of UI5 for Vera announced, I have decided to release a public beta build of the next version of AutHomation/AutHomationHD. This will be version 2.0. The main focus is to have a more unified UI across all platforms that allows me to manage the code in an easier way. Here are some features and I will be adding additional features before a final release:

What has changed:

- New user interface (trying to make it more unified across platforms e.g. tablets, googletv, phones)
- Added an "All" section to display both scenes and devices
- Added an option to poll data in the background when the app is not running. (this is experimental and could drain your battery faster)
- Many bug fixes and other tweaks
- Cleaned up a lot of code and reworked it to allow for better management of adding additional support for devices

I will have to warn that there will be issues and bugs. For the most part, it has been pretty stable. With the new changes in the UI, I have been spending a lot of time trying to get majority of the features back in place. Now I will focus on adding more features and device support and fine tune the graphics. If you feel comfortable to try a beta release, please give it a go and provide me any feedback or issues that you may have.

Here is the download link:

https://www.wuala.com/garrettwp/Android/AutHomation/Public%20Test/?key=cqDXsXIbSidI

AutHomation = Android 2.3 and older
AutHomationHD = Android 3.0 and newer (Tablets, GoogleTV, etc)

- Garrett

UPDATE Release Candidate:

Date: 2012/05/21

I am hoping that this will be the official release. If I do not see any new bugs in the next few days, I will release this into the play store.

Changes:
Minor bug fixes
Added option to turn off text to speech for Voice Recognition.
Added option to change the Voice Recognition error message (e.g. I'm sorry. I'm afraid I do not understand the request.")
Minor tweaks to the under the hood for Voice Recognition.

UPDATE Beta 9:

Date: 2012/05/13

It looks like we are getting very close to a stable build. I have been receiving less reports of issues. Hopefully we can get this pushed out to the market very soon. Let me know if there are any issues.

Changes:
More bug fixes
Added window covering and other minor voice actions to the voice recognition (Clicking on the ( i ) icon in the voice recognition dialog will give you a screen of actions to speak)

Window Covering:
[Open|Close] (device name)
(device name) [Up|Down|Stop]

Added the ability to have the camera image refresh at a specified interval (located in the settings section under devices. Default value is 30 seconds. I plan to have camera streaming in a future build. However testing it will be an issue since the option to have Vera tunnel the camera stream is not working for me.)

UPDATE Beta 8:

Date: 2012/04/29

Changes:
More bug fixes
Added more voice recognition commads:

Thermostat:
Mode:
[Set/Change/Adjust] thermostat name to [Auto|Cool|Heat|Off]
Fan Mode:
[Set/Change/Adjust] thermostat name [fan] to [Auto|On]
Cool Temperature:
[Set/Change/Adjust] thermostat name [cooling|cool temperature] to [temperature]
Heat Temperature:
[Set/Change/Adjust] thermostat name [heating|heat temperature] to [temperature]

Status Info:
Battery Level:
[What is] the [battery level] of device name
Temperature (thermostat, etc)
[What is] the [temperature] of device name

Poll device:
[Poll] device name

Refresh Data:
[Refresh data]

I will try and get a better write up done for the voice commands. If you have any requests, please let me know. I also forgot to mention that the voice recognition portion of the app can accessed via a home screen widget. It is just an icon that allows for direct access to the voice recognition. It can be added by adding a new widget to the home screen and selecting "AutHomation VR / AutHomationHD VR".

UPDATE Beta 7:

Date: 2012/04/24

Changes:
Many bug fixes and force closure fixes
Voice Recognition (Experimental and a work in progress.)

Voice Recognition Info:
English only
May require Google Voice search found in market
Untested on AutHomation (Anroid 2.3 and older)
More commands to come

Usage:

Binary Lights:
[Turn On/Off] device name
[Turn] device name [On/Off]

Dimmable Lights:
[Set/Raise/Lower/Increase/Decrease] device name to [0-100]
[Set/Raise/Lower/Increase/Decrease] device name to [0-100] percent

Locks:
[Lock/Unlock] device name

Security Sensors:
[Arm/Bypass] device name

Scenes:
[Run/Start/Activate/Execute] scene name

Status Info:
[What is the status] of device / scene name
(supports binary lights, dimmable lights, locks, security sensors, scenes, temperature sensors, humidity sensors, energy devices)

Lots more to come with Voice Recognition. Please let me know how it works out for you. It works well if the device and scene names are pronounceable and not abbreviated. You can say part of the name e.g Kitchen Cabinet Lights -> Cabinet Lights.

UPDATE Beta 6:

Date: 2012/04/15

Changes:
Many bug fixes
Fixed memory leaks
More UI adjustments
Added the ability to select either slider or buttons for dimmable devices and window coverings.

Added better device support for AutHomationHD (between phones, tablets and googletv)

This release is more to fix many bugs and memory leaks. No new major features were added.

UPDATE Beta 5:

Date: 2012/03/24

Changes:

Reworked UI for thermostats
Added slider for dimmers and window covering devices replacing the on/off buttons on the device tile
Added battery level support for battery powered devices (requires UI5 version 1.5.344 or newer)
Better connection failure handling
Minor UI tweaks
Bug fixes

UPDATE Beta 4:

Date: 2012/03/16

I have posted an updated beta (beta 4).
Changes:

More bugs fixes.
Support for window coverings.
More UI tweaks
Added error reporting when app crashes (can be disabled, but will help me make this app stable)
Added quick controls for alarm arming/disarming
Added quick controls for window coverings open/close
Added connection status indicator. When the app is refreshing, a "L" will display in the progress indicator for Local connection and a "R" will display for remote connection. (Credit goes to rakstar for this idea)

UPDATE Beta 3:

I have posted an updated beta (beta 3).
Changes:

Bug fixes,
UI changes and tweaks to accommodate some of the user's requests
Added heater device support (Danfoss, etc) - Let me know if there are any issues.
Title: Re: Public Beta Build of Version 2.0
Post by: futzle on March 02, 2012, 05:24:36 pm
Just downloaded it and trying it out on my Honeycomb Galaxy Tab. Looks good! I'll report any issues I see.
Title: Re: Public Beta Build of Version 2.0
Post by: RichardTSchaefer on March 02, 2012, 06:35:04 pm
Garret,
   I have a private Android APP that I have been using for managing Vera. But I like the way yours is going so I will drop mine.
   The primary feature of mine that I like is quick access to things with one hand.
   I had a 3 level tree ... Section ... Room .. Devices + Scenes.
   The max number of items to scroll was at most #Sections, #Rooms In Current Section  + (devices and scenes) from current selected room. If you clicked on any Section or Room node it collapsed the current room and opened the one you picked .. if you picked the current expanded room it would collapse the device and scenes and you would have a simple Section/Room tree. I have close to 100 Scenes + devices. Something to think about.

Relative to polling in the in the background ... I had a service to do all of the IO to Vera. And it constantly polled data ... It's lifecyle was the length of any activity + 10 minutes in case you came back quickly to change something else. I used the events to update the original cached state list of variables. The activities always worked off of that ... The service would send events to the activity if data changed.

Title: Re: Public Beta Build of Version 2.0
Post by: futzle on March 03, 2012, 08:51:59 pm
This may not be a new bug; I never tried with the previous version.

Changing the Arm/Bypass mode on my security sensors doesn't cause them to change state on my security system.  Tailing the LuaUPnP log shows silence when I press Arm or Bypass on the security sensor on AutHomation.

AutHomation shows "Command Sent. Response: OK" when I press Arm or Bypass.  It should be getting back a job ID with this security sensor's implementation.  The security sensor is a child device of a Caddx Security plugin. Implementation is here (http://code.mios.com/trac/mios_caddxnx584/browser/trunk/I_CaddxNX584Security.xml), action is the usual urn:micasaverde-com:serviceId:SecuritySensor1::SetArmed.

If I watch the web interface while pressing Arm/Bypass on AutHomation, the Arm/Bypass symbols change on the device on the web browser in tandem, but the message is never sent to the security system.  This suggests that AutHomation is just setting the Armed state variable rather than calling the SetArmed action.

The same action when done entirely on the web interface works as expected and I see messages in the LuaUPnP log.

I actually don't use the Arm/Bypass feature for security sensors so I am not missing anything with it not working.  This is actually the most serious issue I've had, and for me it's a non-issue.

AutHomation HD Version: 2.0.1.2
Vera OS: 1.5.322
Android OS: Honeycomb
Android device: Samsung Galaxy Tab 7.7

Edit: ooh yeah, the variable is being changed directly:
Code: [Select]
06 03/04/12 12:50:08.274 Device_Variable::m_szValue_set device: 166 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 0 #hooks: 0 upnp: 0 v:0xb88178/NONE duplicate:0 <0x2e614680>
Title: Re: Public Beta Build of Version 2.0
Post by: futzle on March 03, 2012, 09:03:14 pm
Arming a Caddx security partition results in the error "Invalid Service".

From the Luup log I can see why:
Code: [Select]
08 03/04/12 12:55:57.012 JobHandler_LuaUPnP::HandleActionRequest device: 94 service: urn:micasaverde-com:serviceId:AlarmPartition2 action: RequestQuickArmMode <0x2cfe7680>
08 03/04/12 12:55:57.012 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:AlarmPartition2 <0x2cfe7680>
08 03/04/12 12:55:57.012 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=94 <0x2cfe7680>
08 03/04/12 12:55:57.012 JobHandler_LuaUPnP::HandleActionRequest argument action=RequestQuickArmMode <0x2cfe7680>
08 03/04/12 12:55:57.013 JobHandler_LuaUPnP::HandleActionRequest argument State=Stay <0x2cfe7680>
01 03/04/12 12:55:57.013 JobHandler_LuaUPnP::HandleActionRequest can't find urn:micasaverde-com:serviceId:AlarmPartition2 <0x2cfe7680>

The service Id is not "urn:micasaverde-com:serviceId:AlarmPartition2" on the Caddx plugin but "urn:micasaverde-com:serviceId:AlarmPartition1" (code (http://code.mios.com/trac/mios_caddxnx584/browser/trunk/D_CaddxNX584Partition2.xml)).  Control points like AutHomation can't just hardcode these service IDs; they need to parse the device file looking for the service type, and use the matching service Id.  (The Vera web interface gets this wrong too, FWIW.)

Edit: you know, I say that, but I've got a nagging feeling that I might be wrong about it. Who is in charge of service Ids? Think I need to do some more research about how UPnP interoperability was designed to work...
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 03, 2012, 10:15:10 pm
Futzle,

Thank you for your incite. I am using lu_sdata and this does not provide me any data for device type or service id. I have asked MCV to add this to the lu_sdata. I use lu_sdata as it is a fraction of the size of user_data2. This makes it faster to parse the data and keeps the bandwidth down as well. But I hit this limitation of knowing the device serviceid, etc. One suggestion I can do is that when first clicking on the device, I can retrieve the lu_action data and add that to the device data. This would only be a first time thing and will be able to get the proper service id to use. Any thoughts?

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: futzle on March 03, 2012, 11:31:26 pm
Hi Garrett,

lu_sdata is, frankly, useless. Because it hides the service Id of state variables it can't behave in a predictable way when there are two variables with the same name ("status") in different namespaces.  It doesn't tell you what actions are available (or not) on a device.  I think that it's unavoidable to use lu_user_data2 at least once.  Since these parts of the data are truly static, I agree that you need not call this often.  Use the LoadTime attribute on both sdata and user_data2 to learn when the data is potentially out of date (from a Luup SAVE) and needs to be refreshed.
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 04, 2012, 01:03:58 am
I use to use user_data, but even using the dateversion and loadtime, it would do a full sync more often than I would have liked. Also the data is very large and I am trying to avoid excessive bandwidth. But if I have to resort back to user_data and sdata, I will. If I call say, lu_action on the first open of a device, I can get the service id and action states without having to rely on user_data. So my options are do I use lu_action or do I go back to user_data and sdata? Thoughts?

- Garrett

p.s. I appreciate you all providing me feedback. I want to make this app work for everyone and if I have to change the way I do things, I will. I want to make sure I go the best route possible without making an compromises.
Title: Re: Public Beta Build of Version 2.0
Post by: cokeman on March 04, 2012, 04:59:59 am
Hi,

Looking great. But have an issue with the Danfoss thermostats

Shows up with "Error Thermostats is not configured" and the gui that pops up, shows cooling and heating, the "heat temp is correct" but the icon, shows as -1

Hope you can help.

And the "Virtual Switch"  shows up as "?" as does the "Info container"

/cokeman
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 04, 2012, 05:44:57 am
cokeman,

I still have not incorporated the danfoss thermostats yet.

As for "virtual switch" and "info container", these plugins are not supported.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: futzle on March 04, 2012, 06:49:11 am
So my options are do I use lu_action or do I go back to user_data and sdata? Thoughts?

It's a dilemma, I admit.  For my Vera, sdata is ten times smaller than user_data2, so your point is well made. There may be nothing else for it than to code it up and see.  Personally my Android device is Wi-Fi only, so I'm less concerned about data usage than a phone owner would be about 3G data. Make sure you filter my opinions through that knowledge.
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 04, 2012, 07:05:40 am
Thanks Futzle for your incite. I have to think about which route to go. Both methods supply similar data. User_data will be a little harder as the service id's under ControlURLs are not in an array and makes parsing the data tricky. Now another problem is trying to figure out which serviceid to use as most of the devices provide multiple.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: guessed on March 04, 2012, 02:55:02 pm
The service Id is not "urn:micasaverde-com:serviceId:AlarmPartition2" on the Caddx plugin but "urn:micasaverde-com:serviceId:AlarmPartition1" (code (http://code.mios.com/trac/mios_caddxnx584/browser/trunk/D_CaddxNX584Partition2.xml)).

  Control points like AutHomation can't just hardcode these service IDs; they need to parse the device file looking for the service type, and use the matching service Id.  (The Vera web interface gets this wrong too, FWIW.)

Edit: you know, I say that, but I've got a nagging feeling that I might be wrong about it. Who is in charge of service Ids? Think I need to do some more research about how UPnP interoperability was designed to work...
Um, the serviceId for "version 2" of the Alarm panel interface (or the standardization effort) was intended to be:
    urn:micasaverde-com:serviceId:AlarmPartition2

The original interface, as implemented by the Paradox, the "original" DSC, and I think even the first incarnations of your GE was version 1.  It had a serviceId of:
    urn:micasaverde-com:serviceId:AlarmPartition1

The newer DSC code threw out compatibility, and eliminated it's use of version 1.  The Paradox implements both, so I suspect that your GE showing "version 1", but  implementing the "version 2" methods & state-Variables, might be a throwback to the time we were all transitioning the Alarm Partition implementations over.

Bottom line, we do need to have a standardized serviceId, otherwise the CP's can't know what methods and state-Variables exist within the device.  Without standardized serviceId's, even things like Light Switches wouldn't work, although we can have whatever DeviceType (and friends we want, barring the CP's that don't handle that well)

I skimmed over the Vista, PowerMax, Elk, Paradox and DSC and they all implement the version 2 Alarm Panel serviceId:
    urn:micasaverde-com:serviceId:AlarmPartition2
Title: Re: Public Beta Build of Version 2.0
Post by: guessed on March 04, 2012, 03:02:14 pm
@garrettwp,
As to the size of the content, for transmission purposes, that's why I originally created this:
    http://bugs.micasaverde.com/view.php?id=1204

It's a one-line configuration in Vera's lighty, and things would be a lot faster for mobile devices...

with a little CPU used on either end (Vera and the Client) the compression ratio is quite high.  It would save not only bandwidth, but also the time to transmit (since most phones are relatively bandwidth limited).  Of course, it doesn't fix the parse-time issues you're looking to address as well.

Title: Re: Public Beta Build of Version 2.0
Post by: RichardTSchaefer on March 05, 2012, 11:06:30 am
I have used user_data2 and lu_status2. The only time I needed a resync was when Vera's Luup engine was restarted. Not very often. So this is just a startup issue.
On my clients I always kept the JSON object from user_data2 and update it when I get new data from lu_status2. So my json object is continuously synchronized to Vera.
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 05, 2012, 11:39:25 am
Richard,
 Thanks for the info. I use a database to store the data and update the data in the database as new data arrives using lu_sdata with the loadtime and dataversion parameters. As of right now I have decided to stick with lu_sdata. Going with user_data would solve maybe an issue or two, but would not be worth the effort to rewrite. I still face the issue on what serviceid to use. I have asked MCV awhile ago to include the serviceId in the lu_sdata as well as the device_type. Hopefully that is something that can be added in the near future. They have already added additional data that should be available in the next beta.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: RichardTSchaefer on March 05, 2012, 03:12:33 pm
Is Version 2.0 dependent on UI5 ?
I have not downloaded yet because I assumed it was ... But you know what they say about those that assume ...  :D
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 05, 2012, 03:46:34 pm
No, it should not be dependent on UI5. It should work without issue in UI4 minus a few things that were introduced in UI5 for fixes. If you load it, let me know how it goes. 

- Garrett

Title: Re: Public Beta Build of Version 2.0
Post by: futzle on March 05, 2012, 04:03:14 pm
I'll fix up the Caddx plugin to use the same service id. Migrating it without messing with users will be tricky, but that's my problem, not Garrett's.

Edit: grammar
Title: Re: Public Beta Build of Version 2.0
Post by: Ap15e on March 05, 2012, 04:15:38 pm
Version 2.0 beta works just fine on my V1@1.1.1338.
Title: Re: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 05, 2012, 09:40:18 pm
Version 2.0 beta works just fine on my V1@1.1.1338.

Thanks Ap15e for confirming. I was going to try it on my fathers unit as he is still running on UI4.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: chixxi on March 06, 2012, 06:49:07 am
Quote
As for "virtual switch" and "info container", these plugins are not supported.

Any chance to change you mind about that topic? I think these two are some of the most used plugins as for the moment. I'd be glad to provide any info you need, and also do the testing for it. Or can you tell me why you are rejecting support so I could improve them according to your wishes?

Will be testing the beta on my Sony Tablet S (Honeycomp 3.2.1) tonight and report back as soon as possible.
Title: Re: Public Beta Build of Version 2.0
Post by: S-F on March 06, 2012, 07:49:57 am
I made the switch to this beta yesterday. I haven't had any crashes or anything like that yet, so, so far so good.

BTW have you been getting my crash reports? I always give them the title "crash".

On a note unrelated to stability, I don't like having to select a device and open a new window to control it. If I want to dim a light or unlock my door I have to go through more steps now. Is this something you could make optional? I'm not sure I understand why this change to the UI was made.
Title: Re: Public Beta Build of Version 2.0
Post by: Da_JoJo on March 06, 2012, 10:46:33 am
installed 2.0  looks nice but i like the old way of switches better.  first there was a toggle switch and now i get this poppup with the switch , it takes more space and its less usefull this way. for the rest its a major improvement :-)
when i press an unknown device presented with a ? (questionmark) the app immediatly crashes. (powercontroller for mce and heliotrope)

i use:
-vera light (ver 1.5.322) connected to asus n56u router
-dell streak 2.3.2 android phone connected to t-mobile internet

p.s. is there support for other languages ?  i can translate for you if you need any .. dutch/german/french/croatian/greek
Title: Re: Public Beta Build of Version 2.0
Post by: chixxi on March 06, 2012, 12:02:19 pm
OK, I tested AutHomation on my Sony Tablet S running on Honeycomp 3.2.1 together with a vera3 running on 1.5.322.

The App runs very stable, I had only one crash up to now when changing the sort order from section to room. I do like the wish which was already posted that the most important commands could be made without opening a popup first, but that's just a wish. Some things I found/thought:

I don't really think it's a bug: No battery levels of any sensors are shown (only the variable value in "info").

As already mentioned the wwa-02 temperature and leak sensor is not shown correctly. It has an arm and bypass button, which it does not have on the vera. But it seems to have this function to be able to arm it.

I think it would be nice if the room selected would stay selected when browsing through the top menu "Scenes-Devices-All-Favorites". But that's only what I think.

In all the non recognized devices I can see the devices variables by going to "info". Instead of showing a question mark I would just show these variables. For a lot of plugins this would already be great. For example the VariableContainer Plugin  ;D of course you wouldn't be able to set the variables. But you could already read a whole lot of things like states, times and temperatures.

And still my greatest wish: Give the VirtualSwitch from apps.mios.com a chance. But I also saw that this thread already includes a major discussion about the serviceid topic.

That was just short testing. Will post if further bugs/wishes occur.
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 06, 2012, 12:23:10 pm
Quote
As for "virtual switch" and "info container", these plugins are not supported.

Any chance to change you mind about that topic? I think these two are some of the most used plugins as for the moment. I'd be glad to provide any info you need, and also do the testing for it. Or can you tell me why you are rejecting support so I could improve them according to your wishes?

Will be testing the beta on my Sony Tablet S (Honeycomp 3.2.1) tonight and report back as soon as possible.

Looks like I have a lot of responding to do. I'll start with yours first Chixxi. I am not against supporting your plugins. I would love to support them! The lu_sdata only provides so much and I have no way of knowing what type of device your plugin is. I have requested to have MCV provide the device_type and serviceId into the lu_sdata to help figure out what device is what. By knowing the serviceId of the device and plugin, I can easily add support for these sort of things.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: chixxi on March 06, 2012, 12:29:12 pm
sorry, finally got home a took a closer look at your approach with lu_sdata and the very interesting discussion you had in this thread with futzle. And I realized/understood to late that the data you need is just not provided. Didn't want to stress you, I think it would be great for general user experience, and I am glad you're positive too.
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 06, 2012, 12:30:43 pm
I made the switch to this beta yesterday. I haven't had any crashes or anything like that yet, so, so far so good.

BTW have you been getting my crash reports? I always give them the title "crash".

On a note unrelated to stability, I don't like having to select a device and open a new window to control it. If I want to dim a light or unlock my door I have to go through more steps now. Is this something you could make optional? I'm not sure I understand why this change to the UI was made.

There are many reasons for the new layout. Here they are:

- By going with the new layout, I have unified the whole UI across tablets, googletv and phones. This also allowed me to consolidate much of the code to make it much easier to maintain.
- Going with the dialog for the devices allows me to keep each and every device in it's own code base. Making modifications to one device will not affect other devices. This also allows me to provide more data and actions in the dialog. The old way had all of the UI elements in one layout and the code also in one code base and it was getting harder to maintain and making changes could have caused issues with other devices.
- It may not make sense now, but having the new layout also allows me to have more devices being displayed at one time to get an overview of what device is doing what. The old layout wasted space per each device.

I apologize for these changes and I hope that you understand.

- Garrett

p.s. here is a revised layout for the phone that allows for more device to be displayed. I still need to tweak.

Title: Re: Public Beta Build of Version 2.0
Post by: guessed on March 06, 2012, 12:32:07 pm
.... it also works a ton better for D-Pad navigation on GoogleTV!
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 06, 2012, 12:41:02 pm
installed 2.0  looks nice but i like the old way of switches better.  first there was a toggle switch and now i get this poppup with the switch , it takes more space and its less usefull this way. for the rest its a major improvement :-)
when i press an unknown device presented with a ? (questionmark) the app immediatly crashes. (powercontroller for mce and heliotrope)

i use:
-vera light (ver 1.5.322) connected to asus n56u router
-dell streak 2.3.2 android phone connected to t-mobile internet

p.s. is there support for other languages ?  i can translate for you if you need any .. dutch/german/french/croatian/greek

See directed to S-F above for some explanations. Switching from the toggle to the off/on buttons was a request by a few users. it also follows the UI guidelines that many off the other apps use. The reason for the off/on was that some were having issues with not being able to properly send the correct off/on command to a device that either had range issues or was not providing the correct status at that time. By having the off/on, if you want to make sure that the device needs to be off, you simple press the off button and the off command will be sent. The toggle button would do the opposite of what the status of that device was. So you  would have to press it several times to get the correct state you wanted.

For the crash, would you be willing to provide me your data so I can have a look? It looks like something in the lu_sdata is not playing well with the app.

As for the wasted space, I have reworked the phone layout that now provides around 6 devices on the screen at once. I still need to tweak it. The old layout actually wasted more space even though you had the controls there. The new layout is suppose to provide you the overview and any actions needed, you simply press on it and you have all of the controls there. I know it is an extra click.

As for other languages, I have not done anything yet. I need to consolidate all of the static strings, e.g. menus  and settings into a file to allow for other languages.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 06, 2012, 12:42:17 pm
.... it also works a ton better for D-Pad navigation on GoogleTV!

Still some issues to work out, but yes it is much better to move around on the screen. I do hope people understand where my direction is going. It is very hard to please everyone.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 06, 2012, 12:58:02 pm
sorry, finally got home a took a closer look at your approach with lu_sdata and the very interesting discussion you had in this thread with futzle. And I realized/understood to late that the data you need is just not provided. Didn't want to stress you, I think it would be great for general user experience, and I am glad you're positive too.

Glad you understand where I am coming from. The big reason for the lu_sdata is the size. For example, my user_data2 is over 500KB and the lu_sdata is only 14.5KB. Do you see the difference. Also the changes between the two formats are also smaller for the lu_sdata as well. This was a compromise to keep bandwidth down for phone users. I have hope that lu_sdata will get more information available to help with 3rd party development. MCV has already added additional information for me into the lu_sdata that should be available in the coming betas. e.g. battery status which you have mentioned in your previous post.

Quote
I think it would be nice if the room selected would stay selected when browsing through the top menu "Scenes-Devices-All-Favorites". But that's only what I think.

This should work under 3.2. It should highlight the selected room when going back and forth between tabs. For some reason, under Ice Cream, it does not do this anymore and I can not figure out why. I am using the proper method to highlight the room when it resumes to that tab. I am aware of this and working on a way to fix it.

When you click on the info for that device and you see all of those variables in the dialog window, that is pulling the data from vera directly using "id=status&output_format=json&DeviceNum=deviceid". So it is polling vera for the status of the device and I am just simply parsing the json data to display it.

Can you reproduce the crash when doing the sorting again? If is happens again, can you provide me your data so I can track the bug down?

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: guessed on March 06, 2012, 01:00:58 pm
@garrettwp,
I like the way it's heading, the two big items for me now (as a GTV User) are:

a) More Devices displayed concurrently in the grid .... each one being smaller (of course)
b) Simplification/Consolidation of the secondary controls (sorters, menu buttons etc) to reduce the clutter on the screen
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 06, 2012, 01:28:01 pm
@garrettwp,
I like the way it's heading, the two big items for me now (as a GTV User) are:

a) More Devices displayed concurrently in the grid .... each one being smaller (of course)
b) Simplification/Consolidation of the secondary controls (sorters, menu buttons etc) to reduce the clutter on the screen

Guessed,

How is this:

Title: Re: Public Beta Build of Version 2.0
Post by: guessed on March 06, 2012, 01:29:32 pm
@garrettwp,
One thing that might ease problem solving for you is to add an option to "email" the lu_sdata to you.  This could be an option in your Developer menu (etc) but it'll save people having to compose the right kind of URL to fetch it (remotely, locally, etc)

Activating it would fetch the latest [full] lu_sdata, and fire up Email with this as an attachment... ready for the user to "send" it to you (with appropriate disclosures, of course)

Just a thought...
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 06, 2012, 01:34:13 pm
Great idea. I'll look into adding that. Would make things so much easier.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: guessed on March 06, 2012, 01:34:35 pm
Better.  I was hoping to reduce the left Rooms Menu, using smaller fonts, and merge and/or eliminate the far-left and far-right items so I could get a 4x3 grid of Devices (my TV is 50", so these turn out to be quite big)

It would be interesting to know the avg Devices/Room in a "typical" Vera unit, since having most of those fit on a single page, without scrolling, would also be handy...


BTW: What does the Eye do in the right menu?  I clicked it a bunch and couldn't tell what it was doing...

@garrettwp,
I like the way it's heading, the two big items for me now (as a GTV User) are:

a) More Devices displayed concurrently in the grid .... each one being smaller (of course)
b) Simplification/Consolidation of the secondary controls (sorters, menu buttons etc) to reduce the clutter on the screen

Guessed,

How is this:
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 06, 2012, 01:42:09 pm
Let me see what I can do with some more adjusting. The eye is to show and hide devices or scenes that were hidden. I need to implement a tool tip when going to each icon so you know what it does.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: drag0n on March 06, 2012, 04:03:28 pm
The new version looks great on my kindle fire!
I think it could be useful if along with devices and scenes you would add a third category for sensors. Although technically they are devices in practice they have quite different functionality and I believe that presenting them separately will improve usability.
thank you for sharing with us this great app  :)
Title: Re: Public Beta Build of Version 2.0
Post by: Da_JoJo on March 07, 2012, 08:48:22 pm
happy to supply you any file you require  (its this ? http://MY_VERA_IP:3480/data_request?id=lu_sdata&output_format=json (http://MY_VERA_IP:3480/data_request?id=lu_sdata&output_format=json) )
i like the prog a lot and its allready most used app on my phone  ;D
would be great if you could put the on and off buttons on the same page instead of a popup still..  and maybe scroll the tile  to the left with the finger to show its variables ? maybe also a page that has only buttons for control and little text above it , so one has an sort off total control page ?

 
Title: Re: Public Beta Build of Version 2.0
Post by: S-F on March 08, 2012, 09:54:52 am
Last night I downgraded to the version on the market because of the way devices are accessed in the beta and I can say that I'm much happier with it. I know it may not sound like much but having to navigate through all kinds of different windows and hit a bunch of buttons to do something simple like turn a light on was driving me nuts.Selecting a room and then turning a light on is a much smoother process than selecting a room, selecting a device, turning it on and then hitting "done". There is lag in opening up the new window for a device so if I'm locked out of the house I would before just hit unlock on the tablet. Now it's just as complicated for me to enter my PIN. Currently everything I use this app for works pretty well in the latest public version so I don't have much of a reason to change any way. Will the option be available to continue using the current version in the future?
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 08, 2012, 10:19:31 am
I am sorry that you are not liking the new design. I know there is an extra step. The original way was getting to complex and hard to maintain. It also wasted space for devices that did not have much control. I have a few things I can propose to help ease the situation. I can allow the device image to implement the "toggle" state action. If a device supports this option, e.g. lights, locks, etc, it will toggle the state of the device. For example, if a light is off, issuing the toggle state would turn it on, or if a lock is unlocked, it would issue the lock state. Another thing I can offer, which I have in place right now for scenes is to have the dialog close after issuing an action. So if you press the off button on a light, the dialog will automatically close. I know this is not the exact solution to what you want, but it might be a good compromise.

As for supporting the older release, I will not be adding any additional code to it. It should function until MCV changes something on their end and breaks compatibility.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: guessed on March 08, 2012, 10:48:27 am
@garrettwp,
I think there are some options here using a combination of the following features:

a) tap vs press-and-hold
b) setting components to be skipped in the keyboard-based focus traversal order
c) making the focus occur on the item they're most likely to select when the dialog appears (will change for on/off controls)
d) making some dialog selections auto-close the dialog (mostly on/off controls)
Title: Re: Public Beta Build of Version 2.0
Post by: S-F on March 08, 2012, 04:10:27 pm
I am sorry that you are not liking the new design. I know there is an extra step. The original way was getting to complex and hard to maintain. It also wasted space for devices that did not have much control. I have a few things I can propose to help ease the situation. I can allow the device image to implement the "toggle" state action. If a device supports this option, e.g. lights, locks, etc, it will toggle the state of the device. For example, if a light is off, issuing the toggle state would turn it on, or if a lock is unlocked, it would issue the lock state. Another thing I can offer, which I have in place right now for scenes is to have the dialog close after issuing an action. So if you press the off button on a light, the dialog will automatically close. I know this is not the exact solution to what you want, but it might be a good compromise.

As for supporting the older release, I will not be adding any additional code to it. It should function until MCV changes something on their end and breaks compatibility.

- Garrett

Locks and lights are basically all I can think of ATM that need this kind of interface. Changing temperature and so forth isn't used as often and wouldn't suffer much from needing to deal with a more involved interface. If you could make lights turn on and off without having to open new windows and jump through hoops it'll be fine. If I can open up the app, select the room and turn the light on or off with no additional steps I'll be happy.

Thanks for trying to work with us. I understand that the challenges of developing free software make such changes necessary and I'm glad you are taking our input seriously. Honestly, as this is ultimately your personal project we need to be satisfied with whatever you produce to suit your own needs. I'm glad for the tool and hope you continue to find personal gain in it's development.
Title: Re: Public Beta Build of Version 2.0
Post by: fba on March 08, 2012, 04:26:52 pm
I like the direction this is heading.   I do wish I had the newer layout that fits multiple columns on the screen, that looks handy.   I agree that it would be nice to be able to control the state of some devices directly from their "tile" without needing to pull up another screen.   But, at the same time I can see the advantage of having more space in the menu that pops up.   Perhaps a good middle of the road solution is to allow lights and locks to toggle when you tap the image in the tile?   It isn't obvious, but it would allow the basic control to be paired with the desire to fit more information on the screen.  Of course, it could also open a huge can of worms in dealing with the difference between devices that can handle it and devices that can't.

garrettwp -

I noticed in a previous post a quick discussion about being able to e-mail information.  It is pretty easy to do.  If you want some sample code either PM or e-mail me and I can send you some.
Title: Re: Public Beta Build of Version 2.0
Post by: Da_JoJo on March 08, 2012, 05:48:19 pm
I am sorry that you are not liking the new design. I know there is an extra step. The original way was getting to complex and hard to maintain. It also wasted space for devices that did not have much control. I have a few things I can propose to help ease the situation. I can allow the device image to implement the "toggle" state action. If a device supports this option, e.g. lights, locks, etc, it will toggle the state of the device. For example, if a light is off, issuing the toggle state would turn it on, or if a lock is unlocked, it would issue the lock state. Another thing I can offer, which I have in place right now for scenes is to have the dialog close after issuing an action. So if you press the off button on a light, the dialog will automatically close. I know this is not the exact solution to what you want, but it might be a good compromise.

As for supporting the older release, I will not be adding any additional code to it. It should function until MCV changes something on their end and breaks compatibility.

- Garrett
i see the advantage of this on and off button, but cant it be on the tile itself or would this make the tile to big ?
did you get my file ? i can tell you what device is what if needed or anything else you might require :-)
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 09, 2012, 07:04:36 am
I like the direction this is heading.   I do wish I had the newer layout that fits multiple columns on the screen, that looks handy.   I agree that it would be nice to be able to control the state of some devices directly from their "tile" without needing to pull up another screen.   But, at the same time I can see the advantage of having more space in the menu that pops up.   Perhaps a good middle of the road solution is to allow lights and locks to toggle when you tap the image in the tile?   It isn't obvious, but it would allow the basic control to be paired with the desire to fit more information on the screen.  Of course, it could also open a huge can of worms in dealing with the difference between devices that can handle it and devices that can't.

garrettwp -

I noticed in a previous post a quick discussion about being able to e-mail information.  It is pretty easy to do.  If you want some sample code either PM or e-mail me and I can send you some.

Adding the toggle state is pretty easy. I would just add the function to the devices that support it. On my journey home yesterday from work (commute 60 miles each way), I did some thinking and I am going to try and put some basic functions onto the tiles, e.g. on/ff for lights, lock/unlock for locks, arm/bypass for security sensors, etc. I started to add the code when I got home, but ran into an annoying bug that I need to think on how I can solve it.

I have looked up some code on emailing the data over at stackoverflow. I would be interested in what you have if you want to pm me.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 09, 2012, 07:08:27 am
I am sorry that you are not liking the new design. I know there is an extra step. The original way was getting to complex and hard to maintain. It also wasted space for devices that did not have much control. I have a few things I can propose to help ease the situation. I can allow the device image to implement the "toggle" state action. If a device supports this option, e.g. lights, locks, etc, it will toggle the state of the device. For example, if a light is off, issuing the toggle state would turn it on, or if a lock is unlocked, it would issue the lock state. Another thing I can offer, which I have in place right now for scenes is to have the dialog close after issuing an action. So if you press the off button on a light, the dialog will automatically close. I know this is not the exact solution to what you want, but it might be a good compromise.

As for supporting the older release, I will not be adding any additional code to it. It should function until MCV changes something on their end and breaks compatibility.

- Garrett

i see the advantage of this on and off button, but cant it be on the tile itself or would this make the tile to big ?
did you get my file ? i can tell you what device is what if needed or anything else you might require :-)


I did not have a chance to grab the file in time. Can you email me the data to authomation at garrettpower dot com? Can you also tell me the device numbers as well?

I am looking at adding basic function to the tile and it will cause the phone layouts to loose space, but you gain basic function like on/off, etc. I ran into an issue that i need to figure out how to solve. Once I can get that worked out, I can start adding the rest of the code to the app and tweak the tile layout.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: Da_JoJo on March 09, 2012, 07:15:15 am
cool.. thnx for ur hard work :-)
i send the file to ur adress. i have a look at the devices and numbers and report back when done.
any bugs or problem you ran into you can ask us people here and we can do our best to think and solve it.
 
edit: done.. i made a list of the devices and the id that come with it. but i guess this is in the data-file also. it is just the devices that are psychical that require identification as to what device in real-world it is right ?
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 09, 2012, 01:40:22 pm
@Da_JoJo,

Got the info and I'll look at it later. I've been trying to get the new code working and added across both platforms of the app. Here is what I have come up with. Does this get the seal of approval? I've added basic controls for lights, locks, and security sensors. Need to add the ability to run a scene as well. Hopefully I can start back on getting the other bugs worked out and add the additional features others have requested. Keep changing in layouts is taking me away from all of that. But I hope we all can settle on something and I can make majority of you happy. :)

- Garrett

Title: Re: Public Beta Build of Version 2.0
Post by: guessed on March 09, 2012, 01:46:41 pm
Nice!  Looks like a reasonable compromise to me.
Title: Re: Public Beta Build of Version 2.0
Post by: Da_JoJo on March 09, 2012, 02:58:49 pm
awesome !
love it   ;D
 
Title: Re: Public Beta Build of Version 2.0
Post by: S-F on March 09, 2012, 03:22:01 pm
Yeah. Looks good! Thanks for all the effort. It's much appreciated.
Title: Re: Public Beta Build of Version 2.0
Post by: guessed on March 09, 2012, 04:32:13 pm
@garrettwp,
Out of interest, does the Button location (Bottom or Side) depend upon screen orientation (Horizontal or Vertical)?

ie. What does the phone version look like when it's sideways?
Title: Re: Public Beta Build of Version 2.0
Post by: Da_JoJo on March 09, 2012, 04:59:56 pm
@garrettwp,
Out of interest, does the Button location (Bottom or Side) depend upon screen orientation (Horizontal or Vertical)?

ie. What does the phone version look like when it's sideways?

2 tiles next to eachother with lot of empty space    4 tiles on screen  in landscape orientation
2 tiles next to eachother with no space                  8 tiles on normal orientation

i vote for making the tiles in the second picture of garett  to 6 tiles and put on / off  , arm, unarmed  etc  under in the tile and in landscape on the right side of tile..  hoping it aint to much efford.. i see now what is the difficulty here.. a good intuive ui needs user-experience and a lot of feedback and thinking and then reworking the code.. and dont forget the coffee ..
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 09, 2012, 05:59:28 pm
The sad thing is that when putting in the quick action buttons, you loose the ability to have many tiles on the screen for the phone as I am working with limited screen real estate. I'll play around come more, but the comprise with adding back the buttons is loosing how many tiles I can have on the screen.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: Da_JoJo on March 09, 2012, 06:22:17 pm
i think 6 tiles with on/off buttons is a nice comprimise vs the 8 with the popup
i mean one want to use it as a remote so making it into 2 steps is not really convienient ... my 2 cents
 
what would be really cool is to have one page holding all the devices where you can zoom in and eventually press buttons when zoomed to 4 tile size or so

 
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 09, 2012, 06:36:13 pm
Trying to get even 6 tiles onto a screen for a phone is going to be a feat on it's own that includes the buttons. Like I said, I will try and see what I can come up with, but adding the extra buttons took away of having more tiles being displayed on the screen.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 09, 2012, 07:03:53 pm
This is the best that I can do for the phone layout on a screen that is 800x480. If the names of the device is longer than the tile, it will scroll.

- Garrett

Title: Re: Public Beta Build of Version 2.0
Post by: Da_JoJo on March 09, 2012, 07:51:22 pm
oke now u got me speechless lol
just perfect... i'll stop whining now and start bowing and be greatfull  ;D
just ordered this greenway 6 powernode.. takes about a week to arrive alas . it seems to have 6 outputs and support for the device is about 95% . it seems to have 7 controls which of 6 are switches for the outlets and the 7th is unknow.. probably scenecontrol or mastre slave or similar or wattage meter..
it might oppose another challenge to overcome. as in 6 on / off buttons on a tile...   does it then display all this buttons or just the main one ?
 mm well lets first see how the things shows up i my vera..
i think this is going to be an issue for the vera ui also.. more multi-function devices will come out like this 6 outlet powernode and the 8-way in/out board and also some lawncontrol which easily have 16 outputs or more.. there is some serieus problem here i think
Title: Re: Public Beta Build of Version 2.0
Post by: garrettwp on March 10, 2012, 06:50:34 am
installed 2.0  looks nice but i like the old way of switches better.  first there was a toggle switch and now i get this poppup with the switch , it takes more space and its less usefull this way. for the rest its a major improvement :-)
when i press an unknown device presented with a ? (questionmark) the app immediatly crashes. (powercontroller for mce and heliotrope)

i use:
-vera light (ver 1.5.322) connected to asus n56u router
-dell streak 2.3.2 android phone connected to t-mobile internet

p.s. is there support for other languages ?  i can translate for you if you need any .. dutch/german/french/croatian/greek

I looked at your data and loaded it up on my app to try and reproduce the crash. I did not get any crashes. I did make changes on the back end after I released the public beta that must have fixed your issue. I am hoping to have  a new release out in the next day or so with the new changes and some bug fixes. Hopefully I can get started on the rest of the things on my list.

- Garrett
Title: Re: Public Beta Build of Version 2.0
Post by: Da_JoJo on March 10, 2012, 08:53:28 am
Quote
I looked at your data and loaded it up on my app to try and reproduce the crash. I did not get any crashes. I did make changes on the back end after I released the public beta that must have fixed your issue. I am hoping to have  a new release out in the next day or so with the new changes and some bug fixes. Hopefully I can get started on the rest of the things on my list.

- Garrett
most appreciated
strange thing is my batteryscreen dissapeared as well and the batt-loader gives errors on my phone.. reverted it to busybox 1.9.3 as this worked better.. the app still crashes though.. it doesnt when i dont press the buttons and it restarts pretty fast so i dont have a problem with it.. take ur time. i fi can be of assistance lemme know  ;D
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 10, 2012, 10:07:41 am
I just posted a new updated beta. Give it a try and let me know if there are any issues, or if you have any suggestions.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: guessed on March 10, 2012, 10:18:46 am
It looks like the new dashboard armed/bypass buttons are coming up vertically centered on the GoogleTvV.  This places them (roughly) on top of the device label.

Also, for scenes, single they simple actions also, you may run to expose a direct (Run) button for them.

My device is a Logitech Revue, running on a 1080p 58" display. (if it matters)
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: S-F on March 10, 2012, 10:34:47 am
Yeah, I can work with this. Thanks for working so hard to make concessions. It is really much appreciated.

One thing though, it seems the, I don't know what to call it, thing that would circulate when refreshing, is gone. As I was having issues with crashes before, and you thought that it might be due to closing before the refresh was done that might be a good feature to have.
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: guessed on March 10, 2012, 10:36:17 am
A few extra findings...

a) I managed to move keyboard focus to a lit and turn it on from the dash, but now I have a message like "Guest Bedroom 2: Transmit was ok" that's stuck on the UI of that Device.  It marquees every now and gain, but doesn't go away.

Not sure how I managed to get keyboard focus on the On/Off buttons either.

b) the DPad Ok button won't navigate to the Device dialog if it has dashboard buttons.

c) IR dashboard device have a ? Icon instead of the usual IR icon (cosmetic only)


I really like the grid arrangement... It should help speed through the devices a lot faster.

PS: didn't notice before that you had GTV keyboard controls for (S)cene, (D)evices, (A)ll, (R)efresh and (L)search.  .. Very handy
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: Da_JoJo on March 10, 2012, 11:14:36 am
I just posted a new updated beta. Give it a try and let me know if there are any issues, or if you have any suggestions.

- Garrett
going to now :-)
per room favourites would also be nice option and a compact page with only pushbuttons maybe
edit;
tried it now and it dont crash anymore :-)  ah wel this one time when i slide ftom devices screen to left to the selectionscreen and back
but i donno what i exactly did and cannot reproduce it till now.
the landscape has now 9 tiles which lower row is only half shown.. might it be possible to put the on/off buttons right next to the picture on top of eachother so it can fit the 9 tiles..  my screen is also 800x480 but it is a dell streak with another dpi then most phones with this display res
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 10, 2012, 11:35:05 am
A few extra findings...

a) I managed to move keyboard focus to a lit and turn it on from the dash, but now I have a message like "Guest Bedroom 2: Transmit was ok" that's stuck on the UI of that Device.  It marquees every now and gain, but doesn't go away.

Not sure how I managed to get keyboard focus on the On/Off buttons either.

b) the DPad Ok button won't navigate to the Device dialog if it has dashboard buttons.

c) IR dashboard device have a ? Icon instead of the usual IR icon (cosmetic only)


I really like the grid arrangement... It should help speed through the devices a lot faster.

PS: didn't notice before that you had GTV keyboard controls for (S)cene, (D)evices, (A)ll, (R)efresh and (L)search.  .. Very handy

Guessed,

Those controls were not suppose to show up on the googletv interface. I must have changed something and not checked the googletv version to make sure. I will fix this asap.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 10, 2012, 11:44:39 am
Yeah, I can work with this. Thanks for working so hard to make concessions. It is really much appreciated.

One thing though, it seems the, I don't know what to call it, thing that would circulate when refreshing, is gone. As I was having issues with crashes before, and you thought that it might be due to closing before the refresh was done that might be a good feature to have.

The progress indicator should still be there. I am going to fix a few things and upload a new build. This is running on Ice Cream correct?

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 10, 2012, 11:58:48 am
Uploaded new build to fix the googletv issue.

@S-F
 
Try and load this build up and see if the progress indicator is working. It shows up on my Asus Transformer running Ice Cream and HTC Evo running Ice Cream.

@guessed

Clicking on the scene icon, (Tablet and phone versions) will fire off the scene. The comment "Transmit Ok" should go away after the next refresh.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 10, 2012, 12:17:41 pm
I just posted a new updated beta. Give it a try and let me know if there are any issues, or if you have any suggestions.

- Garrett
going to now :-)
per room favourites would also be nice option and a compact page with only pushbuttons maybe
edit;
tried it now and it dont crash anymore :-)  ah wel this one time when i slide ftom devices screen to left to the selectionscreen and back
but i donno what i exactly did and cannot reproduce it till now.
the landscape has now 9 tiles which lower row is only half shown.. might it be possible to put the on/off buttons right next to the picture on top of eachother so it can fit the 9 tiles..  my screen is also 800x480 but it is a dell streak with another dpi then most phones with this display res

I looked at the specs of the Dell and will try to emulate it and see what I can do.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: Da_JoJo on March 10, 2012, 01:07:54 pm
Quote
I looked at the specs of the Dell and will try to emulate it and see what I can do.

- Garrett
most impressive :-)
its not major thing though..
this time when i installed latest version my phone-app asks to move it to sd-card :-)  this means u made major progress am i right ?
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 10, 2012, 01:41:37 pm
Quote
I looked at the specs of the Dell and will try to emulate it and see what I can do.

- Garrett
most impressive :-)
its not major thing though..
this time when i installed latest version my phone-app asks to move it to sd-card :-)  this means u made major progress am i right ?

Hmm, the option to move to sdcard has always been there. Not sure why it came up now. I did make some progress on getting more to fit onto your Dell. What I did was to have the grid auto fit the tiles based on the screen resolution. So what you see is the most that it can get onto the screen.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: S-F on March 10, 2012, 01:57:31 pm
So I loaded up the new build and there was still no progress indicator. I locked and unlocked a door and turned a light on and off through the toggle interfaces on the tiles. Same as I did earlier with the last build. No progress indicator present. Then I tried to change the temperature on a thermostat and had to open up a new window to do it. After opening the new window and making the change the progress indicator appeared where it was expected to be. Now it persists even after closing the window. Go figure. Maybe this would have happened with the last build too. I don't know as I didn't try opening a window. On another note, changing the temp is pretty difficult for me. I couldn't change it by selecting a number to delete and replacing it. I had to use the slider which was pretty difficult to get the desired number with. I just tried it again and I still can't manage it (changing the temp by using keys that is). Oh, and it would be nice to have the target temp listed as well as the current on the tile.

And as always this is on my Prime with ICS.

Thanks
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: Da_JoJo on March 10, 2012, 02:16:20 pm
Quote
Hmm, the option to move to sdcard has always been there. Not sure why it came up now. I did make some progress on getting more to fit onto your Dell. What I did was to have the grid auto fit the tiles based on the screen resolution. So what you see is the most that it can get onto the screen.

- Garrett

ow nvrmnd that i have it on main mem as i have enough space on it (2x32gb sd-card)
this screen solution is the most perfect :-) thnx for the extra trouble you made, highly appreciated
i hope to have my 6 power node next week so i can see how this works out on the vera.. so far what i understand its not 100% working with vera and might have 7 buttons instead of 8.. this would be a good test for the prog and offcourse a new device.
still wonder why the switched power-outlets are considered light-switches... i mean i now have a device called coffeemachine which consumes 1490 watts and it has a light-bulb next to it lol .. not that it aint the brightest idea to have coffee but it aint a light .. its vera related and not to ur prog but still this would be nice if it be changed to power-outlet or something like that.. switched load perhaps.. and a icon like a standard wall-outlet country-specific even
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: futzle on March 11, 2012, 01:06:14 am
Latest beta is spectacular on Galaxy Tab 7.7. Arm/bypass on sensors works perfectly with Caddx motion sensors now. I didn't try arm/disarm on the partition because I have to fix its service id as discussed.
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 11, 2012, 01:18:33 am
Glad to here that it is working. I am going to add arm/disarm quick buttons to the alarm panel tile. For the security sensor arm/bypass, I accidentally had a typo in the code that was calling the wrong lu_action.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: Da_JoJo on March 11, 2012, 07:06:24 am
so far its doing great.. it didnt crash and i tried any combination and polling and all one can try on this baby
but..
i just found one bug.its hard to get this little flyer but its there lol
so after a lot of fiddling around i found it must be in the refresh cycle. all the rest works but when i open some popup screens from temp and this ? devices and then slide back left to the screen with all /global/etc it sometimes crash while the circle refresh thingy in the top right starts spinning.  it doesnt spin also when its working on something whereas the former version did.not sure this was by design but its nice to have a circling thing that tells one its busy doing whatever it needs to do (beyond scope for the normal user so its preferable that it works so they can see its doing its thing and they should wait for the miracles to happen first)
the layout is really cool and i cant wait for the next update with more tiles on it  ;D
its the best compromise in screen remoting and these popups are actually handy to see the bigger picture
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: Da_JoJo on March 12, 2012, 07:12:13 pm
oke .. i started running around with my fly-catcher and found the little (-parental restriction applied-)
when the authomation is in refresh-cylce and i exit the program while its doing this with the back-button on my android, it crashes
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 12, 2012, 09:33:40 pm
Thanks for the info, I'll try and reproduce and get a fix put in.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 13, 2012, 01:45:37 am
oke .. i started running around with my fly-catcher and found the little (-parental restriction applied-)
when the authomation is in refresh-cylce and i exit the program while its doing this with the back-button on my android, it crashes

I was able to reproduce the bug and added a fix to correct it. It will be available in the next beta release.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: chevdor on March 13, 2012, 02:46:45 am
Very nice app. Very snappy compared to home buddy.

Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: Da_JoJo on March 13, 2012, 10:10:08 am
oke .. i started running around with my fly-catcher and found the little (-parental restriction applied-)
when the authomation is in refresh-cylce and i exit the program while its doing this with the back-button on my android, it crashes

I was able to reproduce the bug and added a fix to correct it. It will be available in the next beta release.

- Garrett
aight..lookin forward to next release, cant wait :-D
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 16, 2012, 09:10:01 am
A new beta has been posted. Please give it a try and let me know if there are any issues, concerns, etc. See first post for details.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: Kyle on March 16, 2012, 12:25:04 pm
A new beta has been posted. Please give it a try and let me know if there are any issues, concerns, etc. See first post for details.

- Garrett

Garrett,

When I click on my thermostat control it will automatically set the fan to on and it's also saying "null" under the temp. Other than that I think it looks good! Here is whats happening when bring my thermostat controls up:


04   03/16/12 12:17:52.184    <0x803>
08   03/16/12 12:18:04.569   JobHandler_LuaUPnP::HandleActionRequest device: 5 service: urn:upnp-org:serviceId:HVAC_FanOperatingMode1 action: SetMode <0x16408>
08   03/16/12 12:18:04.569   JobHandler_LuaUPnP::HandleActionRequest argument fwdserver=1 <0x16408>
08   03/16/12 12:18:04.570   JobHandler_LuaUPnP::HandleActionRequest argument remoteIP=*********** <0x16408>
08   03/16/12 12:18:04.571   JobHandler_LuaUPnP::HandleActionRequest argument PK_AccessPoint=***** <0x16408>
08   03/16/12 12:18:04.571   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:HVAC_FanOperatingMode1 <0x16408>
08   03/16/12 12:18:04.572   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=5 <0x16408>
08   03/16/12 12:18:04.573   JobHandler_LuaUPnP::HandleActionRequest argument action=SetMode <0x16408>   
Title: Re: Public Beta Build of Version 2.0 Beta 3
Post by: garrettwp on March 16, 2012, 01:47:49 pm
A new beta has been posted. Please give it a try and let me know if there are any issues, concerns, etc. See first post for details.

- Garrett

Garrett,

When I click on my thermostat control it will automatically set the fan to on and it's also saying "null" under the temp. Other than that I think it looks good! Here is whats happening when bring my thermostat controls up:


04   03/16/12 12:17:52.184    <0x803>
08   03/16/12 12:18:04.569   JobHandler_LuaUPnP::HandleActionRequest device: 5 service: urn:upnp-org:serviceId:HVAC_FanOperatingMode1 action: SetMode <0x16408>
08   03/16/12 12:18:04.569   JobHandler_LuaUPnP::HandleActionRequest argument fwdserver=1 <0x16408>
08   03/16/12 12:18:04.570   JobHandler_LuaUPnP::HandleActionRequest argument remoteIP=*********** <0x16408>
08   03/16/12 12:18:04.571   JobHandler_LuaUPnP::HandleActionRequest argument PK_AccessPoint=***** <0x16408>
08   03/16/12 12:18:04.571   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:HVAC_FanOperatingMode1 <0x16408>
08   03/16/12 12:18:04.572   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=5 <0x16408>
08   03/16/12 12:18:04.573   JobHandler_LuaUPnP::HandleActionRequest argument action=SetMode <0x16408>

Thanks for the info. What UI version are you running? Are you still on UI4? What is your thermostats current fan mode set to? I have looked at your old lu_sdata and it should have the "null" value show that status of your thermostat (e.g. Idle, Heating, etc). Would you be willing to provide me an update lu_sdata?

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: Kyle on March 16, 2012, 02:03:43 pm
No problem man! I am running UI4 still.. The current fan mode is set to Auto. I'm not home now, but i will provide you with an updated lu_sdata when I get home. It was working fine on the previous beta. I even completely uninstalled the app and did a fresh install.
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 16, 2012, 02:06:59 pm
Kyle,

I just uploaded a new build to fix some bugs including yours. Please give it a try and let me know. I think I tracked down the issues.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: Kyle on March 16, 2012, 02:23:16 pm
All fixed now! New layout is nice too! Thanks man!
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: Da_JoJo on March 16, 2012, 05:03:56 pm
installing :-)
started dutch translation for mios also yesterday.. allmost done. which makes me come up with this lietle point..  the language locale support thingy... its still possible or you recon its to much of rebuilding involved ?
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: radarengineer on March 16, 2012, 09:58:23 pm
@garrettwp, the new layout is really sharp!
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: S-F on March 18, 2012, 01:15:52 am
The crashes I was experiencing before seem to have completely disappeared. Also, thanks for including the temp set point in the tile for thermostats.

It's coming along nicely and I'm still using it all the time.

Now if only my tablet worked properly (don't get an Asus Transformer Prime).
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 18, 2012, 01:33:14 am
@garrettwp, the new layout is really sharp!

Thanks for the comment. I am trying my best to make it clean.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 18, 2012, 01:43:04 am
The crashes I was experiencing before seem to have completely disappeared. Also, thanks for including the temp set point in the tile for thermostats.

It's coming along nicely and I'm still using it all the time.

Now if only my tablet worked properly (don't get an Asus Transformer Prime).

The crashes I found were related to the progress indicator and I have rewrote how it works in the app. I am glad that this fixed the crashes. Still learning here...

Is the location of the set points ok? Should it be tweaked? Now that the UI design is set, I can work on tweaking, adding new features and fixing any bugs that may crop up. With the new error reporting in this release, I have fixed several bugs that were being reported. I have a feeling it is going to be a huge life saver when it comes to finding and fixing bugs. Should have added it a long time ago.

Some things I will be working on for beat 5:

Just added battery level for devices that report battery status. Still needs tweaking. (requires firmware UI 5 1.5.344 or newer)
Redesign the Alarm Panel Dialog
Tweak the HVAC Dialog
More tweaking...

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: S-F on March 18, 2012, 07:56:26 am

Is the location of the set points ok? Should it be tweaked? Now that the UI design is set, I can work on tweaking, adding new features and fixing any bugs that may crop up. With the new error reporting in this release, I have fixed several bugs that were being reported. I have a feeling it is going to be a huge life saver when it comes to finding and fixing bugs. Should have added it a long time ago.



I just tried setting temperatures via AutHomation. I can now interface with the set point directly but the app doesn't seem to respond to what I set. I just stays the same after hitting "Done".
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: S-F on March 18, 2012, 11:02:18 pm
I just tried to turn off a light by hitting the off button on it's tile and instead of turning it off the screen changed to a different room. Anything like that ever happen to anyone else or was it just a fluke?  :P

And I didn't accidentally change rooms via normal methods.
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 19, 2012, 12:40:30 am
That is very odd indeed. This only occurred once? By any chance and I know that you stated you did not change rooms by normal methods, but was the tile next to the list of rooms? Could it be that your finger accidentally hit the room next to the tile? Just trying to eliminate all possibilities. I have not experienced this issue.

- Garrett

UPDATE:

Scratch that, I did find a glitch in the build and fixed the issue. For some reason if after selecting different rooms, the app would not release the data of the previous room selections and when the app would go to refresh the data, it would refresh the current room you are in plus the previous rooms that were viewed prior.  Thanks for let me know about the bug.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: Da_JoJo on March 19, 2012, 06:22:43 am
ah cool.. this probably also fixes that when resume from standby after some time the switch from my tv-module responds with empty bla.
 
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 19, 2012, 12:25:52 pm
ah cool.. this probably also fixes that when resume from standby after some time the switch from my tv-module responds with empty bla.

Did this happen in the version before this one or did it only show up in the current beta?

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: Da_JoJo on March 19, 2012, 01:17:15 pm
still happening.. mostly after resume from standby of the phone. probably it gets confused as i have my wifi settings to automaticly connect to mobile internet whenever it looses wifi connection or is in standby.
its telling me it got an empty response.. not sure whats causing it. seems to have improved with latest version though.
 
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 19, 2012, 01:20:28 pm
I made some additional changes the other day to try to get data a few times before warning the user. Before it would just try once with the active server and a second time on the backup server. The issue you are experiencing is that it is trying to get the data but looks to not have a solid connection with the vera and causes the data to be incomplete.

- Garrett

p.s. I am hoping to have another beta by friday with more bug fixes and a few tweaks to the UI. I am trying to release a new build at the end of each week. (Do not hold it against me if I slip here and there). I am hoping that I can get something official to release to the market in the near future. So please provide me any feedback and issues.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: S-F on March 19, 2012, 01:31:14 pm
Yeah, I certainly didn't accidentally press another room. The one that appeared was about as far away from the one I hit as possible.

On another note, this version I'm using now is much more stable than the one in the market. Basically it always works. The one in the market basically works too, just that it would crash on me from time to time and that's history now. So I wouldn't be uncomfortable about putting it up in the market, of the play area, or whatever they call it now.  ::)
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 19, 2012, 01:39:41 pm
S-F,

Glad it is stable for you. I am trying my best to get everything as stable as possible. Programming in Java and Android is all new to me and I have come a long way in the past year. I want to add a few more features to this version and tweak the UI before releasing to the market(play area). But hopefully in the very near future this will get added to the market. You guys have provided me with a lot of feedback and your concerns and I really appreciate it.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: Da_JoJo on March 19, 2012, 01:47:04 pm
I made some additional changes the other day to try to get data a few times before warning the user. Before it would just try once with the active server and a second time on the backup server. The issue you are experiencing is that it is trying to get the data but looks to not have a solid connection with the vera and causes the data to be incomplete.

- Garrett

p.s. I am hoping to have another beta by friday with more bug fixes and a few tweaks to the UI. I am trying to release a new build at the end of each week. (Do not hold it against me if I slip here and there). I am hoping that I can get something official to release to the market in the near future. So please provide me any feedback and issues.

- Garrett
that be great :)
take ur time and i do my best to be of assistance.. and yes it can be put on the market, i guess, since other version tends to crash anyways and this one is fairly stable and it will auto-update then instead of me having to turn on bluetooth and send it etc. :D
might as well set up a paypal donations account so we can "give you the €0,02 in reality lol
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: S-F on March 20, 2012, 10:49:44 pm
100% reproducible. When under Global /Devices if I turn my bathroom light off, for example, once the command is sent the screen will refresh and only show the devices in my kitchen while the tab on the left side still indicates Global, All.  Oddly if I manipulate a device in any other room I still get only the kitchen devices after the refresh. Pretty weird. Probable wasn't caught before because the global view isn't used much.
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 20, 2012, 11:56:48 pm
100% reproducible. When under Global /Devices if I turn my bathroom light off, for example, once the command is sent the screen will refresh and only show the devices in my kitchen while the tab on the left side still indicates Global, All.  Oddly if I manipulate a device in any other room I still get only the kitchen devices after the refresh. Pretty weird. Probable wasn't caught before because the global view isn't used much.

S-F,

This sounds like a similar issue you were experiencing with the room changing when turning off a device. I hopefully have fixed this issue.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: S-F on March 21, 2012, 06:14:49 am
Oh man I hope so. That was the first time I had selected All and now It will flash between the room I want to see and all quite frequently. And it happens when I interface with a device.
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: Martimus on March 21, 2012, 05:14:50 pm
Hi all...

Just downloaded the public beta to experiment with.  Tried loading it on my two Android tablets.  Works great on my Motorola Xoom running ICS 4.0.3.  Does not work, however, on my HP Touchpad running an Alpha version of Cyanogen Mod 9.  The fact that it doesn't work on the Touchpad does not surprise me as CM9 is still very early in it's development.  Just wanted to let others know.

Since I'm rather new to Vera I'll play with this more over the coming days/weeks and provide additional feedback as appropriate.

EDIT:  Out of curiousity I installed a newer version of the CM9 ROM on my Touchpad and then tried installing the AutHomation HD app again.  This time it complained that it could not find my Vera Lite server.  I provided it my username and then password.  It now finds the Vera Lite server and seems to communicate with it ok.  It's possible that the older version of CM9 caused the issue and it's possible that the problem could be with AutHomation HD and CM9.  Either way it seems to be working at the moment...  so I'll experiment with it some more to see if I can find an explanation.
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: S-F on March 21, 2012, 09:47:43 pm
This app is going bananas on me. It seems to like recently utilized scenes and devices because when I change rooms it will bring the last used ones along with me into the new room. That is until I activate a new device and the screen refreshes. The craziness always happens on the screen refresh after activating a device.

Am I the only one here?

Jeez, this is making me self conscious.
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 22, 2012, 12:04:24 am
This app is going bananas on me. It seems to like recently utilized scenes and devices because when I change rooms it will bring the last used ones along with me into the new room. That is until I activate a new device and the screen refreshes. The craziness always happens on the screen refresh after activating a device.

Am I the only one here?

Jeez, this is making me self conscious.

S-F,

If you give me another day or two, a new beta will be released and should have this fixed. I believe majority of the people are using this on their phones so they do not see this issue.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: garrettwp on March 22, 2012, 12:06:13 am
Hi all...

Just downloaded the public beta to experiment with.  Tried loading it on my two Android tablets.  Works great on my Motorola Xoom running ICS 4.0.3.  Does not work, however, on my HP Touchpad running an Alpha version of Cyanogen Mod 9.  The fact that it doesn't work on the Touchpad does not surprise me as CM9 is still very early in it's development.  Just wanted to let others know.

Since I'm rather new to Vera I'll play with this more over the coming days/weeks and provide additional feedback as appropriate.

EDIT:  Out of curiousity I installed a newer version of the CM9 ROM on my Touchpad and then tried installing the AutHomation HD app again.  This time it complained that it could not find my Vera Lite server.  I provided it my username and then password.  It now finds the Vera Lite server and seems to communicate with it ok.  It's possible that the older version of CM9 caused the issue and it's possible that the problem could be with AutHomation HD and CM9.  Either way it seems to be working at the moment...  so I'll experiment with it some more to see if I can find an explanation.

When you say it did not work, what do you mean by that? Does the app not load at all? When you were trying to configure the app, did you use the autoconfigure method? Were you on the same network as the vera unit?

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 4
Post by: Martimus on March 22, 2012, 01:42:08 am

When you say it did not work, what do you mean by that? Does the app not load at all? When you were trying to configure the app, did you use the autoconfigure method? Were you on the same network as the vera unit?

- Garrett

Before I upgraded the ROM on the Touchpad (CM9 Alpha 031812), the app actually acted like it found the Vera Lite on it's local network.  This was kind of odd since the wireless AP that my Touchpad connects to is on an adjoining subnet (outside my firewall).  When I first ran the app I clicked the auto config button and it immediately found the info on my Vera Lite.  The letter inside of the refresh indicator was an "L".  When I attempted to connect to it, however, I randomly got two different messages.  The first was an error message with an error code.  Unfortunately, however, I didn't write the message down and don't recall the specific message text.  The second message indicated that the connection timed out.

After I re-imaged my Touchpad with a newer Alpha build of CM9 (Alpha 031912) and installed the AutHomation HD beta, I again clicked the auto config button.  This time, however, it behaved differently and told me that it could not find my Vera Lite.  After a couple of unsuccessful attempts It asked me for my MIOS user name and then my password.  With that info it was able to locate and connect to my Vera Lite successfully as a remote device ("R" in the refresh indicator).

Given that the ROM on my Touchpad it an Alpha nightly build it's very possible that the ROM had an internal issue that caused the problem.  And, for that matter, re-imaging the tablet may have been all it needed.  That's the problem with nighlies... there is no guarantee of stability from one night to the next.  On the other hand, if it weren't for these Alpha releases, my poor HP Touchpad would still be running WEBOS  ::)
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on March 27, 2012, 10:07:20 pm
It's been quiet in here. Either there are no serious issues and most of the bugs have been squished our no one is using the app.  ;)

It's it safe to say that the app is ready for market release? I just need to do a little cosmetic taking. Thoughts?

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: S-F on March 27, 2012, 11:01:20 pm
It's been quiet in here. Either there are no serious issues and most of the bugs have been squished our no one is using the app.  ;)

It's it safe to say that the app is ready for market release? I just need to do a little cosmetic taking. Thoughts?

- Garrett

WTF? Did you release the new version when I wasn't looking? The app is going completely nuts for me. I have a bookmark for the dashboard now for when AutHomation goes crazy. As it is I wouldn't release it publicly. I personally didn't have any issues at all until the moment (the exact moment mind) that I switched to viewing all rooms. Never been the same. AutHomation shows whatever room it wants, whenever it wants. I try to turn the light off in my bedroom to go to bed and my daughter yells at me because I turned the lights off on her in the bathroom because the room changed itself right before I hit the screen. It's almost funny.  I haven't made any noise because I know you're not only a free man but also one with limited time who is developing software for free and I didn't want to pester you.

EDIT:

Well, I just checked the OP and sure enough you posted an update several days ago. I didn't notice because the thread progress didn't reflect it. I'm on it now and will report back in 24 - 48 hours when I've had time to put it through its paces.

Thanks for the update!
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on March 27, 2012, 11:16:31 pm
S-F,

My apologies for not making a new post on the new beta. I've been working long 7 day weeks. Please let me know if this build fixes the sporadic rooms.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: grybrd on March 28, 2012, 12:09:08 pm
@garrettwp  ... I am still on the old release cause family comes first as far as bugs go ..LOL
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: S-F on March 28, 2012, 05:53:05 pm
@garrettwp  ... I am still on the old release cause family comes first as far as bugs go ..LOL

Don't worry about it. Just take the plunge. The newest version seems to be working fine.
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on March 28, 2012, 09:40:55 pm
So all is well? No crazy room changing voodoo? Glad to here!  :)

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: Da_JoJo on March 29, 2012, 05:10:15 am
ima try the new version
a way to put a icon of a device or an icon that would start a scene from the aandroid-desktop would be nice :)
edit: installed and quit installer screen.. gone to desktop.. start authomation.. crash report send..  authomation starts anyway.. press 6 buttons of my 6 port powernode.. ey that went a bit faster then before  ;D   response time over t-mobile highspeed cell to my 100mbit fd home internet :  < 4 secs
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on March 29, 2012, 05:12:31 am
ima try the new version
a way to put a icon of a device or an icon that would start a scene from the aandroid-desktop would be nice :)

It is on the list. Not sure when it will get added.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: futzle on March 29, 2012, 05:18:13 am
Just installed beta 5. Awesome. No immediate problems. I say go for it.
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: Da_JoJo on March 29, 2012, 05:28:20 am
ima try the new version
a way to put a icon of a device or an icon that would start a scene from the aandroid-desktop would be nice :)

It is on the list. Not sure when it will get added.

- Garrett
Lemme hug you :D
improvement on the beta5 is surely noticable, but you might wanna look at my crash-report.. some minor thingy i think.
http://blog.doityourselfandroid.com/2011/05/24/developing-android-home-screenwidgets/ (http://blog.doityourselfandroid.com/2011/05/24/developing-android-home-screenwidgets/)
http://www.vogella.de/articles/AndroidWidgets/article.html (http://www.vogella.de/articles/AndroidWidgets/article.html)
this could be of help :)
was thinking of a per room  4x4 tile which holds temp, lightsensorvalue,humidity and powerusage and link to authomation prog , separate 1x1 tiles for any device. maybe put per 4 in a 4x4 tile. and some 2x1 tiles for drapers, fibaro duo-switch, curtain-control,heating,
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on March 29, 2012, 06:01:32 am
I did get your crash report. In the beta 5, I made changes to the database. I used the database feature called onUpgrade() and it alters the database tables. I have tested this on different android platforms and on the previous versions of the app. I am not sure why it crashed on you. The error was that it could not find the new columns that were added. I will have to look into this further and try to get this nailed down. It should have populated the new columns before adding the new data.

Anyone else have any issues when loading up beta 5?

- Garrett

p.s. to fix this, go into the app settings and under Development click on "Clear Database" option.

Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: Da_JoJo on March 29, 2012, 06:10:33 am
think its my 6 port powernode.. i switched group just before and the order is changed but authomation didnt keep up as i closed it and updated the prog.. energy readings from the device also not working 100%
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on March 29, 2012, 07:03:08 am
The energy readings are not working in the app or in general?

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: S-F on March 29, 2012, 07:48:38 am
Dimmable lights no longer have toggle buttons on the tiles? That's something I'd like to see. Even if it's just the ability to tap the tile to toggle the state. But then again, that opens the new window for the device.

So far no craziness, although I haven't really put it through it's paces yet. I have tried selecting all rooms, or devices, or whatever it is, and the rooms aren't changing on me any more. So that's a relief.
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on March 30, 2012, 12:51:28 am
Dimmable lights no longer have toggle buttons on the tiles? That's something I'd like to see. Even if it's just the ability to tap the tile to toggle the state. But then again, that opens the new window for the device.

So far no craziness, although I haven't really put it through it's paces yet. I have tried selecting all rooms, or devices, or whatever it is, and the rooms aren't changing on me any more. So that's a relief.

I am planning on adding an option in the settings section to choose weather to display the slider or on/off buttons for dimmable lights. Same will go for window coverings as well.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: Da_JoJo on March 30, 2012, 04:06:34 am
The energy readings are not working in the app or in general?

- Garrett
general, the sub-devices tend to mess up the measurement reading..
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: PurdueGuy on March 31, 2012, 11:22:03 pm
@garrettwp,

I just installed AutHomation on my Kinde Fire, which I plan to mount on the wall.  So far, so good...excellent work!

I am running UI5, and I moved changed some category numbers to move things to different tabs under "Devices."  I moved all fans (either actual fan controllers (VRF01s) or just regular switches (VRS15s) to be on the "Climate" tab instead of "Lights" tab.

Now because of that, AutHomation seems to think they are thermostats?  The icons are a grey thermometer with null degrees and null set points.  Tapping on one of them results in the app crashing.
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on April 01, 2012, 01:25:24 am
@garrettwp,

I just installed AutHomation on my Kinde Fire, which I plan to mount on the wall.  So far, so good...excellent work!

I am running UI5, and I moved changed some category numbers to move things to different tabs under "Devices."  I moved all fans (either actual fan controllers (VRF01s) or just regular switches (VRS15s) to be on the "Climate" tab instead of "Lights" tab.

Now because of that, AutHomation seems to think they are thermostats?  The icons are a grey thermometer with null degrees and null set points.  Tapping on one of them results in the app crashing.

Because you changed the category numbers of the devices, the app thinks that those devices are the new categories. The app figures out what device type each device is by the category number. The reason for this is that I use lu_sdata which is a simple version of the data that Vera uses. This keeps the bandwidth down and also speeds up refreshing of data. The only way to fix this is by changing the devices back to their respective device categories.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: PurdueGuy on April 01, 2012, 01:28:33 am
Because you changed the category numbers of the devices, the app thinks that those devices are the new categories. The app figures out what device type each device is by the category number. The reason for this is that I use lu_sdata which is a simple version of the data that Vera uses. This keeps the bandwidth down and also speeds up refreshing of data. The only way to fix this is by changing the devices back to their respective device categories.

- Garrett
I figured as much, just thought I would check!
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on April 01, 2012, 01:57:17 am
Because you changed the category numbers of the devices, the app thinks that those devices are the new categories. The app figures out what device type each device is by the category number. The reason for this is that I use lu_sdata which is a simple version of the data that Vera uses. This keeps the bandwidth down and also speeds up refreshing of data. The only way to fix this is by changing the devices back to their respective device categories.

- Garrett
I figured as much, just thought I would check!

I put in a request with MCV about a month ago to add the service id of the devices into the lu_sdata. This would allow me to parse by the service id of the device and not the category number. This would allow me to easily support user plugins and also allow for what you are doing.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: tomcat on April 04, 2012, 09:38:02 pm
should I always receive a snapshot from my vera unit instead of a real video streaming in my Skyrocket? ....in the other hand, this beta release works smooth....also, do i have to root my kindle to get the .apk file in it?.....(i've tested the video from the vistacam via "local dashboard" and get no image...

..sorry for my English...
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on April 04, 2012, 10:10:43 pm
should I always receive a snapshot from my vera unit instead of a real video streaming in my Skyrocket? ....in the other hand, this beta release works smooth....also, do i have to root my kindle to get the .apk file in it?.....(i've tested the video from the vistacam via "local dashboard" and get no image...

..sorry for my English...

Right now it is just still images. Streaming is on the top of my list though.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: tomcat on April 04, 2012, 10:18:55 pm
..Garrett, five stars!!
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: capjay on April 05, 2012, 06:30:22 am
the HD beta version is amazing! Very smooth, no problems at all. Definite 5 stars.
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: S-F on April 05, 2012, 10:17:25 pm
Well, it seems to be running completely correctly. I stand corrected. I had assumed that some of the problems I was having were related to my device or to the OS but these days everything works as expected.

Cheers! And thanks for all the hard work. I'm using this app on a very regular basis and it beats anything else out there.

Aside from being able to toggle devices from the tile, as we have already discussed, the only thing I can say is that devices that can only be toggled, like outlets and son on, don't need to have a new window that opens when hit.
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: Da_JoJo on April 07, 2012, 08:42:57 am
jeej found another flyer  ;D


and yes thanx for all the hard work and im greatfull to have been of help.
it would not been this great without you
it more then deserves the 5+ stars as this made homecontrol go to the next level.


like to add another option for the near future :  gps tracking...  so that one leaves the house and all gets shut down automaticly :)
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: chixxi on April 10, 2012, 04:12:12 am
Did some extended testing/playing on the weekend. App is running perfectly fine on my Sony Tablet S. I was very glad to see that you realized so many wishes which were mentioned in the beginning of this forum!

And I am also very happy to see that you are still trying to make your app compatible with vera-plugins in other threads in this forum  ;)

Impressive work, thank you.
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on April 10, 2012, 06:08:54 am
Glad things are working out so far. I am hoping to have another build out soon. Been sick this past week and working way to much overtime does not help either. It is taking me longer to get another build out. I have fixed more bugs that were reported by users via the crash reporting tool. I am also adding voice recognition to the app as well (only english is supported for now). More details about that later. Also more UI tweaks have been made.

As for trying to support 3rd party plugins. It is on the top of my list. It is a matter of getting MCV on the same page and implement my request of adding the device type into the lu_sdata for each device. Another option is to have MCV add "device id" to the search request of the "finddevice" luup request. Both solutions have been discussed with MCVFlorin and MCV. Just waiting to hear on which solution will be implemented. Hopefully the first option. MCV is hesitant in adding the device type to the lu_sdata as they believe it will cause the lu_sdata to grow large in size. I do not think it will have that big effect on the size of the data. Time will tell.

- Garrett

Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: S-F on April 10, 2012, 09:32:35 pm
@ gattettwp, I know you've talked about adding voice commands and am wondering if you've thought about adding support for RichardTSchaefer's HAL? I don't know all of what adding voice support would entail but I'm assuming that to do it right would take a lot and you could let him take care of it. Or if not maybe just add support for HAL so two separate tools aren't needed.
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: garrettwp on April 11, 2012, 12:16:01 am
Richard's HAL remote is a great piece of software and he has done a fine job with it. There are a few reasons for adding my own voice recognition into my app. I do not want to have to depend on a client / server type software that needs to be installed on a windows computer running all of the time. The only computer that runs 24/7 is my linux server that hosts my virtual machines, etc. My other computers are off or sleeping when not in use. I also do not run windows all of the time as I am a linux guy. You also have to be on the local network to use the software unless you open up ports in the firewall which I am very strict about.

The way I am implementing voice recognition is using Google's voice search api's. The voice data gets sent to google's servers for processing and results get sent back to the app for parsing. The only requirement is that you have an active internet connection (which should not be an issue). It will take some work and time to get it to work and done right, but hopefully it will be a useful feature.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 5
Post by: S-F on April 11, 2012, 08:32:40 am
Fair enough. All good points.
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: garrettwp on April 15, 2012, 04:56:25 am
A new beta has been released (Beta 6). This release it to fix the bugs that were sent to me via the crash reporting utility. It also fixes some memory leaks. Minor UI adjustments were done as well.

I have been extremely busy the last month with work (working long 7 day weeks) and recovering from being sick. Hopefully I can get some free time to add a few more features before a final release. Let me know if you have any problems.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: S-F on April 15, 2012, 06:26:08 pm
Thanks for the option to control the tiles for dimmers. It' been rock solid for me. In fact I think it might be the most solid app I use. I'll of course let you know if there is anything wonkey with the new release.

Thanks for all your hard work.
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: Odeen on April 16, 2012, 04:50:39 pm
Hi Garrett,

I'm happy to report that Beta 6 runs swimmingly over Wimax.  I don't need to disable 4G anymore.  :)

Thanks!!
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: grybrd on April 16, 2012, 06:27:19 pm
Question from the guy who waits on all fixes so the family factor is steady .... when is this going to app android store?????
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: garrettwp on April 17, 2012, 12:30:38 am
Hopefully in the very near future. At this stage the app is pretty stable and if anything more stable than the official release on the market.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: sirkro on April 17, 2012, 02:29:39 am
Newest beta is awesome :)

I got a power meter from North-Q that fives me current Kwh. Could you make it possible to show that on a power device? Currently it only shows Watt.
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: cokeman on April 17, 2012, 02:33:07 am

I got a power meter from North-Q that fives me current Kwh. Could you make it possible to show that on a power device? Currently it only shows Watt.

The Kamstrup power meter is the same, only shows the Watt and not the KWH...  :-\

/Cokeman
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: sirkro on April 17, 2012, 02:48:51 am
And if you add this to <application android:hardwareAccelerated="true" and compile with sdk 4.x, animations will be quite smooth on android 4.x devices.  :)

The app will still be compatible with older versions of android.
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: garrettwp on April 17, 2012, 03:50:08 am
Newest beta is awesome :)

I got a power meter from North-Q that fives me current Kwh. Could you make it possible to show that on a power device? Currently it only shows Watt.

Can you provide me the lu_sdata so I can see what the values look like?

UPDATE:

I had cokeman's lu_sdata and looked at the power meter. I'll add that to the list.

And if you add this to <application android:hardwareAccelerated="true" and compile with sdk 4.x, animations will be quite smooth on android 4.x devices.  :)

The app will still be compatible with older versions of android.

Hardware acceleration is already enabled in the manifest.

- Garrett

p.s. I found a few more bugs that were reported by the crash reporting tool. I have (hopefully) fixed those bugs.
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: cokeman on April 17, 2012, 06:52:20 am
Sounds great...

Need an Alfa tester, then let me know :D

/cokeman
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: garrettwp on April 18, 2012, 11:49:31 am
I want to apologize to everyone. It looks like the last build created new bugs and stability issues. This was caused by fixing the memory leaks. I had to rewrite some code throughout the app to fix them. The crash report utility is helping me track them down. Sorry for the bad user experience. I'll try and get out a new release by this weekend. On the bright side I'm glad I got the memory leaks fixed. I'd rather have it break now than later.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: radarengineer on April 18, 2012, 11:29:50 pm
@garrettwp, I have this running on four devices (two sprint evo 3ds, an old elocity A7 tablet running 2.2, and a logitech revue). I've been testing most new versions on each of these and recently generating quite a few crash reports. I can't quite tell what is crashing or I would post about it.

I don't really mind the crashes so much, I just wanted to make sure that I'm not flooding you with two many crash reports. It sounds like from your last post that isn't a problem. As long as that isn't the case I'll keep doing my best to find bugs.
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: garrettwp on April 19, 2012, 12:05:34 am
Thanks for the info. Are the crashes happening mostly from the latest build? The reports help me a great deal, so use it like you normally would. I fixed the bugs that I received in the last few days. Most of these bugs are from the changes I had to make to correct the memory leaks and are more or less simple syntax mistakes. I'll try and get a newer build out this weekend and hopefully with a few more goodies added.

All in all, besides the crashes, how is it performing as a whole? Let me know if you have any questions, suggestions and comments.

- Garrett

Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: capjay on April 20, 2012, 01:35:27 pm
Amazing work!

Just a quick feature request: supporting virtual switches. I use them a lot as manual parameters to my scenes, and I imagine adding support for them would be trivial.
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: garrettwp on April 20, 2012, 02:03:39 pm
Amazing work!

Just a quick feature request: supporting virtual switches. I use them a lot as manual parameters to my scenes, and I imagine adding support for them would be trivial.

Thank you for the comment.  As for the virtual switches, if you are referring to the virtual switch plugin, I would love to add support. However, currently the data that I use lu_sdata does not have the required info that I need to distinguish the virtual switch plugin as well as other plugins. So support for 3rd party plugins are limited until MCV adds the required support that I have requested. As soon as they add the support that I need, supporting 3rd party plugins will happen. There are a few threads mentioning this and I do hope MCV can get this request in. One other issue is that if/when they do add this, it will most likely only be available in the next firmware of UI5.

- Garrett

p.s. A workaround would be not use the virutal switch plugin and create the virtual device doing the following:

UI5:

1. Upload the following file I_VirtualSwitch.xml:
    1. Click on Apps -> Developer Apps -> Luup Files
    2. Upload the file in the upload section on the right (no need to restart luup)

2. Click on Create Device
3. In the Device Type box enter: urn:schemas-upnp-org:device:BinaryLight:1
4. In the Upnp Device Filename enter: D_BinaryLight1.xml
5. In the Upnp Implementation Filename enter: I_VirtualSwitch.xml
6. Click on Create Device (a pop up should pop up saying device has been created)
7. Click on the Reload  to restart the luup engine.
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: drag0n on April 21, 2012, 02:28:52 pm
Thanks for you great work! This app is amazing  :)
Beta 6 has broken tablet view on my Kindle Fire. Multiple crash reports have been sent
Title: Re: Public Beta Build of Version 2.0 Beta 6
Post by: garrettwp on April 21, 2012, 02:35:14 pm
I'm aware of the issue and have hopefully fixed it. It will be in the next beta.

Thanks for the good words.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: garrettwp on April 24, 2012, 12:27:26 am
Beta 7 has been released. Many bug fixes and force closure fixes. Also included voice recognition that is experimental.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: radarengineer on April 24, 2012, 06:51:53 pm
So far I'm having great luck with the voice control, and beta 7 seems to have fixed my crash problems.  :)
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: garrettwp on April 24, 2012, 09:39:18 pm
Great to hear is this on AutHomation or AutHomationHD? I will focus on fixing bugs and getting the voice recognition stable and will hopefully get this ready for official release.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: tomcat on April 24, 2012, 11:58:53 pm
....runing Beta 7 (for 2.3 and older) but I'm getting the "......dont understand the request" message...I've tried with the TURN..device name ON....but got the same message...  ....I think it is my English pronunciation....then I swicthed the initial name for its traduction in english (cocina = kitchen)..but nothing happens....

.....on the other hand....everything goes excellent
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: radarengineer on April 25, 2012, 10:44:16 am
This is on my Evo 3d so AutHomation. When I bought the phone we were promised ICS so hopefully soon I can switch to AutHomationHD in the future. I also have a Revue that is basically only used to run AutHomationHD on my TV, but as far as I know I can't test voice control with it :)
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: oTi@ on April 25, 2012, 10:45:00 pm
@garrettwp,

Beta 7 has been released.
Nice work! Finally got a chance to check out your app, running on ICS-based Android-x86 port on Intel Atom (Asus EeePC).
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: garrettwp on April 25, 2012, 11:56:22 pm
....runing Beta 7 (for 2.3 and older) but I'm getting the "......dont understand the request" message...I've tried with the TURN..device name ON....but got the same message...  ....I think it is my English pronunciation....then I swicthed the initial name for its traduction in english (cocina = kitchen)..but nothing happens....

.....on the other hand....everything goes excellent

I am not sure if there is anything I can do. I am using google's voice to text api's and it is dependent on the returned data for parsing. It has been functioning great for me (though my native language is English). I know radarengineer also said it has been working fine for him. Anyone with English being their second language, have they given the voice recognition a try?

This is on my Evo 3d so AutHomation. When I bought the phone we were promised ICS so hopefully soon I can switch to AutHomationHD in the future. I also have a Revue that is basically only used to run AutHomationHD on my TV, but as far as I know I can't test voice control with it :)

I am glad to hear that the voice recognition is working great on Android 2.3 and older. Since I do not have a device that runs anything lower than Android 3.1, I can only rely on the android emulator. The emulator does not contain the software for the voice recognition. So testing the voice recognition feature is pretty non existent on the older platform. I am trying to get more function added and will hopefully have it in the next release.

@garrettwp,

Beta 7 has been released.
Nice work! Finally got a chance to check out your app, running on ICS-based Android-x86 port on Intel Atom (Asus EeePC).

Glad to see that it is functioning on the EeePC. Thanks for bringing up the issues with it not running. It allowed me to make the changes needed to support more devices. The last few builds have been a little rocky due to the new bugs that I introduced when fixing the memory leaks. But I am trying my best to get them ironed out. A new bug was reported to me earlier in the day for AutHomationHD that causes the app to crash when trying to move a device to another room. I have fixed this bug and that will be in the next release.

I am not trying to focus on getting the bugs ironed out and getting this release ready for the market. If anyone has any issues or something that needs to be tweaked, please let me know.

- Garrett

Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: radarengineer on April 27, 2012, 11:22:51 am
@garrettwp, I noticed with a few devices that I have (ones with long names?) "turn on <device_name>" works but "turn <device_name> on" does not. My device names are currently pretty bad for voice recognition. Everything is "<roomname> lamp", "<roomname> overhead", etc. Lots of name collisions! I have not done extensive testing, but I've been doing more and more control with voice commands and it is great.

I have three devices running 2.3 (Droid 2 Global and two Evo 3ds) I'm quite happy to help with testing in any way that would be helpful (for instance, renaming my devices, or running an exhausting list of commands, etc).
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: garrettwp on April 27, 2012, 12:19:18 pm
@garrettwp, I noticed with a few devices that I have (ones with long names?) "turn on <device_name>" works but "turn <device_name> on" does not. My device names are currently pretty bad for voice recognition. Everything is "<roomname> lamp", "<roomname> overhead", etc. Lots of name collisions! I have not done extensive testing, but I've been doing more and more control with voice commands and it is great.

I have three devices running 2.3 (Droid 2 Global and two Evo 3ds) I'm quite happy to help with testing in any way that would be helpful (for instance, renaming my devices, or running an exhausting list of commands, etc).

I have also been doing a lot of voice control as well (not only for testing but for day to day use). It has been performing pretty well for me as well. It helps to keep the device names simple, however you can say part of the name. For example if the name of the device is Kitchen Cabinet Lights, you can say [Turn On] Cabinet Lights or [Turn On] Kitchen Cabinet. As long as you say part of the name it should find any devices that contain that name and present a list if more than one is found.  I am still tweaking and it will get better in the future.

I am trying to add more commands. The more I use it, I come up with more ideas and add them. I have now added control of thermostats and more status commands e.g. battery level, etc. More to come. I still need to write documentation for this as well.

If you have any suggestions or something you like to see in the voice recognition, please let me know. I should have an update released tonight / tomorrow that will fix more bugs and contain additional voice commands.

- Garrett

P.S. I have stopped adding any new features  and will focus on getting the bugs worked out and finishing the voice recognition. Once everything seems pretty stable (hopefully soon), I will release to the market. I plan to have widgets, camera streaming, and other features in future releases (2.1 and newer).
Title: 3-in-1 not shown
Post by: conchordian on April 28, 2012, 12:54:50 am
Have you tried the beta version of AutHomation?

- Garrett

I have now, thanks, and it's much better.  It doesn't pick up the temperature & light level of my 3 in 1 motion sensor (http://zwave.com.au/index.php?_a=viewProd&productId=19 (http://zwave.com.au/index.php?_a=viewProd&productId=19)) though, unfortunately.
Title: Re: 3-in-1 not shown
Post by: garrettwp on April 28, 2012, 01:14:53 am
Have you tried the beta version of AutHomation?

- Garrett

I have now, thanks, and it's much better.  It doesn't pick up the temperature & light level of my 3 in 1 motion sensor (http://zwave.com.au/index.php?_a=viewProd&productId=19 (http://zwave.com.au/index.php?_a=viewProd&productId=19)) though, unfortunately.

Would you be willing to provide me your lu_sdata and an image of the device that is displayed by vera's control panel? I can than add support.

- Garrett
Title: Re: 3-in-1 not shown
Post by: conchordian on April 28, 2012, 02:45:07 am
The relevant devices are:
Motion Sensor, LightSensor and TemperatureSensor.  Not sure if you need the movement icon, or not so there's both.
http://i.imgur.com/Fp1nY.gif  (http://i.imgur.com/Fp1nY.gif)
http://i.imgur.com/e25YN.gif (http://i.imgur.com/e25YN.gif)

I'm not sure how to give you my lu-sdata, but I'm happy to provide it, if you let me know how. :)

Cheers
Title: Re: 3-in-1 not shown
Post by: garrettwp on April 28, 2012, 04:07:31 am
The relevant devices are:
Motion Sensor, LightSensor and TemperatureSensor.  Not sure if you need the movement icon, or not so there's both.
http://i.imgur.com/Fp1nY.gif  (http://i.imgur.com/Fp1nY.gif)
http://i.imgur.com/e25YN.gif (http://i.imgur.com/e25YN.gif)

I'm not sure how to give you my lu-sdata, but I'm happy to provide it, if you let me know how. :)

Cheers

You can retrieve the lu_sdata by going to the following link:

http://ip:3480/data_request?id=lu_sdata

Where ip is the vera ip address. Before you send it off, please go through the data and carefully remove any passwords or sensitive data you might have. You can take the data and put it into a json formatter found here: http://jsonformatter.curiousconcept.com/ to have the data be easily readable. You can than send the data to authomation at garrettpower.com.

What has me baffled is that by looking at the pictures, they look like normal temperature and light sensor devices. AutHomation should have no problem picking them up.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: grybrd on April 28, 2012, 03:48:17 pm
OK ... 'he' who waits till things are released had to download your beta app.  Thanks for such a great update!!!   Tried the speech thing and it will turn on a light but not turn it off ... get the ole don't understand message.  Garrett thanks again the family will like it too.

Doug
Title: Re: 3-in-1 not shown
Post by: conchordian on April 28, 2012, 08:59:37 pm
You can retrieve the lu_sdata by going to the following link:

http://ip:3480/data_request?id=lu_sdata

Where ip is the vera ip address. Before you send it off, please go through the data and carefully remove any passwords or sensitive data you might have. You can take the data and put it into a json formatter found here: http://jsonformatter.curiousconcept.com/ to have the data be easily readable. You can than send the data to authomation at garrettpower.com.

What has me baffled is that by looking at the pictures, they look like normal temperature and light sensor devices. AutHomation should have no problem picking them up.

- Garrett

OK, I've sent you an email with that data.  I also noticed setting the default page to 'Favourites' doesn't seem to work when the app loads.

The voice recognition is cool, but the 'beep' seems to interfere when waiting, if that makes sense.

Thanks for your help.
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: garrettwp on April 29, 2012, 12:48:59 am
OK ... 'he' who waits till things are released had to download your beta app.  Thanks for such a great update!!!   Tried the speech thing and it will turn on a light but not turn it off ... get the ole don't understand message.  Garrett thanks again the family will like it too.

Doug

The voice recognition can take some getting use to. Speaking clearly and not too fast seems to be the key. Once you get the voice commands down, it should work pretty well. It has been pretty flawless for me.

- Garrett
Title: Re: 3-in-1 not shown
Post by: garrettwp on April 29, 2012, 12:54:42 am
You can retrieve the lu_sdata by going to the following link:

http://ip:3480/data_request?id=lu_sdata

Where ip is the vera ip address. Before you send it off, please go through the data and carefully remove any passwords or sensitive data you might have. You can take the data and put it into a json formatter found here: http://jsonformatter.curiousconcept.com/ to have the data be easily readable. You can than send the data to authomation at garrettpower.com.

What has me baffled is that by looking at the pictures, they look like normal temperature and light sensor devices. AutHomation should have no problem picking them up.

- Garrett

OK, I've sent you an email with that data.  I also noticed setting the default page to 'Favourites' doesn't seem to work when the app loads.

The voice recognition is cool, but the 'beep' seems to interfere when waiting, if that makes sense.

Thanks for your help.

I got your email and will look into what is going on with the 3-in-1 device. As for the favorites tab, this is only available for tablet layout. I made a change to the settings section stating this. As for the beep, what do you mean when waiting? I need to fine tune the voice recognition UI more, but what happens is when the dialog loads up, it initializes the voice api's and the text to speech. Once that is ready, it will beep and than allow the microphone to start listening to audio and you can start speaking.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on April 29, 2012, 01:14:32 am
Beta 8 has been released. It addresses bug fixes that were reported in the last week and added additional voice recognition commands. I also forgot to mention that the voice recognition portion of the app can accessed via a home screen widget. It is just an icon that allows for direct access to the voice recognition. It can be added by adding a new widget to the home screen and selecting "AutHomation VR / AutHomationHD VR".

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: PurdueGuy on April 29, 2012, 02:58:34 am
Garrett,

I know this is a totally unsupported hack, but the Kindle Fire can use an iPhone style headset/microphone and can make use of the mic.  It doesn't work out of the box, but I was able to follow directions here: http://kindlefireboss.blogspot.com/2012/02/control-your-kindle-fire-by-voice-what.html and get that portion working (you don't need to install the voice actions, just google voice).  I then installed a free audio note taking application, and it worked!

Before I installed the above, when I tapped the microphone, I would get a gold mic with "Voice recognition not available!" which I expected.

So I installed the Google Now I get a green might with "Initializing..."  I hit "Speak Now", the mic turns red/dings/"Ready for Speech"...I try "Turn on kitchen" and after a little while I get "No speech input."

I was doing further reading, and some people mentioned that the Kindle Fire can ONLY handle half-duplex.  So it can't play audio at the same time that it's recording audio.  With the test application and headphones, I can hear the headphones being turned off just before the recording is started.  However, with AutHomation (not HD), the headphones are still active, even though no sound is coming out.  I think that means the Kindle isn't really receiving any audio from the mic.  Is is possible to turn off the audio output just prior to starting the recording?

BTW: This was Beta 8.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on April 29, 2012, 05:03:06 am
Garrett,

I know this is a totally unsupported hack, but the Kindle Fire can use an iPhone style headset/microphone and can make use of the mic.  It doesn't work out of the box, but I was able to follow directions here: http://kindlefireboss.blogspot.com/2012/02/control-your-kindle-fire-by-voice-what.html and get that portion working (you don't need to install the voice actions, just google voice).  I then installed a free audio note taking application, and it worked!

Before I installed the above, when I tapped the microphone, I would get a gold mic with "Voice recognition not available!" which I expected.

So I installed the Google Now I get a green might with "Initializing..."  I hit "Speak Now", the mic turns red/dings/"Ready for Speech"...I try "Turn on kitchen" and after a little while I get "No speech input."

I was doing further reading, and some people mentioned that the Kindle Fire can ONLY handle half-duplex.  So it can't play audio at the same time that it's recording audio.  With the test application and headphones, I can hear the headphones being turned off just before the recording is started.  However, with AutHomation (not HD), the headphones are still active, even though no sound is coming out.  I think that means the Kindle isn't really receiving any audio from the mic.  Is is possible to turn off the audio output just prior to starting the recording?

BTW: This was Beta 8.

Thanks for the info. Let me try a few modifications and I'll send you a different build to test and see if we can get it working.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: grybrd on April 29, 2012, 11:40:03 am
OK ... 'he' who waits till things are released had to download your beta app.  Thanks for such a great update!!!   Tried the speech thing and it will turn on a light but not turn it off ... get the ole don't understand message.  Garrett thanks again the family will like it too.

Doug

The voice recognition can take some getting use to. Speaking clearly and not too fast seems to be the key. Once you get the voice commands down, it should work pretty well. It has been pretty flawless for me.

- Garrett

It must be the Minnesota accent ... will try real English to see if that helps .... LOL
Title: Re: Public Beta Build of Version 2.0 Beta 7
Post by: tomcat on April 29, 2012, 01:10:35 pm
(beta 8  )
.....Finally I could turn On / Off a power outlet, , Lock / unlock a Yale bolt.... but before that , I had to change the default language of the voice recognition settings to English (US),....then replace the device name for its English traduction and it worked, one thing I really liked was the option to "pick an action" ( even show you a list of the devices) .....when the voice command recognizes part of the command ....so anyone with English being their second language should do what I did or wait for a future release with this feature (Spanish language)  ;) hehe.......
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: BOFH on April 29, 2012, 02:45:19 pm
Installed Authomation beta on a ZT180 (Zenithink ChiPad) 7" running Android 2.2. Recognizes my GE and Intermatic devices and lets me control them. Sees my Trane thermostat and shows the correct values. Sees and allows me to control my Schalge lever and deadbolt locks.

Installed AuthomationHD on an HP Touchpad running CM( (ICS) Recognizes my GE and Intermatic devices and lets me control them. Sees my Trane thermostat and shows the correct values. Sees and allows me to control my Schalge lever and deadbolt locks.

Voice recognition is not available on either device. :-(  Still, this app rocks! Thank You!

I only have one request. :-) an iPhone version!

Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: PurdueGuy on April 30, 2012, 03:09:10 am
I was all set to try to put Ice Cream Sandwich on my TouchPad this weekend to try out voice recognition, but then I read that the microphone is supported, since they are changing all the audio stuff.  :-(
Title: Re: 3-in-1 not shown
Post by: garrettwp on April 30, 2012, 06:49:06 am
You can retrieve the lu_sdata by going to the following link:

http://ip:3480/data_request?id=lu_sdata

Where ip is the vera ip address. Before you send it off, please go through the data and carefully remove any passwords or sensitive data you might have. You can take the data and put it into a json formatter found here: http://jsonformatter.curiousconcept.com/ to have the data be easily readable. You can than send the data to authomation at garrettpower.com.

What has me baffled is that by looking at the pictures, they look like normal temperature and light sensor devices. AutHomation should have no problem picking them up.

- Garrett

OK, I've sent you an email with that data.  I also noticed setting the default page to 'Favourites' doesn't seem to work when the app loads.

The voice recognition is cool, but the 'beep' seems to interfere when waiting, if that makes sense.

Thanks for your help.

I looked at your data and it appears that your temperature sensor and light sensor are set up as a generic i/o device. In the device settings for the temperature and light sensor, what is the device file set to?

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: conchordian on April 30, 2012, 11:43:19 pm
Here they are:
http://i.imgur.com/lwtdE.gif (http://i.imgur.com/lwtdE.gif)
http://i.imgur.com/dTMdj.gif (http://i.imgur.com/dTMdj.gif)

I forgot to clarify what I meant by the beep of voice recognition interfering.  When the voice recognition is ready to receive input it plays a 'ding', but unfortunately that sound is analysed by the software as a command before a proper one can be spoken.

I also noticed when using Android 2.3, and clicking on favourites, the screen snaps to the bottom and you can't pick the menu items above, until you press the options button, (the one with the three lines, whatever it's called).  As soon as you press that, the page justifies itself correctly.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on May 01, 2012, 12:46:49 am
Here they are:
http://i.imgur.com/lwtdE.gif (http://i.imgur.com/lwtdE.gif)
http://i.imgur.com/dTMdj.gif (http://i.imgur.com/dTMdj.gif)

I forgot to clarify what I meant by the beep of voice recognition interfering.  When the voice recognition is ready to receive input it plays a 'ding', but unfortunately that sound is analysed by the software as a command before a proper one can be spoken.

I also noticed when using Android 2.3, and clicking on favourites, the screen snaps to the bottom and you can't pick the menu items above, until you press the options button, (the one with the three lines, whatever it's called).  As soon as you press that, the page justifies itself correctly.

Thanks for the images. Not sure why the devices are showing as generic i/o and not as light and temperature sensors. As for the beep, it should not interfere with the recognition. Before the beep, the microphone is muted and after the beep is finished, the microphone is un-muted to prevent any interference. As I do not have any devices right now running android 2.3 or older, It is hard for me to test.

As for the favorites, can you clarify a little more? Are you referring to the menu when you long press on one of the items?

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: conchordian on May 01, 2012, 02:08:17 am
It's almost as if it's unmuting a bit too soon.  I wonder if I can get into something like 'system sounds' and replace it with a shorter beep, or one with less reverb.

I'm not sure if it's just limited to favourites, (I'll check), but up the top of the screen is a list with things like rooms, scenes, etc. and only half of their words are being displayed because the screen has scrolled down to the very bottom, even though there's only a couple of devices in favourites and plenty of room on the screen to display them without scrolling down.  When you press the options button the screen scrolls up, or refocuses, and you can read all the menu items properly up the top.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on May 01, 2012, 02:38:37 am
It's almost as if it's unmuting a bit too soon.  I wonder if I can get into something like 'system sounds' and replace it with a shorter beep, or one with less reverb.

I'm not sure if it's just limited to favourites, (I'll check), but up the top of the screen is a list with things like rooms, scenes, etc. and only half of their words are being displayed because the screen has scrolled down to the very bottom, even though there's only a couple of devices in favourites and plenty of room on the screen to display them without scrolling down.  When you press the options button the screen scrolls up, or refocuses, and you can read all the menu items properly up the top.

What type of device is this running on? Is the on a phone or tablet? If this is on a phone, there should not be anything on top. The favorites section should look like the following image attached. As for the beep, this can not be changed as this is coded into the app. The beep plays via the android media player api calls, when the player is done playing the beep, it will un-mute the microphone. There is an api call for the mediaplayer that gets called when it is done playing the sound. I am using this to know when it is done playing the beep to un-mute the microphone.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Odeen on May 03, 2012, 03:32:36 am
Garrett,

2.0 Beta 8 has the WiMax  bug again.  I have no data connection if 4G is enabled on my Sprint phone.  Have to use Beta 6 for now.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: cokeman on May 03, 2012, 03:41:08 am
Hi Garrett,

How about the KWH reading, will that make it to the beta 9 ?

/Cokeman

Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: conchordian on May 03, 2012, 04:04:51 am
What type of device is this running on? Is the on a phone or tablet? If this is on a phone, there should not be anything on top. The favorites section should look like the following image attached. As for the beep, this can not be changed as this is coded into the app. The beep plays via the android media player api calls, when the player is done playing the beep, it will un-mute the microphone. There is an api call for the mediaplayer that gets called when it is done playing the sound. I am using this to know when it is done playing the beep to un-mute the microphone.

- Garrett

Tablet running 2.3

http://i.imgur.com/PE6ec.jpg (http://i.imgur.com/PE6ec.jpg) is pic  of the menu items being chopped.

Cheers
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on May 03, 2012, 05:06:42 am
Garrett,

2.0 Beta 8 has the WiMax  bug again.  I have no data connection if 4G is enabled on my Sprint phone.  Have to use Beta 6 for now.

Nothing has changed between 6 and 8 for the connection checking. Since I do not have wimax in my area, I can not physically check this on my sprint phone. So trying to trouble shoot this will be an issue. When you enable wimax, are any of the other radios enabled? I would like to find out what is going on with this and fix it for you.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on May 03, 2012, 05:10:43 am
Hi Garrett,

How about the KWH reading, will that make it to the beta 9 ?

/Cokeman

It is on my list, not sure if it will make the next beta. I need to change things around on the backend for the data and that would also require me to make changes to a few other things in the app. I still need to go about how I want to add the extra data in.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on May 03, 2012, 05:11:45 am
What type of device is this running on? Is the on a phone or tablet? If this is on a phone, there should not be anything on top. The favorites section should look like the following image attached. As for the beep, this can not be changed as this is coded into the app. The beep plays via the android media player api calls, when the player is done playing the beep, it will un-mute the microphone. There is an api call for the mediaplayer that gets called when it is done playing the sound. I am using this to know when it is done playing the beep to un-mute the microphone.

- Garrett

Tablet running 2.3

http://i.imgur.com/PE6ec.jpg (http://i.imgur.com/PE6ec.jpg) is pic  of the menu items being chopped.

Cheers

What is the black bar at the bottom? This is not part of the app and is the cause of the app having the top portion cut off. Does this happen only when first loading of the app or during the operation of the app? It seems like the menu bar for android is not properly hiding itself to allow the app to go into full screen mode.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Odeen on May 03, 2012, 09:18:06 am
Garrett,

2.0 Beta 8 has the WiMax  bug again.  I have no data connection if 4G is enabled on my Sprint phone.  Have to use Beta 6 for now.

Nothing has changed between 6 and 8 for the connection checking. Since I do not have wimax in my area, I can not physically check this on my sprint phone. So trying to trouble shoot this will be an issue. When you enable wimax, are any of the other radios enabled? I would like to find out what is going on with this and fix it for you.

- Garrett

Thanks.  :)

The Wi-Fi and Wimax radios are mutually exclusive.  Wimax radio disables itself if Wi-Fi is turned on and connected.  The 3G radio is always active.
So, any time Wimax radio is active, AutHomation 2.0 B8 keeps giving a "No Data Connection".  With both WiFi and Wimax disabled, it works fine over 3G.  With WiFi enabled, it works fine in local connection mode.

Also, when I try to auto-configure while Wimax is active, I get a "NO INTERNET CONNECTION: There is no internet connection.  Please enable an internet connection" dialog box.

With only 3G enabled, everything seems to work.  Switching between Wifi and 3G switches AutHomation between local and remote connection modes.  It seems to behave exactly like Beta 5.

Unrelated:
1) it was really convenient to have 6 device tiles per screen in Beta 6.  I can't find a way to enable that in Beta 8...
2) Upgrading from Beta 6 to Beta 8, all my devices disappeared.  I had to clear the cache and reconfigure my password, etc. to get them to appear again.  Weird.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on May 03, 2012, 10:37:40 pm
Garrett,

2.0 Beta 8 has the WiMax  bug again.  I have no data connection if 4G is enabled on my Sprint phone.  Have to use Beta 6 for now.

Nothing has changed between 6 and 8 for the connection checking. Since I do not have wimax in my area, I can not physically check this on my sprint phone. So trying to trouble shoot this will be an issue. When you enable wimax, are any of the other radios enabled? I would like to find out what is going on with this and fix it for you.

- Garrett

Thanks.  :)

The Wi-Fi and Wimax radios are mutually exclusive.  Wimax radio disables itself if Wi-Fi is turned on and connected.  The 3G radio is always active.
So, any time Wimax radio is active, AutHomation 2.0 B8 keeps giving a "No Data Connection".  With both WiFi and Wimax disabled, it works fine over 3G.  With WiFi enabled, it works fine in local connection mode.

Also, when I try to auto-configure while Wimax is active, I get a "NO INTERNET CONNECTION: There is no internet connection.  Please enable an internet connection" dialog box.

With only 3G enabled, everything seems to work.  Switching between Wifi and 3G switches AutHomation between local and remote connection modes.  It seems to behave exactly like Beta 5.

Unrelated:
1) it was really convenient to have 6 device tiles per screen in Beta 6.  I can't find a way to enable that in Beta 8...
2) Upgrading from Beta 6 to Beta 8, all my devices disappeared.  I had to clear the cache and reconfigure my password, etc. to get them to appear again.  Weird.

Something is not adding up here. The number of tiles did not change between betas. Beta 8 still showed 6 tiles for phones that have a screen resolution of 800x480. I have attached an example of what beta 8 looks like. Did you go to the correct link to download beta 8?

https://www.wuala.com/garrettwp/Android/AutHomation/Public%20Test/?key=cqDXsXIbSidI

Can you try and install beta 8 again and see if the problems still persist? It sounds to me like you ended up installing an older version some how.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: conchordian on May 03, 2012, 11:26:36 pm
What is the black bar at the bottom? This is not part of the app and is the cause of the app having the top portion cut off. Does this happen only when first loading of the app or during the operation of the app? It seems like the menu bar for android is not properly hiding itself to allow the app to go into full screen mode.

- Garrett

It is the status bar that displays things like the Wi-Fi signal strength, clock, Bluetooth symbol, etc.

When you first load the app it looks like it tries to hide it, in that all the icons, clock, etc. disappear, but the black line remains as you can see in the picture.  As soon as you press the button to "Access Settings, Auto Config, Unit Info, About", the black bar disappears and the screen refocuses properly.

From then on the black bar doesn't reappear and you can read the title bar at the top.

Cheers 

Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Odeen on May 04, 2012, 05:57:36 pm
Something is not adding up here. The number of tiles did not change between betas. Beta 8 still showed 6 tiles for phones that have a screen resolution of 800x480. I have attached an example of what beta 8 looks like. Did you go to the correct link to download beta 8?

https://www.wuala.com/garrettwp/Android/AutHomation/Public%20Test/?key=cqDXsXIbSidI

Can you try and install beta 8 again and see if the problems still persist? It sounds to me like you ended up installing an older version some how.

- Garrett

You're RIGHT.  I somehow managed to download an older version of the Authomation.apk.  The file shows as having been downloaded 5 days ago, but it's clearly older than Beta 6.

Beta 8, however, has issues with ALL Internet access to the Vera.  Initially, it crashed with the 4G radio enabled, and simply gave a "no Internet access" error when I disabled 4G and ran on 3G only.
You should have a few crash reports from around 2:10-2:20 PM, Pacific time.


Now, it runs on 4G, but does NOT detect the 3G data connection
Here is the procedure I used to reinstall:
WiFi, 3G enabled, 4G radio disabled

Task Manager - Kill AutHomation, then close all active applications
Settings - Applications - Manage Applications - Authomation
* Clear Data
* Uninstall

Installed the latest AutHomation.apk. 
Verified application version 2.0.1.8 through Manage Applications.

Launched AutHomation
Connection Settings - Auto Configure (to configure for local operation)
Password - <MIOS password>
Remember Network
Auto Connection Switching - Check

Verified local operation
Disabled WiFi (Now using 3G radio only)
Switched back to AutHomation and...  "No data connection"
Noticed that I was still in "Local" mode - switched to "remote" connection type
Tried turning a light on...  and still no data connection.

Tried restarting AutHomation - no change
Turned on WiFi - AutHomation stayed in remote connection mode
Switched to Local mode, and it works again.


Note: The web browser works while on 3G, so it's not a phone connectivity issue.

Weird.  Beta 6 has no connection issues, and always seems to be in the right connection mode.

If you could send me a build with extra logging features, I'd be happy to install it, and run it with Wi-Fi, 3G and 4G enabled.  Hopefully it'll give you some idea about what's going on.  Otherwise, I can understand how hard it is to troubleshoot something remotely, and running on a platform with its own idiosyncrasies (like WiMax).  :)
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Da_JoJo on May 04, 2012, 06:16:36 pm
ow yeah this is nice men !
i missed a few weeks here and found you've added speech recognition. awesome !
and yes it works on my dell streak running android 2.2.2 with loquendo TTS susan speechvoice
the speechrecognition was not that great, but after i found out it was set to dutch language and i had put this on english it worked so much better lol
really like this be-lazy-and-enjoy functionality.
mobile data <> local wifi  auto-switching is working better now vs beta4 i had before this beta8.
overall speed improved a lot
had 1 crash (getting used to it lol) probably this exotic database running on the device or the 200+ apps)
funny thing is, the authomation prog resets and continues where it left working fine. pretty neat.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Aaron on May 07, 2012, 11:46:59 am
garrettwp
I just tried the latest beta... it seems much more responsive. Nice work.

One request... I really like the UI overall except when choosing a device/event, it opens a popup - this adds two unnecessary actions/presses (extra one for opening the popup, and closing it).  I ask that you allow control of the events/devices directly from the main screen and remove the popups - or provide that as a switchable option in the settings. Thank you.

thanks for the great app!
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: S-F on May 07, 2012, 04:56:24 pm
garrettwp
I just tried the latest beta... it seems much more responsive. Nice work.

One request... I really like the UI overall except when choosing a device/event, it opens a popup - this adds two unnecessary actions/presses (extra one for opening the popup, and closing it).  I ask that you allow control of the events/devices directly from the main screen and remove the popups - or provide that as a switchable option in the settings. Thank you.

thanks for the great app!

We've already been through that one. To a certain degree you can control what is displayed on the tiles.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: capjay on May 08, 2012, 05:41:53 am
One request... I really like the UI overall except when choosing a device/event, it opens a popup

I find the popup useful, it displays some extra info, like actual battery percentage for example.



Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Aaron on May 08, 2012, 05:13:34 pm
garrettwp
I just tried the latest beta... it seems much more responsive. Nice work.

One request... I really like the UI overall except when choosing a device/event, it opens a popup - this adds two unnecessary actions/presses (extra one for opening the popup, and closing it).  I ask that you allow control of the events/devices directly from the main screen and remove the popups - or provide that as a switchable option in the settings. Thank you.

thanks for the great app!

We've already been through that one. To a certain degree you can control what is displayed on the tiles.

I'll be more clear... PLEASE add an on/off  switch on the device panels. It is VERY wasteful to need to open panel just to turn a light on or off.  If you want to open the panel, just make it happen by touching the icon.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on May 09, 2012, 04:32:13 am
Sorry for being absent for the last few days. Been laying low trying to get things done around the house and relaxing a bit. I should have a minor update in the next day or two to fix any bugs that have been reported since the last beta and minor tweaks.

garrettwp
I just tried the latest beta... it seems much more responsive. Nice work.

One request... I really like the UI overall except when choosing a device/event, it opens a popup - this adds two unnecessary actions/presses (extra one for opening the popup, and closing it).  I ask that you allow control of the events/devices directly from the main screen and remove the popups - or provide that as a switchable option in the settings. Thank you.

thanks for the great app!

We've already been through that one. To a certain degree you can control what is displayed on the tiles.

I'll be more clear... PLEASE add an on/off  switch on the device panels. It is VERY wasteful to need to open panel just to turn a light on or off.  If you want to open the panel, just make it happen by touching the icon.

Not sure that I am understanding what the problem is. The tiles show what I call quick action buttons. So if you have a light device, it should show an on/off buttons with out having to open the popup. Same goes for other devices like dimmable lights, locks, security sensors, window coverings, and so on. See attached images. The reason for the popup windows for the devices is to allow for more information to be displayed for the device and controls that would not fit on the tiles. As there is no way to have dynamically sized tiles for each type of device. This is also to keep the tiles clean as possible and to also maintain a single UI between phones, tablets and googletv (makes my life much easier to maintain a single interface design between platforms).

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Aaron on May 12, 2012, 12:18:08 am
I have another request  ;D

can you add the room label to the panels,  or a partition the screens by room label when using All or Favorites?  Since,  unless one adds the room to the device name,  which would be redundant,  it will be impossible to know which "Light" belongs to what room.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on May 12, 2012, 12:22:07 am
I'll look into what I can do. I am trying my best not to clutter up the tiles as much as possible. What I usually do is add an abbreviation of the room to the title of the device. For example say I have a light in my master bedroom, I would us the letters MB in front of the device name (MB Main Light or MB Ceiling Fan). But let me see what I can come up with.

- Garrett

p.s. I am trying to have a new beta out in the next day or two.
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Aaron on May 12, 2012, 08:15:40 pm
cool, thx. having full labels would be great - guests don't understand abbreviations. Which brings me to another request... a 'guest mode' would be awesome.

Thought around how Guest Mode would work....
Guest Mode would need a password to turn on or off
Admins could hide not only devices but also tabs and rooms: Favorites, Scenes, Kitchen, Basement, etc


I'd like to place a tablet in the kitchen for guests to use and have your app running but "locked down" in Guest Mode. This would be sweet!

great work, looking forward to the next beta!
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Da_JoJo on May 13, 2012, 03:26:06 am
im still a happy user :-)
you could use a guest acccount on the vera, disabling possibility to change config and use this for the authomation but there is still an option to autoconfigure which gets the other users names from the device. Anyways it needs a  password.
running new 2.3.3 korean rom on my streak now and it made the prog run considerably faster. the voice-recognition also works a bit better.
my little brother came to me with his galaxy tab 7.7 and he told me he had find a program called  "tasker" with this program you can make taks for you android like when the gps is on a certain point start a program.
this made me think.. it would be nice to have such an option in the authomation prog.. when it reaches a certain point on gps > turn on lights and unlock the house and deactivate alarms. Or set a certain range or area which authomation responds on with turning on the heating or something like that.
 
 
 
 
 
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: baxy_AU on May 13, 2012, 04:44:11 am
I believe Home Buddy has Tasker integration so you can do exactly as you described.

Sent from my GT-P1000
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: Da_JoJo on May 13, 2012, 05:00:55 am
thnx
it was more a suggestion to new options for garretts program but it allways nice to have the functionality allready in the meanwhile
my little brother is very happy with the tasker program but i dont want to buy it. i rather see garretts program evolve into the best all-in-one solutions since i put a lot of time allready in it and i like it a lot :-)
Title: Re: Public Beta Build of Version 2.0 Beta 8
Post by: garrettwp on May 13, 2012, 07:20:18 am
I plan to have the ability to do what homebuddy does and allow you to activate a scene with tasker. This is on my list and will be added in future version of version 2, (2.1 maybe). It would be easier to allow the create of those actions via a scene in vera and have tasker activate the specified scene. I am trying to keep AutHomation more of a control type app and not a replacement for Vera. Glad you still like the app Da_JoJo. I hope others are getting good use out of it as well. I know it is not perfect, but I hope it meets everyones needs.

 I just uploaded a new build beta 9. I will post what has changed (mainly bug fixes).

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: Da_JoJo on May 14, 2012, 07:22:57 am
Just installed 9 beta and now im even more happy :-D
the speechrecognition is not waiting for initialisation anymore and i fiddled a bit with settings on the voice part in my android. it seems to work good with any speechvoice for the output of spoken voice.  speaking to the device works the best if one sets it to english US language and the voice to English(Generic).
at first start of the VR from the dashboard widget it doesnt seem to respond right all the time, but when i turn my screen from landscape to normal it resets the VR and then it works ok. i get confused sometimes whether if i can start speaking the command or not. sometimes i start talking and the VR tells me its ready and sometimes it just tell me it could understand : "im sorry bladiebla"   (kinda annoying to hear it 10 times if command not recognised , make this something like : request failed   or maybe even user-settable (i like to make it : Boss, i failed !)
i understand your view on the gps thing..maybe its the better way but the tasker prog dont even run on my dell streak :(
its not a big deal though . primary goal is usablity.
well maybe it is not perfect yet but you getting close  ;D
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 14, 2012, 08:09:27 am
I just put one of the android phones I have back on Android 2.3 (Gingerbread). It was running Ice Cream Sandwich. Hopefully this week I can have some time to test everything out. Most of the testing has been on my HTC Evo running Ice Cream and also on the Droid X on Ice Cream as well. Since the Droid X is a test phone and my HTC Evo will soon be another test phone (Replacing with HTC One X). I can have a few more devices to test running different versions of android.

I found that some of the manufactures do not follow the standards of Android. For example using the mute api function to mute the mic during the playing of the beep does not work on some handsets e.g. Droid X. It does work on my HTC Evo, Asus Transformer tablet, and Galaxy Nexus. I did some searching and found that other manufactures are hit or miss with this as well. Others are reporting similar issues. It really makes it hard to try and get the voice recognition to work 100% across all devices. That is the reason for putting in the option to disable the beeping sound before listening for speech.

I can add an option to allow the user to input their own phrase to speak when it can not recognize the command. Would take a whole of two seconds to add. I know what you man when it can get annoying. Sometimes I mispronounce the room name or mess up the speaking of the command and I get tired of hearing the voice saying the phrase. I can also add an option to disable the speech.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: chris66 on May 14, 2012, 08:10:33 am
Hello Garett, Great app!

What do you need to display a wind sensor, like Oregon WTGR800? I can see it through the RFXCOM interface, but not in your android solution.

Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: Da_JoJo on May 14, 2012, 08:52:11 am
still happening.. mostly after resume from standby of the phone. probably it gets confused as i have my wifi settings to automaticly connect to mobile internet whenever it looses wifi connection or is in standby.
its telling me it got an empty response.. not sure whats causing it. seems to have improved with latest version though.
 
found the problem.. when one has set the extra security on the vera it needs a login and password which somehow doesnt passthrough to the vera. when one opens the dashboard on local network with local ip and login to it, the problem dissapears and authomation works ok again. not sure what causing this, authomation , the vera itself or the portal.



edit: must be the portal since i experience same issue with firmware upgrade, it wont connect then ..only after loggin in local first with the http-login.
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: Da_JoJo on May 14, 2012, 08:56:44 am
....an option to allow the user to input their own phrase to speak when it can not recognize the command. Would take a whole of two seconds to add. I know what you man when it can get annoying. Sometimes I mispronounce the room name or mess up the speaking of the command and I get tired of hearing the voice saying the phrase. I can also add an option to disable the speech.

- Garrett
that would be even better :-)  disable or be able to set it to user defined phrase.


edit: while ur at it .. voice command for all on / all off  would be nice too
edit2: on the other hand one could make a scene where everything is being turned off and call it "Mi Shizzle"  and open VR and say : "run Mi Shizzle"  .. or "activate mi shizzle" it works but its ehh weird.. :-)

i have also a scene where it turns on light and heating for my pet .. i sorta dislike the idea of :  "execute my pet"
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 15, 2012, 02:52:02 am
Hello Garett, Great app!

What do you need to display a wind sensor, like Oregon WTGR800? I can see it through the RFXCOM interface, but not in your android solution.

3rd party plugins are hit or miss with AutHomation. If they use the standard vera device types it should show up fine. If the plugins use custom device types, I will need to add support for them and this can be tricky. MCV added a feature for me to be able to figure out the device type. This will be in UI5 firmware 1.5.372 or newer. I hope to implement this into AutHomtion in version 2.1.

If you can provide me your lu_sdata:

You can retrieve the lu_sdata by going to the following link:

http://ip:3480/data_request?id=lu_sdata

Where ip is the vera ip address. Before you send it off, please go through the data and carefully remove any passwords or sensitive data you might have. You can take the data and put it into a json formatter found here: http://jsonformatter.curiousconcept.com/ to have the data be easily readable. You can than send the data to authomation at garrettpower.com.

If the data is for the windspeed is in the lu_sdata and I can easily figure out how to distinguish the device, I can add it to AutHomation.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 15, 2012, 02:56:22 am
....an option to allow the user to input their own phrase to speak when it can not recognize the command. Would take a whole of two seconds to add. I know what you man when it can get annoying. Sometimes I mispronounce the room name or mess up the speaking of the command and I get tired of hearing the voice saying the phrase. I can also add an option to disable the speech.

- Garrett
that would be even better :-)  disable or be able to set it to user defined phrase.


edit: while ur at it .. voice command for all on / all off  would be nice too
edit2: on the other hand one could make a scene where everything is being turned off and call it "Mi Shizzle"  and open VR and say : "run Mi Shizzle"  .. or "activate mi shizzle" it works but its ehh weird.. :-)

i have also a scene where it turns on light and heating for my pet .. i sorta dislike the idea of :  "execute my pet"

Let me see what I can do. I just bought a new laptop and will not have everything transferred over until I receive some additional goodies to have installed. Hopefully if all goes well with this beta, I can publish it to the play store. Adding the the additional option should not have any effect on the app, so I am not worried that it will cause any regressions. I hear you on some of the pronouncing of the commands. Depending on the device names, it can get quite interesting lol.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: Da_JoJo on May 15, 2012, 04:29:20 am
a new laptop means building speed increase ^^
the naming convention is tricky, it will on a point damage user interaction by removing certain commands on the other hand it might need a look-over since there could be up to 256 devices attached to the vera.
the all-on and all-off  function shouldnt be much of a problem to impent since these are native commands and vera does support these.
you could make an extra tile for this like a  light-switch. since it needs a separate section for uncommon devices anyways might as well put it ther ?
it deserves a spot in de marktplaats :)
there are a lot of programs in the market that either crash or dont work greatly and this authomation has never let me down not even with the 2 time crash i actually experienced with the early beta build. for it to be on the market it is way more eaasy to update and maintain the prog. if it where to have a bug by accident it'll send a bug report anyways. besides you can allways blame the ui5 lol
 
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: baxy_AU on May 16, 2012, 08:13:20 am
Hi garrettwp
I have been using your app for a while now and have to say it is coming along fantastically...however I just noticed today, after changing my Aeon Labs motor controllers from D_DimmableLight to D_WindowCovering as described in this thread: http://forum.micasaverde.com/index.php/topic,5977.0.html
that these devices still appear as dimmable lights within AutHomation although they now appear as window coverings in UI4 and in Home Buddy.
Do you have any ideas why this is? btw I have tried removing and reinstalling and refreshing the app + data
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 16, 2012, 12:03:07 pm
Hi garrettwp
I have been using your app for a while now and have to say it is coming along fantastically...however I just noticed today, after changing my Aeon Labs motor controllers from D_DimmableLight to D_WindowCovering as described in this thread: http://forum.micasaverde.com/index.php/topic,5977.0.html
that these devices still appear as dimmable lights within AutHomation although they now appear as window coverings in UI4 and in Home Buddy.
Do you have any ideas why this is? btw I have tried removing and reinstalling and refreshing the app + data

Can you enlighten me and tell me what the device_type is set to? Is it set to urn:upnp-org:serviceId:WindowCovering1 or is it set to something like urn:upnp-org:serviceId:Dimming1? The way that AutHomation figures out what type of device it is, is by looking at the device category. It appears that your window covering has a category of 2 (dimmable light). Going by device categories is a limitation of the lu_sdata and MCV has added a feature for me that will be in a future UI5 release 1.5.372 or newer that will allow me to go by device types. This code will not be implemented into AutHomation until version 2.1. I am trying to get 2.0 out the door very very soon (hopefully by next week).

If you are willing to provide me your lu_sdata, I can have a peek and see what is going on.

You can retrieve the lu_sdata by going to the following link:

http://ip:3480/data_request?id=lu_sdata

Where ip is the vera ip address. Before you send it off, please go through the data and carefully remove any passwords or sensitive data you might have. You can take the data and put it into a json formatter found here: http://jsonformatter.curiousconcept.com/ to have the data be easily readable. You can than send the data to authomation at garrettpower.com.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: baxy_AU on May 16, 2012, 07:36:52 pm
Hi garrettwp
thanks for the tip, changing the D_DimmableLight to D_WindowCovering had also changed the device type to urn:upnp-org:serviceId:WindowCovering1 after saving. The category number however was still 2, I have now changed them all to 8 and all is good.
Off topic I have been thinking about upgrading my Vera2 to UI5 as there are a few new features but in your opinion, is UI5 on the Vera2 worth it yet (or will the Vera 2 ever be capable of a stable UI5 experience)?
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 17, 2012, 04:04:06 am
UI5 has come a long way since I started using it in the very early stages of development. For Vera 2, if you want to run UI5, it is recommended to have a usb flash drive to enable usb logging and also to enable swapping onto the usb drive as well to help with the lack of ram in the unit. Future builds of AutHomation will have features that can only work with UI5, it will still maintain compatibility with UI4, but some things will not function.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: baxy_AU on May 17, 2012, 06:37:44 am
I already use USB for logging, how do I enable swap to USB?

Also when upgrading do scenes remain intact or are they lost in the upgrade process? Do you have any other tips for upgrading?

Sorry for asking you in this thread but its sometimes difficult to find up-to-date information
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 17, 2012, 06:49:47 am
Have a look here:

http://wiki.micasaverde.com/index.php/USB_swapfile_creation

and here to activate it across a reboot:

http://forum.micasaverde.com/index.php/topic,8883.msg71591.html#msg71591

In the past when you do a firmware update, you would have to recreate the swap file. Not sure if this is the case with UI5 (have no need for it now).

- Garrett
Title: Re: Re: Public Beta Build of Version 2.0 Beta 9
Post by: baxy_AU on May 18, 2012, 04:34:03 am
Thanks for the links and information.
To get back on topic, I would like to +1 the idea of adding an ALL operator to the voice commands if possible so that the command will be sent for all device name matches
Eg: "set all dimmable lamps to 30%" or "close all shutters" etc

[/quote]
that would be even better :-)  disable or be able to set it to user defined phrase.


edit: while ur at it .. voice command for all on / all off  would be nice too
edit2: on the other hand one could make a scene where everything is being turned off and call it "Mi Shizzle"  and open VR and say : "run Mi Shizzle"  .. or "activate mi shizzle" it works but its ehh weird.. :-)

i have also a scene where it turns on light and heating for my pet .. i sorta dislike the idea of :  "execute my pet"
[/quote]

 2
Title: Re: Re: Public Beta Build of Version 2.0 Beta 9
Post by: baxy_AU on May 18, 2012, 04:35:00 am
Thanks for the links and information.
To get back on topic, I would like to +1 the idea of adding an ALL operator to the voice commands if possible so that the command will be sent for all device name matches
Eg: "set all dimmable lamps to 30%" or "close all shutters" etc

[/quote]
that would be even better :-)  disable or be able to set it to user defined phrase.


edit: while ur at it .. voice command for all on / all off  would be nice too
edit2: on the other hand one could make a scene where everything is being turned off and call it "Mi Shizzle"  and open VR and say : "run Mi Shizzle"  .. or "activate mi shizzle" it works but its ehh weird.. :-)

i have also a scene where it turns on light and heating for my pet .. i sorta dislike the idea of :  "execute my pet"
[/quote]

 2
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 18, 2012, 05:19:23 am
I'll add that to my list. Right now I am focusing on bug fixes and will try and get a final build out this weekend. I just got a new laptop and waiting on some parts. So work will be limited until I can get everything installed and where I need to be.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: S-F on May 18, 2012, 06:41:10 pm
I find it odd that you still have bugs to hunt down since it's been rock solid for me. I just installed beta 9 last night. I didn't rush to 9 because I didn't have a single issue with 8. And I also started a new job which has me going whenever I'm not sleeping :-\

Thanks again for this great tool. Your dedication to it is really quite impressive and I for one am very grateful.
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: Odeen on May 18, 2012, 07:59:21 pm
Hi Garrett,

Beta 9 works peachily over 3G, 4G Wimax and Wi-Fi.  :)  Not sure what the issue was with Beta8 and 3G. 
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 19, 2012, 07:02:44 am
Most of the bugs are in AutHomation and are pretty minor. But a bug is a bug and it is best to fix it. :) I have been receiving less and less crash reports. Either I have got a pretty stable build or not many people are using the app (hopefully the former). I need to find some time to get the next release out. Which should be the last and hopefully official release. I hope to get that time in the next day or two.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: lolodomo on May 20, 2012, 05:11:14 am
Hi Garrett.

I just played with your application on my Android phone. I like the ability to have each device in (more or less) full screen 8)
I encountered no problem.

Two things that I don't really like:
- there is no way to exit quickly the application. Back button seems to go through all the navigation history (like the browser)
- we have to select a room first and so no way to have devices from different rooms at the same time. But that is a choice.

Good work. I will now switch between your application and Home Buddy.
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: lolodomo on May 20, 2012, 05:12:09 am
Hi Garrett.

I just played with your application on my Android phone. I like the ability to have each device in (more or less) full screen 8)
I encountered no problem.

Two things that I don't really like:
- there is no way to exit quickly the application. Back button seems to go through all the navigation history (like in the WEB browser)
- we have to select a room first and so no way to have devices from different rooms at the same time. But that is a choice.

Good work. I will now switch between your application and Home Buddy.
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 20, 2012, 07:03:29 am
Hi Garrett.

I just played with your application on my Android phone. I like the ability to have each device in (more or less) full screen 8)
I encountered no problem.

Two things that I don't really like:
- there is no way to exit quickly the application. Back button seems to go through all the navigation history (like in the WEB browser)
- we have to select a room first and so no way to have devices from different rooms at the same time. But that is a choice.

Good work. I will now switch between your application and Home Buddy.

lolodomo,

Thank you for your comments. Let me answer your concerns:

1. When you mean exit, do you mean exit completely out or going back to the main screen? If it is for the main screen, I can look into having the application icon at the top left hand corner allow you to go directly to the main screen. If it is for exiting the app completely, you can use the home button on the device.

2. You have a few options: You can select the all room to show all of your devices. You can than sort by category if you want to break it down more. You also have the option to search for a particular device as well. Or make use of the favorites section. The usability as you can see is different from what HomeBuddy offers. Some prefer my layout and others prefer HomeBuddy's.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: pgrover516 on May 20, 2012, 09:29:51 pm
Garrett, does using the home button to exit not leave the app running in the background like most apps?
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: garrettwp on May 20, 2012, 11:57:31 pm
Pressing the home button will cause the app to go into a pause state and when opening the app it should resume to where it left off (just like all other apps). If you have the option to allow data to be refreshed in the background, a service process will run in the background.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: garrettwp on May 21, 2012, 03:19:03 am
Just released another update. This is considered the release candidate. If no new bugs crop up, I will release this version to the play store. Changes posted in the first post.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: lolodomo on May 21, 2012, 04:37:27 am
Garrett, does using the home button to exit not leave the app running in the background like most apps?

Yes, it is (verified).
That might be stupid but I don't like to leave applications running in background when I don't use them.
Title: Re: Public Beta Build of Version 2.0 Beta 9
Post by: lolodomo on May 21, 2012, 04:44:25 am
2. You have a few options: You can select the all room to show all of your devices. You can than sort by category if you want to break it down more. You also have the option to search for a particular device as well. Or make use of the favorites section.

Yes, ok, that's fine finally.


I see that the temperature icon is sometimes blue, sometimes red. What does it mean ?
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: garrettwp on May 21, 2012, 04:54:08 am
Depending on the temperature level, the icon will appear blue for cold or red for hot.

cool:
less than 65F
less than 18C

Heat:
65F or above
18C or above

- Garrett
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: Aaron on May 21, 2012, 10:34:17 pm
RC working well

Any thought around "partitioning" the Favorites by Room or labeling like <Room> - <Device Name> ?
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: capjay on May 22, 2012, 06:29:59 am
Depending on the temperature level, the icon will appear blue for cold or red for hot.

Speaking of icon colors, I have a thermostat, while cooling, sometimes the icon is blue and sometimes it's gray (even when cooling) any special meaning?
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: garrettwp on May 22, 2012, 06:46:29 am
RC working well

Any thought around "partitioning" the Favorites by Room or labeling like <Room> - <Device Name> ?

It is on my list. I still need to figure out how I want to go about it as I am limited on room for the tiles.

Depending on the temperature level, the icon will appear blue for cold or red for hot.

Speaking of icon colors, I have a thermostat, while cooling, sometimes the icon is blue and sometimes it's gray (even when cooling) any special meaning?

It should only be gray when the thermostat is set to off (not in auto, heat, or cool). What type of thermostat are you using?

- Garrett
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: capjay on May 22, 2012, 09:21:59 am
It should only be gray when the thermostat is set to off (not in auto, heat, or cool). What type of thermostat are you using?

I'm using Trane Z-wave tstat with beta 8 (working solid). I'm pretty sure the AC is on, yet the icon is gray. Screenshot attached.
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: garrettwp on May 22, 2012, 10:34:45 am
Looks like a bug with the Mode set to auto. Ill have to look into it and see what I can find.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: garrettwp on May 23, 2012, 02:41:15 am
I have hopefully fixed the issue with the Thermostat mode not showing the correct icon when in "Auto" mode. I was not accounting for the icon change when in this mode and hence why you see the gray icon. It should now reflect the state it is in either heating (red icon), cooling (blue icon), or idle (gray icon).

- Garrett
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: capjay on May 23, 2012, 04:23:30 am
I have hopefully fixed the issue with the Thermostat mode not showing the correct icon when in "Auto" mode.

Kudos for another squashed bug :-)
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: garrettwp on May 24, 2012, 03:13:56 am
I am hoping to have an official release by this weekend. It looks like no new bugs have cropped up so far. The fix for the temperature icon will be in the official (next) release.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: Aaron on May 25, 2012, 07:21:15 pm
RC working well

Any thought around "partitioning" the Favorites by Room or labeling like <Room> - <Device Name> ?

It is on my list. I still need to figure out how I want to go about it as I am limited on room for the tiles.

The newer "device panel" UI, while nice looking, has a lot of unused space, and the panel gfx takes up extra room. Maybe an option to use the older UI .. a List View?

I had a few UI thoughts I hope you consider... I mocked up a slight mod to your current UI to add the room names and also show the previously used toggle, which I think looks much nicer than the separate rectangles for on/off, and would also free up space for other info.. like a 'last triggered' day/time, or something relevant to the device.

have a great holiday weekend!

Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: S-F on May 26, 2012, 07:35:37 am
I had the first snag in a while last night. I selected the view scenes, which I hardly ever do, and when I went back to devices everything was displayed. Changing rooms brought everything back to normal, but even if I pressed scenes or devices while still in that room everything was still there.
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: garrettwp on May 26, 2012, 02:29:42 pm
That is odd. I tried to mimic the same thing and I can not reproduce the issue. I went to the scenes section and back to devices and got the devices for the room selected. I'll keep playing and see what I can find.

Aaron,

Where you have the room labels is where I was planning on putting them. Even though you say that there is wasted space, my goal is not to clutter up the tiles to make it hard to read the information that is important. The goal of the tile is for the important stuff and some quick actions. As for the toggle switch, I went with the separate on/off buttons as I got requests to have them. It also makes it easier to select the correct function. Say that the light is on, but for some reason Vera reports that it is on. If it was a toggle, you would have to toggle the button several times to get the correct action. With the separate buttons, all you have to do is select off.

I moved away from the list view to keep the UI the same across all platforms (phone, tablet and googletv). It would be too time consuming to maintain different layouts across multiple platforms and would get complicated fast.

I'll try and get the room labels added in for the final release that I hope to have out at the end of the weekend. Have a great / safe holiday.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: S-F on May 26, 2012, 06:34:01 pm
Yes it is odd. I haven't encountered this before or since. Granted I don't view the scenes tab much. It is not reproducible. I just thought I'd mention it any way. It's probably just another issue with my Transformer.

Thanks again for this great tool. I use it daily.
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: Aaron on May 26, 2012, 06:48:28 pm
Where you have the room labels is where I was planning on putting them. Even though you say that there is wasted space, my goal is not to clutter up the tiles to make it hard to read the information that is important. The goal of the tile is for the important stuff and some quick actions. As for the toggle switch, I went with the separate on/off buttons as I got requests to have them. It also makes it easier to select the correct function. Say that the light is on, but for some reason Vera reports that it is on. If it was a toggle, you would have to toggle the button several times to get the correct action. With the separate buttons, all you have to do is select off.

I moved away from the list view to keep the UI the same across all platforms (phone, tablet and googletv). It would be too time consuming to maintain different layouts across multiple platforms and would get complicated fast.

I'll try and get the room labels added in for the final release that I hope to have out at the end of the weekend. Have a great / safe holiday.

- Garrett

I do like the look of the panels, it is nice.

I understand the reasoning for the separate buttons.

Observation and thought about action/reaction/refresh of the GUI...
I was wondering if you'd be able to add in an option where the user's last command would be "sticky" in the GUI - thus immediately showing the to-be state of the device?
Currently the GUI will show the 'last state' until it refreshes from Vera; then the GUI reflects the changed state. This can take a few seconds and is a bit confusing, especially for guests. In those few seconds the user thinks the command did not work (since the GUI does not reflect the change) and may try to change it again.
... thoughts?
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: lolodomo on May 28, 2012, 04:07:09 am
Hi Garrett.

I think that when the application is started, data are not refreshed. Can you confirm ?
If that's true, I think you should refresh data automatically at startup.
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: guest13549 on June 02, 2012, 05:19:31 am
I love this app so much.. :)

A minor issue with it, is that Aeon Labs Smart switches does not show energy consumption when on, like e.g. the Everspring plugs.

And it would be nice with multiple favorites  :) (upstairs/downstairs etc)

Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: capjay on June 02, 2012, 05:51:27 am
+1 for the multiple favorites. I'm always hesitating to put more devices in favorites, cause I want to avoid to have a long list to load  :)
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: garrettwp on June 02, 2012, 10:23:03 am
Let me look into it and I'll add it to my list. I can not guarantee anything.

My apologies for not being active on the status of the app. I've been busy getting other things done. I am making a small change to the app and will have it on the market within the next few days.

- Garrett
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: Aaron on June 02, 2012, 12:53:41 pm
And it would be nice with multiple favorites  :) (upstairs/downstairs etc)

This is a good idea. Being able to custom name each favorites screen is ideal.

One good use case for this... touch pads are strategically placed in areas and show a favorite screen has items in proximity to that area.


Another feature that would be useful...

Having Authomation store/sync the 'config' from the Vera. This provides a few benefits:
1) Complete backup/restore of config if something happens to the client device
2) Ability to easily switch devices without needing to do a complete reconfig of Authomation.
3) "Hidden" devices could be set once, and synced as hidden to all clients
4) etc...

Garrett,
You have a great app with tons of potential. I tried Home Buddy and while it works well, I like your app better. Though, Llama integration would be great.
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: PurdueGuy on June 02, 2012, 09:34:05 pm
Hey Garrett,

Wanted to keep you updated, I tried the RC on Kindle Fire.  Disabled the beep and TTS, and it works just fine.

-PurdueGuy
Title: Re: Public Beta Build of Version 2.0 Release Candidate
Post by: garrettwp on June 04, 2012, 03:17:14 am
Closing this thread as I have posted version 2.0 on the play market. Will create a new thread for the official release.

- Garrett