Looking forward to this
In Germany, too, people are hot for your app.
While I love people being hot for me, I guess you mean another Martijn
Whenever I’m in the Netherlands, I’ll visit you. We’ll find out together how hot you are.
kwhPrijs is a homey logic variable set with a prefix number. If you have high and low tarifs there are some examples on the forum to set these based on time.
New app update (live: 0.1.1)
- NEW: initial release of the app
New app update (live: 1.0.0)
- BREAK: New app id
- NEW: Number with decimals card
NOTICE: the app needs to be reinstalled , since we had to made an ID change. The first app is not available in the store anymore!
Current flows continue to work, but it’s advised to install the new app and change the flow cards. After that you can remove the old app with version number :
You can see the version number on the mobile app: More → Apps → Flow Utilities
Sorry for any inconvenience…
New app update (live: 1.1.3)
- Remove Notification card
- Minor settings page tweaks
- Tweaks and bugfixes
- Add German translation thanks to @fantross
I really like this idea, did find a bug, and have some feature requests:
I needed to reboot the app before all variables/tokens were created/registered after creating them in the app settings, would result in error(s) before I did so.
A popup warning for the “delete all” button, people with fat finger Will accidentally delete all their variables.
I Assume these are already on your to-do list:
Trigger card(s), for when variables have changed, like the duration, for example the “stop duration” could be stopped in several flows, adding all calculations in all those flows is kinda redundant.
Also better for flow management, as you really know when a value has changed/updated to the new value, delays in the flow cards work, but could result in (edge case) mishaps (and the end result can come in faster, not after at least 4 seconds when using all calculations).
Thanks for your feedback, this is really helpful!
The bug is an unknown issue, I will try to reproduce this issue since during development we didn’t experienced this. Will get back on this.
For the feature requests: I really like the ideas, I will add this to our to-do list!
I’ve installed the app but haven’t figured it out yet. But I hope it should work.
I want to calculate the consumption of my kWh meter for the day.
So “start position” meter, “end position” meter and calculate as end position - start position = daily consumption.
Start standings at 00:01 and end standings at 23:59.
Can you give me a hint ?
If I create a variable in the Homey app, I see it immediately on the web app.
If I create a variable in the web app, I see it immediately in the Homey app.
I don’t have to restart the app.
Thanks for the app.
Awesome that you installed the app. For just your case we created this app.
I think you need te following setup:
Note: 1 & 10 will be your tag/variable of your energie meter to get current counter. The
? will be the tag created by Flow Utilities app (For some reason this doesn’t show in shared flows). So in this case
Kwhmeter verschil or if you have English setup it will be
Note: use the the delay, otherwise calculations are not correct since the cards ar started at the same time.
And the price, is this a fixed value or dynamic based on some site?
kwhPrijs is in my case a fixed value setup as variable in homey. Since my power consumption price is the same for high and low tariffs.
But if you don’t have that you can have a flow setting the current value from 2 other variables(high/low) based on time/date. Setting the 3rd and use that value for the calculation.
Thank you for the explanation. I was misled by your used 1 and 10. Because I want to know the difference of the same meter, I have to enter the same twice. As in the example with both flows, a 1. I fill there the aggregated meter reading, that should be my daily consumption with the solar panels included. And when I manually execute the flows, calculations are also made. So it works. Thank you.
And I bought you a beer.
Ah yes, you need to set the same tag for both flows indeed. Now there where set to a fixed number to have a valid flow.
When the first card is triggered this will store the data in the app to be used in the end card.
Nice that it works for you!
And many thanks for the beer!
New app update (live: 1.1.5)
- Add confirmation popup for removing variables
- FIX removal of variables
New app update (test: 1.2.0)
- NEW: Trigger flowcards (all variables OR a single variable) :
– When Duration calculated
– When Comparison was made
- FIX: Tokens set to null when variable was added
- FIX: Locale improvements
New app update (test: 1.2.1)
- FIX: comparison when value is 0