Alex Muthmann

I still think it would be useful. A simple error message is often misleading :( Probably the usage of the extended notification (http://developer.android.com/training/notify-user/expanded.html) would be a good starting point?

hey, thanks for posting this bug, saved me a lot of debugging. I ran into the same issue on a 918+ with the Club3 thing, I had the last release...

There is no official documentation of this data, but i contacted the creators and they told me, it's ok to use. The values are in this order: date open high...

It's not "outdated" it's oldschool ;) Edit: i commited the code to my fork: https://github.com/deveth0/XChange/tree/advanced-bitcoinchart-data

Read the docs ;-) there is a setting to swap heat /auto exactly for this case.

Did you check the docs? You can configure if the TRV is set to `heat` or `auto`. See also https://github.com/KartoffelToby/better_thermostat/issues/1155

I have a few TS0601 which just heat when set to heat and don't care about the set temperature. When setting it to "auto" they heat to the configured temperature...

@yecukeng: you can upgrade to 1.2.1 which was released yesterday ;)

Afaics this is an issue with the action configuration in jail.local which does not set the sender / sendername: https://github.com/fail2ban/fail2ban/issues/2071#issuecomment-371796715

A similar behavior can be observed if the test-name uses certain special characters, e.g. `do some weird things with \$foobar`