AutHomationHD 3.3.1.1 Alpha

Apps & Remote Access Unmaintained
1

I have posted a sticky on how you can try an alpha build of the next release. There will be cosmetic issues / inconsistencies, incomplete features and device support as well as bugs. Here is a list of changes in this version:

MMS / UI6 ACCESS:

For remote access. If you already have your Vera with UI6 added into the app, you’ll need to go into Manage Veras → Edit Vera:
Enter username
Enter password
Select MMS

To add a new Vera with UI6. Go to Manage Veras → Add Vera. Follow the on screen tutorial.

Version: 3.3.1.1:

Direct Download

Updated 2014/04/19

Feature: Added On / Off Status for Sonos and DLNA Devices.
Feature: Added Radio Thermostat support.
Fixed: Minor bug fixes.

Version: 3.3.1.0:

Direct Download

Updated 2014/04/16

Feature: Added cover art / song info for Squeezebox, Sonos, and DLNA card view.
Feature: Added the ability to put Vera into include / exclude mode.
Feature: Add card views for Window Covering, Google Calendar and PLEG.
Feature: Added energy mode to HVAC device dialog.
Fixed: Sonos repeat and shuffle buttons.
Fixed: Minor bug fixes.

Version: 3.3.0.5:

Direct Download

Updated 2014/03/20

Fixed: Made a few minor changes to Voice Recognition to improve accuracy.
Fixed: Crash for Voice Recognition when speaking a command.

Version: 3.3.0.4:

Direct Download

Updated 2014/03/19

Feature: Card View for Sonos, Squeezebox, DLNA, Russound, Combination Switch, and Day and Night plugins.
Feature: MutliSwitch Card View support.
Feature: Overhauled UI icons.
Feature: Many UI tweaks.
Fixed: Sonos fixes (still an issue with repeat button function).
Fixed: Various bug fixes and tweaks.

Version: 3.3.0.3:

Direct Download

Updated 2014/02/28

Feature: MultiSwitch label support.
Feature: MutliSwitch Card View support.
Fixed: Voice Recognition HotWord detection beep issues.
Fixed: various bug fixes and tweaks.

Version: 3.3.0.2:

Updated 2014/02/25

Feature: Support for UI6 / MMS Authentication (still need to add Auto Configuration Option).
Feature: Ability to send log data via email. Located in Settings → Development Settings → Send Log Data
Feature: MultiSwitch Plugin Support.
Feature: Virtual Motion Sensor Plugin Support.
Feature: MultiSwitch custom intent support (Shortcut / Tasker).
Fixed: various bug fixes and tweaks.

For remote access. If you already have your Vera with UI6 added into the app, you’ll need to go into Manage Veras → Edit Vera:
Enter username
Enter password
Select MMS

To add a new Vera with UI6. Go to Manage Veras → Add Vera. Follow the on screen tutorial.

There may be a possibility that any home screen shortcuts will stop working. This looks like some sort of Android bug due to changing the version number.

Version: 3.2.1.6:

Updated 2014/01/27

Fixed: Bug where app would crash on trying to load vera connection data in GetDataService. This would also happen if auto refresh was not enabled.

Version: 3.2.1.5:

Updated 2014/01/23

Feature: Added option for user to submit Vera data from app via email. Located in Settings → Development Settings → Send Vera Data.
Fixed: Updated Nest plugin support to accommodate current Nest plugin changes.
Fixed: Minor bug fixes.
Fixed: Cleaned up code.

Version 3.2.1.4:

Updated: 2014/01/06

Feature: New crash reporting tool. Will now prompt to email log output as well as option to include vera data. Can be disabled.
Feature: Added Discrete Power, Toggle Power and HA Device Toggle to custom intent / Tasker / Home screen shortcut.
Feature: Moved auto connection switching option into individual Vera connection details. This can be enabled / disabled by editing the vera connection details under “Manage Veras”. This will need to be re-enabled if you had this set in the settings section.
Fixed: Voice recognition accuracy. (I was accidentally comparing the escaped names to the the vera database to find the correct match)
Fixed: Voice recognition crashing for some users. (Due to special characters in names)
Fixed: Greatly enhanced the auto connection switching speed. It should now only take a few seconds to figure out which connection to use.
Fixed: Small bug fixes and UI tweaks.

Version 3.2.1.3:

Updated: 2013/12/27

Feature: Using new library for Card View (Experimental).
Feature: Using new library for pull to refresh (Simulates Gmail pull to refresh).
Feature: Add card view support for the following devices / plugins: Scenes, Variable Container, Weather, Alarm Panel, ISY Controller, Energy Meter.
Feature: Added support for the PowerArithmetic plugin.
Feature: Added backup / restore option (Experimental and needs thorough testing).
Fixed: Issue where app settings would be cleared (hopefully fixed).
Fixed: Updated code to enhance switching between local and remote connections.
Fixed: When sending a command and on local connection, if the command fails to send via local connection, it will try and send via remote servers. This should help with auto connection switching issues. E.g. Tasker firing a task before connection can fully switch over to new connection.
Fixed: Minor tweaks and bug fixes.

Version 3.2.1.2:

Updated: 2013/12/11

Fixed: The ability to toggle repeat and shuffle for Squeezebox, Sonos, and DLNA Media plugin.
Fixed: Some Russound bugs and cleaned up the UI.
Feature: Added support for WifiRTS device (window covering).
Fixed: Switched the ISY fanlinc to use 0-100 values for fan speed. (Per changes in the ISY plugin)
Fixed: Other minor issues / bugs.

Version 3.2.1.1:

Updated: 2013/12/01

Feature: Hotword voice detection (experimental) See below
Feature: DLNA Plugin support (needs testing)
Feature: Russound Plugin support (needs testing)
Feature: Variable container intent support (plus Tasker and Homescreen support) See below
Feature: Notifications instead of toast message for Sending command failure / success
Feature: Bluetooth data connection support
Feature: AV Input service intent. See below
Fixed: Sonos plugin support
Fixed: MiLight plugin support
Fixed: Send command retry bugs
Fixed: Minor bugs and UI

Voice Recognition Hotword detection:

You can enable this in the “Voice Recognition” settings. This is a very experimental feature and has only been tested on a very limited set of devices. Use at your own risk. When enabled, you can say “OK Vera” and it will activate the voice recognition portion of the app. This will only work while inside of the app.

Variable Container intent:

Set variable name:
authomation://device/veraid/deviceid/vcontainer/name/1/newname

Where veraid is your vera unit id, deviceid is the variable container id, 1 is the variable to change and newname is the name you want to use.

Set Variable Value:
authomation://device/veraid/deviceid/vcontainer/value/1/newvalue

Where veraid is your vera unit id, deviceid is the variable container id, 1 is the variable to change and newvalue is the value you want to use.

AV Input Selection:

Set av input to 1:
authomation://device/veraid/deviceid/av/input/1

Where veraid is your vera unit id, deviceid is the av device id, 1 is the input to change to.

Version 3.2.1.0:

Updated: 2013/11/08

  • Re-worked Voice Recognition backend, it now uses fuzzy logic using the frej library and will allow for support in other languages (I hope).
  • Re-worked the backend that retrieves the vera data. When using the auto refresh option it will now maintain a connection with Vera and will update as new data happens. Almost real time update.
  • Re-worked the components that send commands to vera, this runs in the background as well as the custom intent service and will allow your commands to be sent simultaneously. It will also try and resend the command if it fails.
  • Added Categories section. You can now show your devices by category.
  • Ability to use custom icons when creating Device / Scene Home Screen shortcuts.
  • You can sort by Room when in Categories or Favorites section.
  • Re-worked the auto connection switching code. Hopefully it performs better.
  • Connection status indicator at the lower left corner of the screen. Cloud = Remote, Home = Local, Triangle with exclamation point = connection issues, Octagon with exclamation point = not connected.
  • Added support for MiLight White, RGB, and RGBW lights.
  • Added support for Philips Hue Bulbs (still working on UI e.g. tile view).
  • Experimental card view (like google now). Only works well in phone layout. Running into some road blocks.
  • Lots of minor UI tweaks.
  • Lots of bug fixes, hopefully with the many changes I did not create more!

The list is incomplete and will be updated as I remember more changes I have done.

  • Garrett
2

great update the respond is a lot faster now when pressing a button till the action excute

what does RGBW support mean? this is for fibaro RGBW ?

thanks

3

No, it is for the milight plug in developed by Rex on the forum. So I guess you have 3.2.1.0 from the play store? Looks like it is now active.

  • Garrett
4

Hi Garrett,

Initial test results for 3.2.1.0 Alpha

[ul][li]MiLightRGBW works well on both color-wheel and White button. Good work![/li]
[li]New rotary dimmer control works well on MiLightWU[/li]
[li]New rotary temperature control works well[/li]
[li]Auto-refresh is very effective[/li]
[li]Scene Active flags working really well[/li]
[li]Window Covering device is missing icon but shows it in detail view[/li]
[li]Allows setpoint to be set on Heater Relay - creates the variables[/li]
[li]Poor hit-rate with voice response[/li]
[li]Voice response prompts to pick one of several identically named devices[/li]
[li]Other devices seem to work as before[/li][/ul]

As mentioned elsewhere, none of my existing shortcuts work with the alpha. Before I recreate the 25+ shortcuts on each of my four Android devices, will they break with each new release?

5

Thank you for the feedback. What were you trying to say for the voice commands?

For the shortcuts, did you have to uninstall the app prior to loading the new one or were you able to install on top of the existing version?

  • Garrett
6
Thank you for the feedback. What were you trying to say for the voice commands?
I tried [i]Turn on kitchen light[/i] and [i]Turn kitchen light on[/i]. When recognized, I got a prompt to pick one of two to four devices all of which were labelled [i]Kitchen Light[/i]. Some other commands like [i]Turn bedroom light on[/i] work some of the time but often produce a pick-list including several other lights - often multiple kitchen lights.
For the shortcuts, did you have to uninstall the app prior to loading the new one or were you able to install on top of the existing version?
It took me a little by surprise. I didn't uninstall the previous version - the alpha one just turned-up on all my devices.
7

Do you have multiple devices that have the same name? I need to make the pick list a little more clear. E.g. Instead of the Device, room and device type, Add the type of action that would be performed. The pick list would show up if it either finds multiple devices with similar names or it somehow found multiple actions for that device to perform.

When you say the shortcuts did not work, did it say that the app was not found or did it not perform that intended action? If the latter, it could be that I may have broken something with the backwards compatibility of the custom intents and I need to fix this. I made major changes to the backend of the app and I want to make sure I do not break compatibility from upgrading.

I’ll also investigate the icon issue for the window covering. I appreciate the feedback. This is what I need to make the app as reliable as possible.

  • Garrett
8
Do you have multiple devices that have the same name?
No exact duplicates but several called [i]xxx[/i] [b]Light[/b]. So a request to pick from multiple of the same device is perhaps because it didn't understand the required action? Yes that could be shown in a better way. I'm also interested in how it could find four possible actions for a binary switch...
When you say the shortcuts did not work...
Sorry, that was vague. The existing shortcuts report: [i]App isn't installed[/i]. If I create new shortcuts they work fine. I can recreate all the shortcuts but it will be annoying if this happens with each new release. I have rebuilt the set on one tablet to check that it all works OK. I'll hold-off doing the others until I see what happens on the next iteration.

I do like the ability to change the icon for device and scene shortcuts. 128x128 pixel pngs give good results. Good feature!

I appreciate the feedback. This is what I need to make the app as reliable as possible.
I'm happy to be able to help. It isn't entirely altruistic, of course. I've replaced all my Jogglers with Nexus 7s running AutHomationHD so I'm enjoying the fruits of your labours. ;D

BTW: I believe you told me that you hadn’t finished implementing support for MiLightCU (DimmableLightC)? The color-wheel and White button show-up but give ERROR: No implementation.

9

Not sure on the shortcut issue. I will have to run some tests, but this is an android issue and not an app issue. It should not affect if the app is already installed. But let me test it out.

The MiLightCU plugin should work. I have it installed on my development vera with the sending of the command commented out. I might have the wrong service used for the device in my app. I will look into it.

As for the voice recognition, I am implementing a more friendly picker. That will be in the next release, hopefully it will be easier to understand what it thinks you said.

  • Garrett
10
The MiLightCU plugin should work. I have it installed on my development vera with the sending of the command commented out. I might have the wrong service used for the device in my app. I will look into it.
Well it confuses me and I wrote them ;D There is an early debug plugin for MiLightRGB that you should ignore. The one to use for a DimmableLight is called [i]MiLightCU1[/i].

urn:schemas-dcineco-com:device:DimmableLightC:1
urn:dcineco-com:serviceId:MiLightCU1

Edit: I can see from the log that you’re using the serviceId for the old debug plugin. Sorry to have made it so confusing.

11

It was actually a copy and paste error! I copied the MiLightRGBW code after finishing that for the MiLightCU. I fixed it and will be in the next release, hopefully in the next day.

  • Garrett
12

Refreshes over the web seem to be slower with this version… like 2-3x.

It takes so long it seems like AH is frozen.

To help troubleshoot, can you add an onscreen indicator (similar to the little cloud/home icon) for when a data refresh is happening… maybe with a timer? This would help see if there is an issue or not. Putting a way to enable/disable it in the settings would be awesome :slight_smile:

13

I have not experienced any slow refreshing of data. Nothing major has changed from how it gets the data and parses it. Do you have auto refreshing enabled? What makes you assume refreshing is slower? With auto refresh, the app will connect to Vera and wait for changes, when changes happen it will parse the returned data and connect to Vera again. Changes should happen almost instantly.

  • Garrett
14

Autorefresh is on, background is off. When I open AH I can see the cashed values, thus I can watch them change as the current/actual value update. With the alpha, that wait time is much longer that the last beta

Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

15

Aaron, I’ll explain how the new auto refresh works. If auto refresh is enabled in the settings, in the new alpha releases it will create a persistent connection with Vera. This is using the timeout variable in MCV’s lu_sdata command. This allows the connection to be held onto until Vera has changes, there is a minimum delay of 2 seconds set as well. What this does it it tells Vera to wait at least two seconds after new data changes before sending it to me. This allows for any additional changes after the first change to be sent and limit additional data requests being sent to me.

When you load up the app, it will connect to Vera and request for changes, depending on the last time you run the app, it will either retrieve the changes from the last update or download the full data if required. If many changes happen from the last time you used the app, it may take a few seconds for the data to sync and show on the UI side.

  • Garrett
16

I’m noticing that sometimes AutHomationHD has trouble figuring out how to reach my Veralite. I’m still ruling out issues on my end, but one thing that’s happening that’s a bit annoying is that AutHomationHD periodically retries my failed command and vibrates to show that there was an error (per my choice in AHHD’s options).

The issue is that it took me a while to figure out why my phone kept vibrating, but there were no notifications waiting. Perhaps AHHD should put something in the notification bar when a communication fails? Have it “stack” for multiples (so that I don’t get a full notification drawer) and perhaps allow me to cancel the action that’s in a fail-loop?

17

I am getting an error logged every six minutes when I have AHHD 3.2.1.0 Alpha active on any of my in-house tablets. The error is:

[code]01 11/15/13 13:09:23.396 e[31;1mUserData::WriteUserData failed File Size: 75191 save size 75185e[0m <0x2bc87680>
01 11/15/13 13:15:23.391 e[31;1mUserData::WriteUserData failed File Size: 75321 save size 0e[0m <0x2bc87680>
01 11/15/13 13:21:23.585 e[31;1mUserData::WriteUserData failed File Size: 75182 save size 0e[0m <0x2bc87680>
01 11/15/13 13:27:23.393 e[31;1mUserData::WriteUserData failed File Size: 75169 save size 0e[0m <0x2bc87680>
01 11/15/13 14:27:23.386 e[31;1mUserData::WriteUserData failed File Size: 75119 save size 75164e[0m <0x2bc87680>
01 11/15/13 14:33:23.547 e[31;1mUserData::WriteUserData failed File Size: 75053 save size 0e[0m <0x2bc87680>

[/code]
The File Size varies a little and usually save size is shown as 0. I do not get the error if AHHD is not active. In the above extract from the log, I killed AHHD for one hour and the error stopped being logged.

Any ideas?

18

[quote=“RexBeckett, post:17, topic:177727”]I am getting an error logged every six minutes when I have AHHD 3.2.1.0 Alpha active on any of my in-house tablets. The error is:

[code]01 11/15/13 13:09:23.396 e[31;1mUserData::WriteUserData failed File Size: 75191 save size 75185e[0m <0x2bc87680>
01 11/15/13 13:15:23.391 e[31;1mUserData::WriteUserData failed File Size: 75321 save size 0e[0m <0x2bc87680>
01 11/15/13 13:21:23.585 e[31;1mUserData::WriteUserData failed File Size: 75182 save size 0e[0m <0x2bc87680>
01 11/15/13 13:27:23.393 e[31;1mUserData::WriteUserData failed File Size: 75169 save size 0e[0m <0x2bc87680>
01 11/15/13 14:27:23.386 e[31;1mUserData::WriteUserData failed File Size: 75119 save size 75164e[0m <0x2bc87680>
01 11/15/13 14:33:23.547 e[31;1mUserData::WriteUserData failed File Size: 75053 save size 0e[0m <0x2bc87680>

[/code]
The File Size varies a little and usually save size is shown as 0. I do not get the error if AHHD is not active. In the above extract from the log, I killed AHHD for one hour and the error stopped being logged.

Any ideas?[/quote]

Where is this log from? The error output does not help me as there is nothing in their that I can relate to my app. Are any of the settings in AutHomationHD set to 6 minutes? I have nothing in my app that defaults to using 6 minutes.

A few other questions so I can try and reproduce. Do you have auto refresh enabled? Is the tablet left on with the app loaded and in the foreground?

  • Garrett
19

I would look to see what “[tt]df[/tt]” says on the machine, and also what “[tt]logread[/tt]” is indicating.

The symptom is similar to what when either the internal drive is full (eg. MCV failed log rotations/cleanup) or when the flash itself is hosed. The former shows in [tt]df[/tt], the latter shows in [tt]logread[/tt].

I’ve burned out the internal flash on at least one Vera unit so far, maybe 2. Newer releases use a deferred write, so the change/write rate may not match whatever is causing the writes to occur (which, in many cases, is normal given what’s stored in that file)

20
Where is this log from? The error output does not help me as there is nothing in their that I can relate to my app. Are any of the settings in AutHomationHD set to 6 minutes? I have nothing in my app that defaults to using 6 minutes.
These are entries from LuaUPnP.log. None of the lines before or after the error are unusual - just normal Vera activity. I just extracted the lines with the UserData write error.
A few other questions so I can try and reproduce. Do you have auto refresh enabled? Is the tablet left on with the app loaded and in the foreground?
Auto-refresh is enabled and the app is running in the foreground. The tablet is on a charging dock with a Daydream enabled. If I kill AHHD, the errors stop. Edit: Sometimes the log entries stop shortly after killing AHHD - usually after one final error. On occasions I have seen the error logs continue until I restart Luup. After a restart I do not see these errors logged until I start AHHD. I have repeated this test several times.

Is it possible that the new auto-refresh is holding something open that Vera tries to use every six minutes?

I would look to see what "df" says on the machine, and also what "logread" is indicating.
[code]Filesystem 1K-blocks Used Available Use% Mounted on /dev/root 4608 4608 0 100% /rom tmpfs 31240 824 30416 3% /tmp tmpfs 512 0 512 0% /dev /dev/mtdblock7 11264 1872 9392 17% /overlay overlayfs:/overlay 11264 1872 9392 17% / /dev/sda1 518320 22928 469064 5% /tmp/log/cmh /dev/mtdblock8 4480 4480 0 100% /mios[/code]

I log to USB and rotates seem to happen as expected. What should I look for in logread (attached)?