OK. But I canât even get into that menu. The errors comes before I get in. And when i click OK on the error message I get to a screen saying Timeout! Homey opptattâŚ
The error should only appear when the app has not loaded correctly. Does it help to restart the app (not reinstall) ?
Seems like a different error was the last one this time
How I noiced the error was a âspinning wheelâ on the Innsikt, when I wanted to check month tarif
Doesnât help to restart app
This sounds like it is a little bit outside of my control. So either the homey disk is full so there was no space to fully install the app or there is a bug in the Homey itself that prevents it from initializing the app correctly.
So the error you get on the screen is actually from the Homey API itself (not this app), and it indicates that the Homey API has not read the app API definition file. So it all happens before any invocation of this app⌠so I would expect this to happen within the first minute during/after the app is upgraded to a new version but never after that. (so as long as the app device has a spinning icon - this might take a bit longer if your homey is busy⌠or maybe Homey uses longer time to download the app upgrade and install it if the internet connection is unstable?)
So it seems to me like this should resolve if you
- wait until the app has properly downloaded and installed the updated app version I sent out this morning.
If waiting does not help, does it help to restart Homey?
I have changed the feedback message for this case as follows from version 0.18.35 of the app and onwards (test version available here):
It seems like Homey is updating the app version. Please try again in a minute or two when the app has been properly installed.
Assuming that this was the case for you. If waiting does not resolve it then please let me know.
For everyone on testing that is using the Easee charger. Please note that I implemented a new charging algorithm that was going for testing. But in the process I discovered that the old algorithms would have been rendered unusable, so please report back quickly if the new algorithm does not work so I can try to fix it, otherwise, you need to charge outside of Piggy for the time being. (or go back to stable)
The most recent stable app update introduced 2 crash bugs:
- One for owners of knx thermostats
- One for owners of Easee chargers that has not installed the test-version of the easee app.
Anyone experiencing these crashes can update to the test version of the app as these has been fixed.
If there are no problems with it the test version will go to stable within the day.
Tried everything to get it working, but nothing worked. But to day it is working again 
Itâs a bit odd @foni , sounds like the app was not installed correctly or at least not initialized correctly. I wonder⌠maybe you was hit by the crash-bugs as noted above. As those would prevent the app from being initialized I suppose you could get symptoms such as that.
Though, I did transfer the update from testing to stable less than a hour ago so in case you donât have it yet it might be something else.
Installed this and have been testing this the last week. Having issues with the app turning off heating (to avoid using more than 10kwh in an hour) but not turning it on again when the Power usagte is under control. Is this a known issue?
Using mill units and heatit ztrm3. None of them was turned back on (and i waited 30minutes).
I have gotten a few reports about this, and done a little investigation without success so far, so any clues you may provide can be good. What I know so far is that if you restart the app then it starts working again. Thus I did add a feature to dump the internal state of the app under the setup menu called advanced / Backup. If you can do a state dump when the app is broken and then restart and add another state dump when it is working we can see clues in the diff between the two dumps (sorry you have to manually copy the state dumps into files for now, but it was the best I could get on short notice.)
Cool! Iâll Get back to you when I experience this issue again!
Thanks!
You can follow the status of this issue here: Some times units are turned off but does not turn on again ¡ Issue #82 ¡ frodeheg/no.sparegris ¡ GitHub
Whoever asked for Elko Smart Super TR RF support can now test it here
Finally
We have reached the milestone where car charging is working as intended for Easee chargers so I pushed it to stable right now. (Though, nobody has yet complained about charging with flows (other chargers), so I just assume they work too.)
This will allow me to focus more on the next milestone, improving the user experience. Starting with the most prominent issue above with devices not turning themselves on again, there will be a few improvements in how the app behaves, looks, interaction with the interface and flows going forward. As always, if you have any suggestions or requests, please file a new ticket on this link and your idea might be the next feature.
Other news: We just passed 600 users after a massive surge this week, will we be 1000 before the end of the year?
@Krisch2 , The issue with devices not being turned on again has now been resolved in test version 0.19.4.
Apparently, if you had disabled temperature control of devices, then they would not turn on again.
Was this the case for you, or could it be another bug?
I have Tibber Pulse and Easee charger and I am thinking of installing and test. Can the app adjust the Easee charging current if I want the total power should not to exceed Level 4 15Kw?
