Custom driver issue in 3.50-15

Hello,

I have a custom dbus-modbus-client driver for Satec power meter(s), which stopped working in 3.50-15 with weird feedback.

This is quote from logfile in 3.40-36:

4000000066ce53f902b5ac14 *** CCGX booted (0) ***
4000000066ce53f93a666e8c *** starting dbus-modbus-client ***
4000000066ce540624ce9d74 INFO Waiting for localsettings
4000000066ce5406250e0004 INFO waiting for settings
4000000066ce5409192e7ad4 INFO registered ourselves on D-Bus as com.victronenergy.modbusclient.tcp
4000000066ce540932c5083c INFO Satec Probing
4000000066ce5409339f7a1c INFO Satec Probing done
4000000066ce540933c040bc INFO [tcp:10.9.8.40:502:1] Found Satec_EM133
4000000066ce54093424a00c INFO Satec device init
4000000066ce540938667424 INFO Satec register Phase 1
4000000066ce540938aa3f9c INFO Satec register Phase 1 done
4000000066ce540939545e64 INFO Satec register Phase 2
4000000066ce540939b4a2ec INFO Satec register Phase 2 done
4000000066ce54093a2ea54c INFO Satec register Phase 3
4000000066ce54093a803c04 INFO Satec register Phase 3 done
4000000066ce540a001d2eb4 INFO Satec set Registers
4000000066ce540a0074a554 INFO Satec device init done
4000000066ce540a355c54ec INFO registered ourselves on D-Bus as com.victronenergy.grid.satec_1061402

Here is from 3.50-15:

4000000066d0d8bb011434fc *** CCGX booted (0) ***
4000000066d0d8bb34d3a8a4 *** starting dbus-modbus-client ***
4000000066d0d8c91e86a8bc INFO dbus-modbus-client.py v1.58
4000000066d0d8c9218be9dc INFO Waiting for localsettings
4000000066d0d8c921c0e45c INFO waiting for settings
4000000066d0d8cb2a3da6ec INFO registered ourselves on D-Bus as com.victronenergy.modbusclient.tcp
4000000066d0d8cc02f25754 INFO [tcp:10.9.8.40:502:1] Found Generator controller: CRE Technology Gensys Compact Prime
4000000066d0d8cc1749dc54 INFO [tcp:10.9.8.40:502:1] Found Generator controller: CRE Technology Gensys Compact Prime
4000000066d0d8d61dde3b8c INFO [tcp:10.9.8.40:502:1] Found Generator controller: CRE Technology Gensys Compact Prime
4000000066d0d8e01cd1c8e4 INFO [tcp:10.9.8.40:502:1] Found Generator controller: CRE Technology Gensys Compact Prime

Somehow Venus now recognizes it as a generator. Productid is 0xFFFF in driver.

What could be wrong?

Update.

I commented “import cre” in dbus-modbus-client.py, and Satec meter now works.

Question is why Venus began detecting meter as generator?

4000000066d1dade02ffad64 *** CCGX booted (0) ***
4000000066d1dade353ec29c *** starting dbus-modbus-client ***
4000000066d1daea24dbef9c INFO dbus-modbus-client.py v1.58
4000000066d1daea28914eac INFO Waiting for localsettings
4000000066d1daed00b93fd4 INFO registered ourselves on D-Bus as com.victronenergy.modbusclient.tcp
4000000066d1daed1b9b2d44 INFO Satec Probing
4000000066d1daed1c1cec1c INFO Satec Probing done
4000000066d1daed1cef18cc INFO [tcp:10.9.8.40:502:1] Found Energy meter: None Satec_EM133
4000000066d1daed1d6ae04c INFO Satec device init
4000000066d1daed23437164 INFO Satec register Phase 1
4000000066d1daed249c5a44 INFO Satec register Phase 1 done
4000000066d1daed253857dc INFO Satec register Phase 2
4000000066d1daed25982f04 INFO Satec register Phase 2 done
4000000066d1daed272ff98c INFO Satec register Phase 3
4000000066d1daed284011cc INFO Satec register Phase 3 done
4000000066d1daed28a693fc INFO Satec set Registers
4000000066d1daed28baac84 INFO Satec device init done
4000000066d1daee33b04acc INFO registered ourselves on D-Bus as com.victronenergy.grid.satec_1061402