question

@teemischer

There's another thread on this, with some links too. Maybe could help..

https://community.victronenergy.com/questions/47688/ess-with-em24-ethernet.html

Yes, I am aware. I used the search function and have already read everything in the forum related to the EM.

My problem is not that I can't get it to work. It works perfectly until it suddenly stops.

Repowering the EM24 always solves the problem, so my issue is directly related TO THIS DEVICE ONLY.

All I would like to get is a newer firmware file so I can check whether the problem goes away.

But nobody can/wants to give me a file, I am being passed around. Finger pointing. :-(

Please make sure you using shielded ethernet cable with the correct connectors. This is a must for all these connections. This will reduce issues in the future. Even if this is not what is causing your problem it will certainly help in the future.

So far my feedback (@mvader (Victron Energy), @Daniël Boekel (Victron Energy Staff) with EM24 after running 2.62 :

It seemed more stable BUT today i experienced again that the EM24 fell out from the Venus. After a min or so it came back.

Later today i did a change to the Multi thru VE.Config so it restarted and then the EM24 wouldn't show up anymore so i am not impressed.

I tried to do a reboot of the cerbo then the EM24 wasn't shown so i went to Modbus TCP, fount it selected it then it was show again in the device list but as above Not Connected. How they got this product approved is a puzzle to me. Maybe the interface is not part of the MID approval...hmmm

This is SO frustrating product to work with and it wasn't cheap either. I am stuck now without being able to get it up and running and i can't shut down whole house electricity AGAIN....

I look thru the logs on the Venus with SSH but i can't find anything that points something relevant.

I just had this issue on v2.63. Has been running for about 3 weeks.

Looks like it is not fully fixed yet.

Dear all,

As recently discussed elsewhere in these long threads: Victron Venus OS v2.62 improved stability with the meters a lot, but did not fix it completely.

For those where there is still an issue, I now have a new firmware file for the meter itself - received from Carlo Gavazzi. Its version v1.6.x, released in January 2021. This release has solved a very similar (or the same) problem for other customers.

The firmware, as well as update instructions as well as how to see what version you currently have installed are all available on Victron Professional: https://professional.victronenergy.com. In case you don't have an account yet, please make one; takes only a few second and no charge or other fees are involved.

I'm quite certain this will solve the issues; and please keep me posted on the progress.

thank you, Matthijs

ps. I'll unaccept the previous answer, and now accept this one; to make sure its on top.

For those that are having issues: could it be that the automatic modbustcp scanning is causing issues? From what I found on sniffing my network, my Cerbo GX will ARP-request every IP-address in my subnet and try to connect with it on port 502.

perhaps the bulk ARP queries OR the attempt to connect to the device on it's modbus tcp port (while there is already an existing connection) is causing issues?

I've disabled automatic scanning and am having no issues, even with firmware 1.4.30.

I have two EM24 ethernet meters (One for production and one for Grid metering) - Both were running 1.3.30 firmware - I wasn't noticing any lockups, however, I decided to install the newer firmware today on both - It went perfectly. The update process is simple - You run the software on a PC on the same network as the meters, you create a manual connection, enter the IP address of the meter and it connects. Click the Settings-> Update firmware and send it the bin file that you can obtain from the https://professional.victronenergy.com/downloads/firmware/ area. The meters were immediately redetected by my Cerbo and normal operation resumed within seconds.
New Firmware now: 1.6.48

Hi all,

EM24 installed here since one week, updated 1.6 at the installation time.

This night, EM24 disconnected .

I'm be able to recover connection thru config menu from the EM24 panel itself without power down all the instllation. I have changed the port 502 to 501 to 502 again, also the switch position initally in "Lock" position.

That must be investigated if it disconnect again...

Hello there.
Just wanted to share my recent adventures with the EM24 Ethernet.
Bought the device back in april, worked very well from day one and also solved my previously mentioned visualisation issues on the vrm dashboard (here https://community.victronenergy.com/questions/72046/vrm-dashboard-not-showing-pv-inverter-history-and.html).
The EM24 shipped with fw 1.4.30 (I guess) and since there were no hickups, I had no update in mind. Venus OS was also on the latest release, v2.73 as of today.
Couple of days ago I discovered pretty low activity from my fronius inverter. Checked settings on the remote console and zero feed-in was set to 0W. Also, the multis were on passthrough rather than bulk and in the device list instead of the EM24 it showed "device not found". So in the ESS settings I switched battery life back and forth and selected the multis for energy metering. Zero feed-in ramped up to 10000W and the fronius was working normally.
Then I opened up UCS and the EM24 showed up as conneceted, disconnected, connected, ... (as seen from @peternielsen here: https://community.victronenergy.com/comments/77330/view.html), ping via CMD was responding fine and all of a sudden the EM24 was online in the UCS. So back on the remote console, the EM24 was again in the device list.
So I tried updating to fw v1.6, but UCS said the fw does not match and it will reboot to the original fw. And since then, the EM24 remains on "info boot", even after disconnecting the grid and power cycling the meter (as mentioned by @wasolar here: https://community.victronenergy.com/questions/98205/em24-ethernet-no-connection-info-boot.html). The decive will no longer show up in UCS or the remote console, but is still responding to pings via CMD.
For power cycling I had the grid disconnected for only a minute or so, not sure if this was enough to deplete the caps. Will try again next week for some longer, but any help on restoring it back to "info run" is very much appreciated!

Cheers.

I have a EM24 with sw version 1.6.48 and hw version 1.1.30.

I startet with Venus OS on a raspberry, a Wallbox with OpenWP and smarthomeNG which all poll the EM24 via ModBus. Then my setup run into this issue.

The EM24 was still pingable, the ModbusTCP port 502 was open, but the device did no longer reply to the requests. However I could revive the EM24 by changing the static IP address back and forth.

Now I changed the configuration so that the Venus OS polls the EM24 and acts as a ModbusTCP server for the wallbox and smarthomeNG. I hope the setup stays stable...

Hey there,

it seems that the general connection problems have been fixed, but there still seem to be problems when multiple devices connect to the EM24 (as @realhik also reports).

Next to the Cerbo GX, I also queried data from the EM24 using IOBroker and that might have led to lockups that I experience.

• Carlo Gavazzi EM24
  • Hardware v1.1.30
  • Firmware v1.6.48
  • Configured with static IP
• Cerbo GX
  • Firmware v2.84
  • Configured with static IP

I now also moved the IOBroker to query the data via the Cerbo GX instead of the EM24 directly and I will continue to monitor this. Nevertheless this should definitely be investigated by Carlo Gavazzi. Also an easy option to restart the ModbusTCP server on the EM24 without having to power cycle the device (and the entire house connected to it!) should really be implemented.

In general, I think an option to configure alerts in VRM for the case a device loses connection would also be very helpful for this and also other configurations.

So now after two weeks with the new EM24 there is the first lockup.

This is with FW 1.6.48, HW 1.1.30.

There is also an openWB wallbox which should read the EM24 through the gx device, I guess similar to how @realhik describes his system.

I would love this device to run properly, but maybe the RS485 model is a safer bet.

Hi,

I have the same Problem with the latest firmware on both, the EM24 Ethernet and the ColorControlGX.

I take notice of the problem when my ESS System is suddenly feeding max. power to the grid (once in ~2 weeks).
Then I have to switch off the breaker to reset it.

The CCGX is the only device accessing the EM24.

I have exactly the same lockup problem -- unfortunately with the latest firmware on both: Multiplus2 (2.84) and EM24 (1.6.48).

The EM24 runs fine for 1-2 weeks. Then, suddenly the Multiplus2 cannot connect any longer and goes into "PassThru" mode. Also the Carlo Gavazzi software cannot connect to it in that case.

My current workaround is to change the port, save settings and change it back to 502. Afterwards, the EM24 becomes available again immediately.

This is quite annoying.

The EM24 is configured to use a static IP (DHCP Off).

Hey,

so regarding the lockup issue - and maybe this is interesting for Victron staff as well - you don't need to power cycle the EM24 or change IP address/port. In my case, restarting the Cerbo is all it is needed, and the EM24 re-appears in the device list.

Good thing is, I don't have to be on site to fix the problem.

Bad thing is, it happened twice today.

System: 3 phase Multiplus2 (494), Cerbo (v2.84), CG EM24 (v1.6.48), Fronius Symo (on AC out), openWB wallbox

As @sviwowa said, this completely ruins ESS as it sets the Multiplus2 into pass through mode and Power limit on the Fronius is set to 0W.

Same issue here.

My EM24 looses connection after a couple of days and there is no chance to reconnect it. Unplug Ethernet cable or restart CerboGX does not help.

Fixed IP on both devices.

FW 1.6.48
HW 1.1.30

Has anyone an idea how we can solve this?

Another EM24 to go mad: EM24 1.1.30 fw 1.6.48 + Cerbo 2.84 & OpenWB access via "cerbo relais". The modbus log in the venus shows an error when the openWB (ip ...230) tries to access the EM24 (ID41).

My question: Is the "cerbo relais" the solution, or just forwarding the access to the EM24?

BTW: Due to this irrational behaviour we call 'em "The Italian" ;-) Pls Carlo G. fix your product soon, or dear Victrons change the ootb grid meter to a more stable product. Thx.

same problem here, with latest firmware on cerbo and em24, static ip ...

2 lockups in 1 week, do you know if Victron/CG is aware of this problem ?

not really an answer but :

https://community.victronenergy.com/questions/125793/shelly-3em-smartmeter-with-venusos-cerbo-gx.html?childToView=131116#answer-131116

Dear @mvader (Victron Energy)!

Can you give us please some insides if Victron is working on this topic?

Same issue here. Newest Cerbo an EM24 release. Fixed IPs.

That's definitely not a reliable and stable system. I hope Victron is fixing that asap.

I had a deeper look into the modbus-client log files of the cerbo.

There are several and repeating errors

Error reading registers 0x00-0x4f: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] Incomplete message received, expected atytes (0 received)

Just after this error messages, the EM24 is noted as device failed. 30-60seconds after this log entry the device is found again and registered on d-bus.

But today was different, a background scan was started after the device fail. The scan was completed but there was no registration of the device, so the device list remains empty.

Maybe this is the case also in your environment, just check /var/log/dbus-modbus-client

@mvader (Victron Energy)

Hi all,

maybe this could be helpful.
Today I received my new EM24 Ethernet with a preinstalled firmware version 1.7.3.

Don't know the changelog or where to get this version.

Maybe Victron can get hands on this version an provide a download.

Best Regards
Andreas

Hello,

I use the EM24 LAN in a separate VLAN and ask only via original Victron GX.

- Victron GX FW: 2.87

- Victron EM24: 1.73

Interesting:

I do not need to power off the EM24, after the Networkstack got confused. It is enough to deactivate DHCP mode in EM24, wait 10 seconds and activate DHCP again. After that he his alive again for round about 4 days.

Errors in modbus client logs (logfile attached):

• Error reading registers 0x00-0x4f
• Error reading registers 0xa100-0xa100

Questions:

- Might it be helpful to use a static IP instead of DHCP, or is the issue on the TCP Modbus level?

- Does a firmware downgrade to 5110394.1.6.30.21010801.bin (from Victron Proffessional) help?

See modbus client logs attached.

modbusclient.txt

Looks like Victron is providing latest 1.7.x Firmware.

Hi,

The lockup issue is still existent with EM24 Firmware v1.7.3 and CCGX v2.90~14 .

This is getting really annoying.

It would be nice to know if it makes sense to wait for a solution from victron any longer or install the RS485 version.

try to install firmware from 1.63 to 1.73 goes wrong, now i can't connect anymore with ucs7 to em24.

power off for 30s, doesn't help

change ip or dhcp, doesn't help

no other device online , when to connect em24

try with gx devices to scan for modbus tcp, no devices

ping works

any ideas or protokoll to connect or reset ?

still having problems with the EM24 - it is running about a week after latest victron update... no connection over modbus, EM24 is pingable after changing the static ip from the EM24 to another and back again it is working again.

I had a locked up EM24 after it worked for several hours. In the end found the problem, the static IP adress I had set was already in use by another device. Assigning a not used adress fixed the issue. Fun ;)

Also two questions.

• I do have the firmware file downloaded. But the ucs software asks for an Authorization Code to update the firmware. Where can i find such Authorization Code?
• Is the firmware from Victron compatible with the model EM24DINAV23XE1X? I wonder if applying the Victron firmware could brick the EM24DINAV23XE1X.

Hi folks. now im back from this lockup.

Yesterday i fiddled around with Home Assistant. and configured it to connect to Carlo by modbus.
And then seeing matthijs answer about not to overload the EM24 to much. i deleted all my config in Home Assistant (For now)

and did the port change localy on the EM24 and turned DHCP of.

so now its working. for how long. we will se.

After a few weeks of working, my EM24 has now locked up and won't let me connect. Reading this thread a month ago, I stopped connecting to the meter with UCS from my PC, leaving my Venus GX (most recent version) to communicate with it.
When I connect my laptop directly to the meter, It says connected, but when click to open it says disconnected. Is there a way to reset the meter from the joystick on the unit itself?

Hello,
my Multiplus-II GX was working since 2 days and now I have the first lockup of the EM24. Switching on/off dhcp did the trick but this is not a solution.

Firmware: 1.7.3
Hardware: 1.1.30

Multiplus GX and EM24 is connected through an ethernet switch and wifi is off. GX is the only device that is checking the EM24. All devices use static IP, no dhcp.

I've checked this discussion and it seems there is no working solution right now?

If so I ask my dealer to change to the RS485 Version or buy the elgris device.
Chris

So let's face it: EM24 Ethernet is a shixxx, not usable product.

I am wondering why everybody is so friendly and trying to work around? It's a completely overpriced 3phase counter so we can expect it works! @Victron, what solution will you provide? This discussion is almost ongoing for 2 years!?!

I have the same, also upgraded to latest firmware. No other device accessing the EM24 (the OpenWBs directly connect to the Cerbo). Problem even occurs when OpenWB is not accessing at all. I have the lock-issue between all 5-7 minutes and 3-4 hours. Most often <10 Minutes.

Please get it done or otherwise exchange with the RS-Version foc.

Can Victron please give us a statement here? My 28KWh battery + MPPTs are completely useless due to this faulty device.

Thank you in advance!

Thank you, this was helpful! @chrisu

Last 24h, no lockup / problem occured!

This is the way to the solution;

nano (editor) opens the .py file:

For me it even worked with 1.5 seconds:

If it's THAT obvious, why is Victron not able to guide us there / change the standard settings accordingly?

just to double check; I had issues because I assigned a static ip address which was already in use. If not yet done, validate you have assigned unique adresses.

In case you wouldn't know how to check, for example, unplug the ethernet cable from the EM24 (probably easier to unplug it on the switch side) and do a ping to the ip address of the EM24. If ping still replies, you have assigned double addresses. If it doesn't reply, then it is less likely.

Hi,

I just had a lockup, even with a min_timeout of 2.5
Very frustrating...

So I took a look into the dbus-modbus-client.py script.

It seems that the modbus client always runs with a interval time of 250ms. Isn't this too fast? I thought that the internal refresh time of venus is only 1 second or so, so it makes no sense to have a higher refresh rate ? I set it to 500ms, let's give it a try.
Anyone knows the refresh time of the em24 itself?

In addition, I added this contant:

pymodbus.constants.Defaults.Retries = 0

Default is 3 according to th pymodbus manual, so the connection should now be dropped after the first failed reading, and not after 3 which also has an impact on response time.
Let's see if anything changes. I'm not a pro of this, Victron should fix this problem first and not simply add new ABB Meters.

First time, since I installed it 3 months ago, i had this problem with the "EM24 disconnect" issue. However, in my case a simple reboot of the cerbo (V2.92) did solve this problem

Switch the EM24 Port (502 to 501) at the device, also work without reboot

Habe zwei EM 24 Ethernet die alle 10-20 Tage aussteigen. Nie beide gleichzeitig.

Ist wirklich traurig, das hier zu lesen und seitens VICTRON keine Lösung in Sicht ist.

Mein System kostet über 10.000€ und läuft nicht, wegen dem dummen EM 24.

Leider habe ich keine Möglichkeit aus RS485 zu wechseln.

Habe auch immer wieder disconnect beim EM24. Hab mich an den Hersteller gewendet.

Leider fühlt sich die Carlo Gavazzi GmbH nicht verantwortlich.

Antwort erste mail:

"ich vermute, da es sich auf Victron bezieht, handelt es sich um einen EM24, der nur für Victron hergestellt wird. Wenn dies der Fall ist, dann kann ich Sie leider nicht weiter beraten. "

Antwort zweite mail:

"Hallo Herr ...,
tut mir leid, aber der EM24DINAV23XE1X29 ist leider ein kundenspezifisches Produkt, über die ich keine Auskunft geben kann und auch keine Informationen habe. Sie müssen sich bei Ihrem Verkäufer erkundigen.

Mit freundlichen Grüßen / Best regards
Dr.-Ing..........
Field Application Engineer
Product Sales Support
*************************
Carlo Gavazzi GmbH"

Wenn Carlo Gavazzi nicht zuständig ist, dann sollte Victron das Problem lösen bevor die EM24 keine Garantie mehr haben! Victron macht auf seiner Homepage immer noch Werbung für das Produkt und es gibt dort keinen Hinweis auf die Probleme.

Über eine Stellungnahme von Victron würde ich mich sehr freuen.

Mfg

Michael

Habe zwei EM24 verbaut natürlich Ethernet.

Fallen beide ständig aus.

Es ist ein Witz das nicht geholfen wird.

Ganz lieben Gruß an Victron. Bitte macht eure Hausaufgaben.

@jailbraik: Mein EM 24-ETH mit fester IP hat sich immer zwischen einem Tag und drei Tage verabschiedet. Seit ich den automatischen Scan für die Mod-Bus Geräte im Cerbo deaktiviert habe, läuft er auch schon mal länger durch.

Ich werde ihn aber trotzdem gegen die RS485 Variante tauschen.

Ist mir alles zu unsicher.

To the Victron Staff: please find a solution for this EM24 ETH issue!!!!

I have an em24 with ethernet and no issues since i updated to 1.7.3 and made sure it had a good ip address, no lockup ever. I have only one device querying it, maybe that helps? Sometimes i connect with the ucs to see data directly.

Da heute mal wieder mein EM24 ausgestiegen ist, sei mir die Frage erlaubt, ob da Victron jemals gedenkt das Thema anzugehen.

Spannend ist ja, dass die Aussetzer total random kommen. Mal hält es 2 Tage, dann wieder 3 Monate und alles dazwischen ist möglich.

Als Workaround habe ich mir jetzt mal nen shelly 1 bestellt und werde den an den N vom EM24 packen und den jede nach mal für 30 Sekunden abschalten. Ist zwar mega traurig, aber vielleicht klappt das ja.

Wenn man sich ansieht, dass das Thema aus 2020 kommt, immer noch aktuell ist und kein Lösung angeboten wird, ist schon traurig. Ebenfalls traurig, dass die Produktkombination immer noch beworben wird.

Meiner ist auch auf 1.7.3 und steigt regelmäßig aus. Cerbo sowie der Rest sind up to date...

Finde auch schwach, dass bis jetzt keine Lösung vorhanden ist.

@mvader (Victron Energy) ,

Hi,

it seems a new firmware is out for the EM24, version 1.8.3, if you look at the post below from basd-scho of march 12th 2023.

Could you please upload it to the Victron Professionnal fimrware dowload site to make it available? As far as the post says, it is operating fine....

Thank you,

Hello,

unfortunately I tried to upgrade from 1.7.3 to 1.8.3. All upgrades during the last year went fine. But that one did not work. It upgraded normally, but now I get the info "boot". I can ping but not connect. Port changes or multiple power disconnects did not change anything ...

Does anyone has a good idea? @mvader (Victron Energy)

See pictures below:

Hello,

Thanks to the amazing Victron 3rd Level support, which emailed me pro active! I got all fixed and running again.

Technically it could happen in a firmware update (rarely) that a EM24 get stuck in boot mode, like you can see it in my screenshot. In this case please email (removed by moderator; that email address is nor supposed to be public) and they can help you.

Best regards

Sebastian