Changelog

Changelog

Please note: There might be also a newer beta version available. To register for beta version, make sure to join the andFHEM Google+ group
and register on one of the following pages below (for your installed version):

In some cases widget configurations remain within andFHEM even though they
don't exist any more. AndFHEM still tries to update them, loads the device
list and tries
to update a device that cannot be found. This consumes loads of battery and
is useless,
which is why this behaviour changed in 4.7.9.

When updating a single widget fails, all other widgets will still be updated
by now

Migrate more devices as generic devices: (15 device types still left to be migrated
...)

Add password protection also when returning to the main app from a widget.

Repair widget update when having different servers configured

Repair application crash for devices containing on/off in groups within a setlist

IMPORTANT: Speech recognition only
for for Google Now. As Google Now is deprecated and is being replaced by Goggle
Assistant, speech recognition will stop to work.
Up to now, there is no workaround for this issue, as the official API for Google
Assistant requires a central server to be called (which we do not have for FHEM).

Evaluate devStateIcons for device states and attributes (only for textual
attributes, not for on/off buttons or sliders).
As this feature has nothing to do with basic application functionality, this feature
is only available to Premium users.

First of all, this should resolve some (very) long standing issues.
Especially, when opening the app after some time, the device list was shown
as empty (no devices found). This bug should be just fixed with the new
infrastructure.

The staggered view also means that when using multiple columns, especially
for tablets, rows of different columns are no longer aligned. The columns
are layouted completely separately. In effect, this uses much more of the
available space.

However, this also means that there is no longer a grid - thus it is
difficult to find out which attributes of each row belong to each other.
Android has introduced cards to treat that issue. This is exactly what
AndFHEM does now. However, this is a design experiment, so if you
don't like it, feel free to send me a message, together with a hint on how
to solve this issue in a better way.

Previously it was possible to specify column sizes within the preferences.
This option is gone by now. AndFHEM will calculate a "good" column width for
you. However, if this does not work on your device, please tell me.

Load device graph definitions when opening the device detail page instead when
loading the xmllist. Please make sure
to update the device list from within the "Favorites", "Rooms" or "All devices" view
to be sure all graphs
are shown correctly

If using multiple connections andFHEM will now store favorites and widgets for each
of those connections. In effect, you can now execute widget commands without
changing the connection within andFHEM. Note: AndFHEM will only migrate existing
favorites if only one connection is available. Note2: This is a pretty huge change.
I've tried to test those "few" available features to my very best. If you still
encounter some bugs, please feel free to write a mail or open a Github issue.
Thanks!

Delay HUE commands (just like CUL_HM) to see whether andFHEM will update the status
correctly afterwards

3.8.0 beta1 (04.10.2015)

This is an initial beta release for the new version relying totally on generic devices.
Please note that not
all devices have been migrated as generic by now. Some devices, incl. AVR, dummy and rgb
devices are still
missing. However, the big ones (like HomeMatic, FS20, FHT, ...) are done.

Make use of sortRooms FHEMWEB property correctly (space as delimiter instead of
comma, repair sort
order)

Preparations for Android 5

Remove ActionBarSherlock as actionbar provider, make use of Google APIs

Compile against Android 5, allowing to install andFHEM on Android 5

Adapt styling to material design (at least a little bit, more to come).
Screenshots will be
updated when the styling update is finished. This will take some time as
Android 5 provides
loads of nice things.

Important: This has impact on pre Android 4 devices. Android 2.3
support has been
dropped. Android 2.3.3 is still supported, but I will not take too much care
on looks for now.
The market share concerning andFHEM is down to 5%, with drops of 2% expected
each month.
Effectively this means that Android 2.3.3 support will be dropped in about
three to four months.

Configurable y-axis ranges for graphs. From now on there are some defaults for
minimum and maximum
y-axis ranges. If you find some completely invalid ranges, please tell me. For
exotic use cases, you
might want to read about the new yaxisminmax hook.

Dim support for ReadingsProxy devices This also includes a major cleanup for
all other dim devices.
If one of your devices stopped working, please send me a current xmllist so I can
resolve the error.
Thanks!

Handle setList correctly. FHEM sends some very nice information about which states
are available for
switching. Up to now andFHEM pretty much ignored that values. This is now evaluated
correctly, resulting
in a cleaner application design and, for all users, an updated available target
states switching row.

Send Android wide broadcasts if a GCM device state change has occurred. This can be
used to trigger
actions within Tasker.

Add a Locale plugin for changing connections. You can use that one to change the
current connection
based on WLAN availablity.

Add a connection selector to the send command Locale plugin.

Add an Intent service for providing device names to external applications (see
External Interfaces for
details)

Add pressure graph to TRX_WEATHER devices

Fix a bug resulting into devices being sorted into wrong functionality groups.

Note: As the Locale plugins have
massively changed,
existing configurations have to be reconfigured, as Locale, Tasker and Llama will
not find the
previously existing plugin. Sorry for the inconvenience.

Graphs refactored (Hopefully I did not break anything. If you encounter
some new issues here, please send me an email. This especially concerns
sum graphs). In effect, scaling of axis should work now. Scale buttons
are also back.