After a smartmeter switch initiated by the energy infrastructure company there is no data coming through over the P1 connection on my FLM2b, and no data is sent to pvout. I have switched to DSMR 4 and back to 2.2 to no avail. Last part of syslog attached below, device is on firmware 250
I have no clue what is going on or what I can do to get it working again. Any help is greatly appreciated.
Jaap
Jan 1 00:01:06 flukso-297d47 user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:06 flukso-297d47 daemon.info supd[680]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Jan 1 00:01:07 flukso-297d47 daemon.info spid[683]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Jan 1 00:01:07 flukso-297d47 user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:07 flukso-297d47 user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:07 flukso-297d47 daemon.info fluksod[686]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Jan 1 00:01:08 flukso-297d47 user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:08 flukso-297d47 daemon.info tmpod[689]: Sucessfully started with DEAMON=tmpod and DAEMON_PATH=/var/run/tmpod
Jan 1 00:01:09 flukso-297d47 user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:09 flukso-297d47 daemon.info parsed[695]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Jan 1 00:01:10 flukso-297d47 user.info sysinit: Daemon returned 0 as return value.
Jan 1 00:01:10 flukso-297d47 daemon.info kubed[698]: Sucessfully started with DEAMON=kubed and DAEMON_PATH=/var/run/kubed
Jan 1 00:01:19 flukso-297d47 user.info heartbeat[701]: POST https://api.flukso.net/device/297d47846b1c53d0d14010173d7c9895: 200
Jan 1 00:01:21 flukso-297d47 daemon.info supd[680]: Received event START for ntp
Sep 14 17:15:30 flukso-297d47 cron.err crond[576]: time disparity of 24564554 minutes detected
Sep 14 17:30:01 flukso-297d47 cron.info crond[576]: crond: USER root pid 774 cmd /usr/bin/fcheck
Sep 14 17:45:02 flukso-297d47 cron.info crond[576]: crond: USER root pid 819 cmd /usr/bin/fcheck
Sep 14 18:00:01 flukso-297d47 cron.info crond[576]: crond: USER root pid 864 cmd /usr/bin/fcheck
Sep 14 18:01:01 flukso-297d47 cron.info crond[576]: crond: USER root pid 885 cmd /usr/bin/heartbeat 0
Sep 14 18:01:03 flukso-297d47 user.info heartbeat[886]: POST https://api.flukso.net/device/297d47846b1c53d0d14010173d7c9895: 200
Sep 14 18:14:05 flukso-297d47 daemon.notice netifd: wan (468): Sending renew...
Sep 14 18:14:05 flukso-297d47 daemon.notice netifd: wan (468): Lease of xxx.xxx.xxx.xxx obtained, lease time 7200
Sep 14 18:15:01 flukso-297d47 cron.info crond[576]: crond: USER root pid 950 cmd /usr/bin/fcheck
See https://www.flukso.net/content/no-reading-p1-kamstrup and check if this corresponds to your issue.
Thank you for your answer.
It is not quite the same because after cat /dev/ttyS0 there is no data at all. When I do cat /dev/ttyS0 there is nothing and I have to issue ctr-c in Putty to come back to prompt.
So it seems there are posts in syslog with confirm value 200 but no telegram or any data actually.
I am hesitant to use fp1. Dont know really what will happen and don't want make matters worse.
Jaap