DevonMG4
Established Member
An update is needed to this as I think I've been unintentionally misleading in my recent posts, I put it down to age or a brain fart!
In my posts since #344 I keep making incorrect reference to failed coms between Zappi and the Internet, that's wrong, what I should have said is that I'm happy that MY sporadically incomplete charges since upgrading to V5 software on the Zappi are due to poor or failing coms between the Zappi and the device that has the incoming CT clamp connected to it, not the internet.
It doesn't change what I see as the fix for our Zappi / MG4 SE charging problems as our Zappi is so far away from the house, hardwiring it back to the router will hopefully solve the problem as I will then have good coms with the device that the incoming CT clamp is connected to - in my case this is an eddi configured as the master device and also to be hard wired back to the router providing a far more resilient coms route to the Zappi by no longer relying on Myenergi's propietory 868MHz wireless link.
Poor local coms giving a flaky charge should not effect:
A Zapppi that has no other myenergi devices, ie no CT or CT wired directly into the Zappi without a Harvi
Most other configurations I believe could be affected.
I was lucky enough to watch this coms failure in action today as IO allocated me an 11:00z-11:30z charge slot and I wandered out to witness it falling over. It's here in this 30sec vid. Note top right, there is no flow of power from the grid and then the key message Local Coms Lost! Emphasis on Local, it has no sight of the incoming CT or power flow. Normally the graphic shows power flowing in from the pylon to the house to cover what the Zappi is using.
Why is all this here and not in a Myenergi forum. My past experience of solar stop start charging leads me to think that the MG4 is intolerant of being messed about and after a period of stop / start tells the charger that it's had enough and signals charge complete and so ends up short charged.
This recent discussion in this thread came about largely from a back and forth between myself and @Alex Brumpton
In my posts since #344 I keep making incorrect reference to failed coms between Zappi and the Internet, that's wrong, what I should have said is that I'm happy that MY sporadically incomplete charges since upgrading to V5 software on the Zappi are due to poor or failing coms between the Zappi and the device that has the incoming CT clamp connected to it, not the internet.
It doesn't change what I see as the fix for our Zappi / MG4 SE charging problems as our Zappi is so far away from the house, hardwiring it back to the router will hopefully solve the problem as I will then have good coms with the device that the incoming CT clamp is connected to - in my case this is an eddi configured as the master device and also to be hard wired back to the router providing a far more resilient coms route to the Zappi by no longer relying on Myenergi's propietory 868MHz wireless link.
Poor local coms giving a flaky charge should not effect:
A Zapppi that has no other myenergi devices, ie no CT or CT wired directly into the Zappi without a Harvi
Most other configurations I believe could be affected.
I was lucky enough to watch this coms failure in action today as IO allocated me an 11:00z-11:30z charge slot and I wandered out to witness it falling over. It's here in this 30sec vid. Note top right, there is no flow of power from the grid and then the key message Local Coms Lost! Emphasis on Local, it has no sight of the incoming CT or power flow. Normally the graphic shows power flowing in from the pylon to the house to cover what the Zappi is using.
Why is all this here and not in a Myenergi forum. My past experience of solar stop start charging leads me to think that the MG4 is intolerant of being messed about and after a period of stop / start tells the charger that it's had enough and signals charge complete and so ends up short charged.
This recent discussion in this thread came about largely from a back and forth between myself and @Alex Brumpton
Last edited: