No problem, Douwe,
I expect the Homey cache gets cleared by uninstalling the Solax app, and
(optional extra step: disconnect the power for 10 minutes, and after Homey startup is completed, )
install the app again.
Ah, thanks, I’ll give it a try.
I removed the SolaX app and completely powered off Homey from the 230V for 10 minutes. Unfortunately, that didn’t solve the issue either. Too bad. Thanks for the tip anyway. We’ll keep looking.
1 Like
It’s very unlikely but are you using some special antivirus protection on your router, which replace the HTTPS certificate during connection to check SSL traffic?
Thanks for thinking along. I’ve connected the Homey to an Asus router via UTP. I haven’t tinkered with its settings. In the meantime, I did reset that part of the pipeline as well. Unfortunately, no luck. It remains a strange phenomenon.
Right.
It still might be Homey’s clock being off, Douwe (despite what it shows you)
To force Homey’s clock to now:
- go to Location
- move the map to have the pointer point in another timezone
- wait a minute
- move the map back, to have the pointer point to Homey’s location, or enter the address of Homey’s location
(changes are getting auto-saved)
Hi Peter, thanks for the tip. I just gave it a try. I uninstalled the SolaX app and virtually relocated my Homey from the Netherlands to South Sumatra (Martapura) for a few minutes. Interestingly, the time zone switched to Asia/Jakarta, but the actual time didn’t change. If that was the idea, I couldn’t quite get that part to work.
After that, I reinstalled the app, but unfortunately, I’m still getting the same error message as before. I think I’ll throw in the towel now—unfortunately, it’s not working. Thanks anyway for thinking along!
Hello, for a flow I need to know the different possible states of the “Run Mode” tag. When everything is fine it is on “Normal”. I need to know all the other possible states. I can’t find it after searching. Could you please help me ?
Thanks
YW!
When it’s about the local time, it should.
So, I just tested with Jakarta as well, got the same results 
no change!
Then I set it to Sydney, and that changed the local time like it should:
Can you give it a go using Sydney?
Preferably use https://tools.developer.homey.app/tools/system to view the time.
Hi Peter, this morning I selected Sydney. The time via your link does indeed show the local Sydney time. After that, I installed the SolaX app, both while set to Sydney and back home in the Netherlands. Unfortunately, neither worked successfully.
Is it possible that there’s another cache memory somewhere in the Homey that might need clearing?
Ah that"s a real bummer.
I have no other ideas to clear a cache somewhere, but to perform a factory reset and start from scratch (because restoring a backup probably restores the cache as well, which is unwanted…)
But first I’d like to recommend to inform with Athom support what could be the cause of the certificate rejection by Homey.
And maybe the app dev can (double) check if the app cleans up everything as should, after de-installing
1 Like
@Michal_Stranik did you look perhaps to my last post? there you can see the difference between before the update and after.
I have a solax inverter running since yesterday, did setup the token to use the cloud api…
but i see no data:
So you have taken data from https://global.solaxcloud.com/blue/#/ecosystem, used your current dongle serial number, and it doesn’t work ? If yes, then the only chance for you is to submit diagnostic log and hope that developer will have a look on it.
Exactly. It accepted the token, but i get 0 events and no data…
i did send the report: ec526d65-1400-42a5-9cb2-c5a089cbf6fa
Now it works, no idea it it needed some time…
Another question: I would like to have a percentage level at the “power changed” event, to not get it fired on every single wattage change 
I guess for Cloud it doesn’t matter, you will not get updates more frequent then every 5 min - based on your settings.
My dongle has port 502 open and i can get date in real time. I also ordered another dongle which updates every 10 seconds.
Hi all, I have 2 solax inverters connected to a homey pro on 2 diffrent locations.
For both it seems that the reading of the data freezes at a certain moment.
Most of the times it is resolved with restarting the solax app.
What could be the problem?
Any permanent solution?
BR
Lately, I have been getting more and more frequent messages: Cannot read properties of undefined (Reading Soc)
sometimes this error stays for half an hour sometimes half a day, each time at a random time.
Now it gives this message from 16:00 today, before that it did give the value. (I didn’t change something or do to it)
On the solax cloud app everything works fine and no error message is shown.
Any idea what I can do about this?
thanks in advance for the help
Hi Michal I recently got my Homey and am delighted with the insights that your app is providing. I have been reviewing the different insights available. I have the impression that the labels for “Charge Today” and “Discharge Today” have been swapped. As you can see from the attached screenshot, when SOC increases (i.e. charging) that is when the “Discharge Today” curve rises. In contrast, when SOC decreases (i.e. discharging) then is when the “Charge Today” curve rises.
Happy to accept that I have misunderstood, and welcome your response. It’s only a cosmetic problem and doesn’t stop me using the data. Fantastic.
