This morning, I noticed that the Android display showed no connection.
Checking VRM, I found that no live connection was possible, with the last update occurring six hours ago (around 7 AM).
I then checked the P1 meter in HomeWizard and saw that the system had started charging at around 1 AM. The charging increased in steps, as shown in the HomeWizard screenshot, until the battery reached full charge this morning. I have manually discharged the batteries to make room for surplus solar power, and reverted to V3.54.
Blame on me…. Thanks for your input LX.
Well today again some weird behavior, and that with v3.54.
I looked for the cause and after a while I found that my network had changed IP addresses. I did not set fixed IP addresses, I am a fool.
I believe that this caused a change in IP for the Cerbo so the SMA energy meter could not transmit the data to the Cerbo anymore and indeed this caused some strange behavior.
Android Display not connecting and loss of the metering device.
But after all it is okay to have a post about this I think.
I changed the devices to fixed IP and it connected again, though it took some reboots and time.
I also think that if an important device like a metering device has lost connection to the Cerbo that the Cerbo should not go into any mode, not loading not discharging or what so ever.
Or let the user set a mode that fits purpose for the installation in case a metering device has lost connection.
For me this is unpredictable behavior that should be set by the user or system installer, even remotely changeable.
By default, with ESS, the system goes into passthrough as it has lost its connection to an EM.
Behaviour is built around supported and tested devices, so strange behaviour from mods will not be tested or considered, which often use different mechanisms to provide data to the system.
Effectively yes.
With a tested EM, that is part of QA and will be widely installed, so the probability of running into an issue is reduced, and if you do find one, it will be fixed far faster.
I still need to implement a function in the python script for setting the ‘dbusservice[‘/Connected’] = 0’ if no data from the multicast stream is received, this way the Cerbo will set itself in passthrough mode? I will check the documentation on that one.
The whole day was filled with disconnects and strange behavior, even with official V3.54
Finally after a lot of hours searching and debugging got It up running again on V3.60~48
It is now working for hours without interruption, lets see how it behaves the coming days.
I was debugging the Python script from the GitHub project and starting the test script on my MacBook caused the SMA Energy Meter data stream on the Cerbo GX to immediately start as well. This had to be a multicast routing issue.
The stream stopped after some time, so i think the connected switches in between halted the Multicast data because of misconfiguration, but strangely it had worked for some days before.
For now it works after tweaking some network settings and change some details in the Python script.
Unifi gear from time to time has some strange behavior, depending on device updates.
Technology sometimes makes you want to pul out all hair… Mix it in the cocktail with inexperience and the taste will definitely not be great;)