This beta doesn’t support ethernet port and VE direct connected devices. My energy meter was off and all MPPTs in stand by.
Roll back to ~48 was very helpfull.
Today morning the same. No ethernet port. installation in pass throught mode. Roll back to official release 3.54. Cerbo MK2 should be the problem. It’s one of the Cerbos without existing CAN2
Mine talks fine to several devices on ve.direct on the standard connector and over USB.
I can’t get a modbus tcpip device to work with a new MK3 Cerbo using ~49 or production.
I think something else went wrong, no issues found so far with connectivity to devices, no changes have been made that would affect that.
Do you have any modifications loaded?
Yes I do have some 3rd part drivers loaded for the BMS, and additional temperatures and a tank. My original Cerbo and Cerbo-S both communicate with the modbus tcpip device using node red with those same drivers. The MK2 device has never communicated, using any level of firmware.
Much like my original original Cerbo and Cerbo-S both will work with a node red dashboard, the MK2 will not. I dropped back to production software in the MK2 and the GUI still seized up last night on wifi, and would not connect on BT, but I noticed the serial driver for the BMS was still being polled for data.
It’s unclear if it’s a defective unit, an issue with the new design, firmware that doesn’t play well with the MK2, or pilot error?
Can you point me to the logging locations that I should be looking at.