DSMR 2.2 with FT232 P1-kabel: connects, then nothing

[mdbijl]

I have a Kamstrup 382JxC meter (DSMR V2.2). After upgrading Home Assistant somewhere along the way it stopped working. I installed dsmr-console to start debugging.

My assumption are that the Home Assistant integration and dsmr-console are using dsmr_parser, right? If not, please discard this issue.

I have tested on two different devices:

• Raspberry Pi 4 with RaspOS Wormwood, Python 3.11.2.
• MacBook M1, Python 3.11.2.

I tested with two different cables. I also tested on another meter: both of the cables work with a meter in the office (Kaifa 15022 meter, DSMR V4)

Below are the repsonses when running dsmr_console:

Raspberry

./dsmr_console --device /dev/ttyUSB1 --version 2.2 --verbose
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:dsmr_parser.clients.protocol:connected

MacBook

./dsmr_console --device /dev/tty.usbserial-AR54FX3V  --version 2.2 --verbose
DEBUG:asyncio:Using selector: KqueueSelector
DEBUG:dsmr_parser.clients.protocol:connected

After this there is no more logging. Until I ^C:
^CINFO:dsmr_parser.clients.protocol:disconnected because of close/abort.

When on my MacBook I connect with CoolTerm with 9600 7E1 with hardware flow control of and software flow control either on or off it does connect. I see one dot character coming in. Then nothing. I this expected with the DSMR 2.2 protocol?

Hypothesis

My hypothesis is that either my meter is in some state where it stopped sending DSMR 2.2 telegram or that something changed in dsmr-console which stopped it to work.

[dupondje]

You could test with screen or something on the ttyUSB and see if you receive some data. But as it gives no output, I think the meter stopped giving dsmr messages.