Good to hear, planning is still rough as now sun isn’t (cloudy) that bright at this moment so estimation isn’t perfect.
Hi Jeroen. Al good now, no high load an no crashes. 
Resetting all hardware/settings worked. But, I don’t know what was the cause.
Perhaps an idea for a future release: backup (and import) hardware settings?
If I’m the only one then not wise… 
I cant backup hardware settings. That is Homey. Problem hardware id’s change.
1 Like
Not a bug in my code, must be something from Athom?
Is this some other app putting those capabilities under it?
I dont see/know/recognize this.
EDIT: Check the Advanced Device Capability app?
A wishlist option could be to integrate the Solcast API for more precise solar forecast. Works surprisingly well!
I am currently not allowed, my app has no Homey acces to other apps.
Am using open-metio with radiation data which is okish.
Hi Jeroen,
I have set up a system to heat my boiler using surplus solar power. With the P1 meter, I detect how much energy I draw from or how much energy I feed into the grid. I use an energy socket to measure the boiler’s consumption. From the difference between the two, I calculate the power output with which I can now control the boiler.
Since the update of v3.13.47, I see that “energy_socket Polling - Minimum poll interval raised to 30 s (was 2 s)”.
Due to this increase in the polling of the energy socket, my system has become unstable. The cause: a new control value for the boiler is calculated every 4 seconds, but the socket is only read every 30 seconds.
If I only control the boiler every 30 seconds, my system is much too slow, and I draw power from the grid for an undesirably long time when, for example, a cloud passes in front of the sun or another device switches on.
Please return the polling of the energy socket to 2 seconds as before.
Direct access to other Homey apps isn’t needed, as it is possible to directly query the Solcast API itself. But for the moment open-metro might be enough.. just food for thought 
This also explains an issue I have. Thanks for the tip. I know now how to fix it.
@Jeroen_Tebben : If you change this permanently you should also update the advanced settings for the Energy socket. Mine still show a polling interval of 10 seconds and minimum allowed is 1. This should be changed to 30 because they are now actually polling every 30 seconds.
Sorry Patrick & @Hsd1965 this got derailed by other users that have 30 sockets and a crashing Homewizard app / Homey. Let me restore and give control back to you as a user.
But that will lead me to not act on this anymore if people struggle with their sockets this way and end up with crashing app due to high CPU load.
Yes, for clear weather days it’s great. For cloudy days it could be better, what’s your thought on that? Just keep the open-meteo for now and see how it goes… You could always add support for Solcast API as an addition to open-meteo later, if you’re feel like it.. I’m already happy for now 
1 Like
Deleted
It would be ideal if I could set the polling time of the socket myself, just like you can do for the P1 Meter in Homey’s advanced settings.
Thanks in advance.
It should cater for cloudy days as well, also it needs to learn from samples next 3 days to improve the curve so it might look off a bit but there is some bias to improve it.
Indeed, but this setting has no effect, polling remains 30 sec in de not updated version…
