Thanks Dick.
to note, it has been running pretty smoothly on this side recently, so already very happy with it. getting it from the web API will hopefully only make it more reliable and robust.
thanks!
Thanks Dick.
to note, it has been running pretty smoothly on this side recently, so already very happy with it. getting it from the web API will hopefully only make it more reliable and robust.
thanks!
Thanks for your kind words Patrick. On my side itās also running smoothly. I have a feeling that too many requests to the ECU will make it to stop communicating. I now have a 5 minute interval and a start and stop depending on sunrise and sunset.
The downside of the web api is that with a short polling interval you will reach the maximum api calls pretty fast. There is a possibility to pay for an increased amount of calls, but Iām unaware of the costs.
Device just became unavailable and the app no longer exists in the home app Storeā¦. @Dick_J something happened?
Aah, so that is for the normal version. the test version still functions ![]()
Only thing is that the tag:
āwhen power changedā is not available in the test version,
Hi Patrick, that tag should not have changed. I will look into that.
Itās still there. The thing is that some flowcards you only see when selecting the device in the āappsā column on the left. Maybe I can change that, I have to look into that
aaah, itās in th middle, not on the right list of cardsā¦. thanks
I moved the cards to the list on the right. Downside is that the āoriginalā cards do not exist anymore and you will have to repair your flows
oke thanks. helps for the clarity. will repair them
I see al lot of crashes, can somebody send me a diagnostic report? At my installation itās running fine, so I donāt know whatās causing the crash.
I use Copilot sometimes to write the code, but last week it messed up a lot of code ![]()
I thought I had fixed things, but obviously not all/ enough. Maybe Iāll roll back to an older version.
Hi Dick no crashes here, app is running smoothly.
Diagnostic code: 1f23f1ba-d0d9-44a6-9f60-25cd8ebc5157
Best regards Peter.
Hi Peter, thanks. I also donāt have any problems. It could be just one user, but I doubt that.
I saw that you only use the ECU data. Itās possible that the error only occurs in the web application.
Today, 100 crashes. A new milestone ![]()
Maybe I can help, it is really strange app was working and now for the second time it mentions application unavailable and when I got to the store link it is gone as well. When I click the old app link from this forum post I can install it again and it works again. Needed to do this now two times already.
Report: 31633088-1fe0-47b6-8662-f5e458306dfa
exactly the same here. Looks like it happend both times though at an app update.
Running smoothly for the rest.
Hi Niels, that happened to me as well, I turned automatic update off and than you donāt have any problems, you only have to update manually.
It seems that the automatic update installs the regular version all the time instead of the test version.
Best regards Peter.
I install the app in a different way, so I was unaware of this. I finally found an issue with the ECU triggers, when an error occurs or when the power changed.
I released a version where this should be solved.
APS app v1.3.9
I had changed the code to be more efficient. The ECU has to be polled once for information about the inverters and firmware and once for the generated power.
I combined that, which led to the ECU becoming non responsive. So I changed it back. Also added a flowchart to reset the web polling counter, for instance at every first day of the month.