ualex73 / docker-s0pcm-reader Goto Github PK

Since 11 februari 2023 the s0pcm-reader fails to work.
I have performed a restart of HA and this is the logging:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/config.sh
cont-init: info: /etc/cont-init.d/config.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023-02-15 11:28:35,142 ERROR: MQTT failed to connect to broker 'Connection Refused: unacceptable protocol version.', retrying.
2023-02-15 11:29:34,267 ERROR: MQTT failed to connect to broker 'Connection Refused: unacceptable protocol version.', retrying.
2023-02-15 11:32:54,783 ERROR: MQTT failed to connect to broker 'Connection Refused: unacceptable protocol version.', retrying.
2023-02-15 12:16:19,643 ERROR: MQTT failed to connect to broker 'Connection Refused: unacceptable protocol version.', retrying.

How can I solve this?
I have performed a Rollback to the state of 10 feb 2023.
This is the logging I get:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/config.sh
cont-init: info: /etc/cont-init.d/config.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

And it works now....

With kind regards,

René Kwee

Hi!

I have created this docker on a Raspberry Pi, and it seems I have not setup something correctly.
The S0PCM-5 is connected to solar pannels with 1000Imp/KwH (Algodue UEM80-4D R pulse meter)
There was one error reported, as I had no measurements.yaml, that was fixed automatically and now I can see in the measurements it is counting up, it was 0, now 22 (bad day of sun, running for half an hour)

date: 2023-04-24
1:
pulsecount: 22
today: 22
total: 15000701
yesterday: 0

The total is derrived from the current meter readout: 15000,69 (times 1000 impulses = 15000690)

I can see it registering in the Mosquitto 2.0.15, running unsecured :
1682323131: New client connected from 192.168.1.154:53265 as S0PCM (p2, c1, k60).
(This is on an Unraid cmccambridge/mosquitto-unraid Latest docker container)
But no data appears to be published.
I can only see the client reporting in on Mosquitto, no messages.
Mossquitto is connected to Home Assistant, but also there no device is visible as S0PCM (Or any other new ones)

configuration.yaml.txt
measurement.yaml.txt
s0pcm-reader.log.txt

Did I set it up wrongly?
Did I miss something?

Hoi Alexander,

Ik heb hulp nodig met het installeren van deze docker, kan echter geen contact info vinden.
Dus vandaar deze manier.
Wellicht kan je contact met mij opnemen [email protected]

Alvast bedankt,

Mede naamgenoot.

Currently the S0PCM-Reader doesn't support TLS, but encryption is important these days.

Errors are reported in the logfile, but it could be handy to send those too via a MQTT topic. This can be then shown in Home Assistant or a notification send. It is important we don't send a burst of these messages.

Currently the daily counters are reset at 00:00 and not stored. For history usage it could be interesting to log the daily count in a separate (e.g. CSV) file and/or publish the 'yesterday' count via MQTT at 00:00, this makes it possible to use InfluxDB/Grafana to visualize it.

The S0PCM-Reader doesn't support birth/Tombstone message yet, this could be handy to monitor if the container stops/fails etc and send a notification to your handset.