See no issues in the log right? Do you see live data? And how is everything connected?
hmm very strange but now it works 
When I try to use the API with the python script below I got an 404 (not found) error? Does anyone have an idea? DSMR reader API is enabled and the key is correct…
Thanks!
import requests
import json
response = requests.get(
'http://IP_OF_HASS:8123/v2/datalogger/dsmrreading',
headers={'X-AUTHKEY': 'YOUR-API-KEY'},
)
if response.status_code != 200:
print('Error: {}'.format(response.text))
else:
print('Response: {}'.format(json.loads(response.text)))
Yes, live graphs do work. Here I can also go back several days via the graph. However, the archive tab has not been updated since May. It is connected via a USB serial adapter directly to the P1 port and to the home assistant hardware.
Did you also check the official docs on this? Common error resolution: How do I fix Day statistics are lagging behind? — DSMR-reader v5 documentation
1 Like
it seems like the process keeps restarting? The time of upload day and our statistics keeps moving up automatically?
2023-10-25 21:43:01,341 DEBUG mixins run_loop 79 | dsmr_datalogger.management.commands.dsmr_datalogger: Sleeping 2.0s
2023-10-25 21:43:01,793 DEBUG schedule execute_scheduled_processes 31 | SP: 1 backend service(s) ready to run
2023-10-25 21:43:01,794 DEBUG schedule execute_scheduled_processes 34 | SP: Running "Generate consumption data" (dsmr_consumption.services.run)
2023-10-25 21:43:01,853 DEBUG services compact 211 | Compact: Processed reading: 15038987 @ 2023-10-25 21:43:14+02:00
2023-10-25 21:43:01,859 DEBUG schedule reschedule 78 | SP: Rescheduled "Generate consumption data" to 2023-10-25 21:43:02.854325+02:00 (ETA 0:00:00.999862)
2023-10-25 21:43:01,871 DEBUG mixins run_loop 79 | dsmr_backend.management.commands.dsmr_backend: Sleeping 1.0s
127.0.0.1 - - [25/Oct/2023:21:43:02 +0200] "GET /about HTTP/1.1" 302 0 "-" "curl/8.0.1" "-"
127.0.0.1 - - [25/Oct/2023:21:43:02 +0200] "GET /api/hassio_ingress/nCd8-Tq9MRR3XbaA19gnCCKrVRQjM4Z2A_PBxMwmUhM/admin/login/?next=/api/hassio_ingress/nCd8-Tq9MRR3XbaA19gnCCKrVRQjM4Z2A_PBxMwmUhM/about HTTP/1.1" 404 179 "-" "curl/8.0.1" "-"
2023-10-25 21:43:02,877 DEBUG schedule execute_scheduled_processes 31 | SP: 1 backend service(s) ready to run
2023-10-25 21:43:02,877 DEBUG schedule execute_scheduled_processes 34 | SP: Running "Generate consumption data" (dsmr_consumption.services.run)
2023-10-25 21:43:02,901 DEBUG schedule reschedule 78 | SP: Rescheduled "Generate consumption data" to 2023-10-25 21:43:03.895609+02:00 (ETA 0:00:00.999935)
2023-10-25 21:43:02,914 DEBUG mixins run_loop 79 | dsmr_backend.management.commands.dsmr_backend: Sleeping 1.0s
2023-10-25 21:43:03,347 INFO dsmr_datalogger_api_client read_telegram 31 | [2023-10-25 21:43:03.347179] Opening connection "/dev/ttyUSB0" using options: {'baudrate': 115200, 'bytesize': 8, 'parity': 'N', 'stopbits': 1, 'xonxoff': 1, 'rtscts': 0}
2023-10-25 21:43:03,683 DEBUG dsmr_datalogger_api_client read_telegram 58 | [2023-10-25 21:43:03.683892] Read 1 Byte(s)
2023-10-25 21:43:03,920 DEBUG schedule execute_scheduled_processes 31 | SP: 1 backend service(s) ready to run
2023-10-25 21:43:03,921 DEBUG schedule execute_scheduled_processes 34 | SP: Running "Generate consumption data" (dsmr_consumption.services.run)
2023-10-25 21:43:03,945 DEBUG schedule reschedule 78 | SP: Rescheduled "Generate consumption data" to 2023-10-25 21:43:04.940033+02:00 (ETA 0:00:00.999950)
2023-10-25 21:43:03,957 DEBUG mixins run_loop 79 | dsmr_backend.management.commands.dsmr_backend: Sleeping 1.0s
2023-10-25 21:43:04,018 DEBUG dsmr_datalogger_api_client read_telegram 58 | [2023-10-25 21:43:04.018326] Read 0 Byte(s)
2023-10-25 21:43:04,352 DEBUG dsmr_datalogger_api_client read_telegram 58 | [2023-10-25 21:43:04.352874] Read 0 Byte(s)
2023-10-25 21:43:04,687 DEBUG dsmr_datalogger_api_client read_telegram 58 | [2023-10-25 21:43:04.687132] Read 1038 Byte(s)
2023-10-25 21:43:04,694 DEBUG datalogger telegram_to_reading 81 | Received telegram:
/CTA5ZIV-METER
1-3:0.2.8(50)
0-0:1.0.0(231025214317S)
0-0:96.1.1(4530303639303030373136373634313231)
1-0:1.8.1(005301.872*kWh)
1-0:1.8.2(002604.579*kWh)
1-0:2.8.1(002569.540*kWh)
1-0:2.8.2(005987.702*kWh)
0-0:96.14.0(0001)
1-0:1.7.0(00.412*kW)
1-0:2.7.0(00.000*kW)
0-0:96.7.21(00064)
0-0:96.7.9(00086)
1-0:99.97.0(10)(0-0:96.7.19)(230130163918W)(0000435033*s)(230125154845W)(0002150597*s)(230125154845W)(0002150597*s)(230125154844W)(0002150597*s)(221231191715W)(0000003107*s)(221231191714W)(0000003107*s)(221231191714W)(0000003106*s)(221215045032W)(0023624233*s)(221215045032W)(0023624233*s)(221215045031W)(0023624232*s)
1-0:32.32.0(00015)
1-0:52.32.0(00020)
1-0:72.32.0(00010)
1-0:32.36.0(00013)
1-0:52.36.0(00011)
1-0:72.36.0(00013)
0-0:96.13.0()
1-0:32.7.0(235.0*V)
1-0:52.7.0(232.0*V)
1-0:72.7.0(232.0*V)
1-0:31.7.0(001*A)
1-0:51.7.0(000*A)
1-0:71.7.0(001*A)
1-0:21.7.0(00.187*kW)
1-0:41.7.0(00.032*kW)
1-0:61.7.0(00.155*kW)
1-0:22.7.0(00.000*kW)
1-0:42.7.0(00.000*kW)
1-0:62.7.0(00.000*kW)
!C8E2
2023-10-25 21:43:04,758 DEBUG mixins run_loop 79 | dsmr_datalogger.management.commands.dsmr_datalogger: Sleeping 2.0s
2023-10-25 21:43:04,962 DEBUG schedule execute_scheduled_processes 31 | SP: 1 backend service(s) ready to run
2023-10-25 21:43:04,962 DEBUG schedule execute_scheduled_processes 34 | SP: Running "Generate consumption data" (dsmr_consumption.services.run)
2023-10-25 21:43:05,018 DEBUG services compact 211 | Compact: Processed reading: 15038988 @ 2023-10-25 21:43:17+02:00
2023-10-25 21:43:05,028 DEBUG schedule reschedule 78 | SP: Rescheduled "Generate consumption data" to 2023-10-25 21:43:06.019640+02:00 (ETA 0:00:00.999966)
2023-10-25 21:43:05,046 DEBUG mixins run_loop 79 | dsmr_backend.management.commands.dsmr_backend: Sleeping 1.0s
2023-10-25 21:43:06,056 DEBUG schedule execute_scheduled_processes 31 | SP: 1 backend service(s) ready to run
2023-10-25 21:43:06,057 DEBUG schedule execute_scheduled_processes 34 | SP: Running "Generate consumption data" (dsmr_consumption.services.run)
2023-10-25 21:43:06,081 DEBUG schedule reschedule 78 | SP: Rescheduled "Generate consumption data" to 2023-10-25 21:43:07.076265+02:00 (ETA 0:00:00.999952)
2023-10-25 21:43:06,092 DEBUG mixins run_loop 79 | dsmr_backend.management.commands.dsmr_backend: Sleeping 1.0s
2023-10-25 21:43:06,764 INFO dsmr_datalogger_api_client read_telegram 31 | [2023-10-25 21:43:06.764109] Opening connection "/dev/ttyUSB0" using options: {'baudrate': 115200, 'bytesize': 8, 'parity': 'N', 'stopbits': 1, 'xonxoff': 1, 'rtscts': 0}
2023-10-25 21:43:07,097 DEBUG schedule execute_scheduled_processes 31 | SP: 1 backend service(s) ready to run
2023-10-25 21:43:07,098 DEBUG schedule execute_scheduled_processes 34 | SP: Running "Generate consumption data" (dsmr_consumption.services.run)
2023-10-25 21:43:07,101 DEBUG dsmr_datalogger_api_client read_telegram 58 | [2023-10-25 21:43:07.100942] Read 1 Byte(s)
2023-10-25 21:43:07,122 DEBUG schedule reschedule 78 | SP: Rescheduled "Generate consumption data" to 2023-10-25 21:43:08.116568+02:00 (ETA 0:00:00.999946)
2023-10-25 21:43:07,134 DEBUG mixins run_loop 79 | dsmr_backend.management.commands.dsmr_backend: Sleeping 1.0s
Hopefully, somebody can help me. I have a Raspberry Pi with Home Assistant installed using a Docker image. Now I’ve installed the USB P1 cable between my RPi and my Landis + Gyr E350 and added DSMR Reader to HA. Unfortunately, I do not receive any information. Is this because I use the HA Docker implementation or do I forget something else? Thanks for your help.
Good day,
I’ve had this since the new year. Can’t get DSMR to work properly anymore
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 01-set-hassio-vars: executing…
Home Assistant DSMR Reader Add-on - Release: 1.10.2
Home Assistant DSMR Reader Add-on - This addon is the latest version
Home Assistant DSMR Reader Add-on - Configuring addon settings
Home Assistant DSMR Reader Add-on - No port configured, configure a UI port in the Network options
[cont-init.d] 01-set-hassio-vars: exited 1.
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
I get that UI every time. But I really don’t know what to do
No port configured, configure a UI port in the Network options.
Thanks
Try to reset your configuration settings and set it up again?
thank you Sander for your response. don’t know what caused it. but I reinstalled dsmr, Metabase and timescale and re-entered all the settings and now it works again.
How do I update DSMR-reader?
HA wil let you know when i publish a new addon version. Update to 5.10.4? · Issue #80 · sanderdw/hassio-addons · GitHub
1 Like
I have the same issue, I’m following these steps Updating DSMR-reader — DSMR-reader v5 documentation but I don’t have a user ‘dsmr’
I have no idea how to add it, I’ve tried through the ‘normal steps’ of creating a user (made it admin and so on) but that didn’t seem to do the trick. I’ve run cat /etc/passwd and my own user pops up, but not the user dsmr
I think this is blocking me from proceeding to the next step
./deploy.sh
UPDATE: think I’ve gotten one step closer, but not there yet…
running this command
docker exec -it addon_0826754b_dsmr_reader bash
after which I failed to update again
UPDATE2:
I ran this command which updated the docker
docker pull xirixiz/dsmr-reader-docker:latest
However, still stuck at updating from v5.10.3 to a later version
Don’t update in the addon itself, the Home Assistant Addons architecture, which is based on Docker, is not build for updating things that way.
And regarding the 5.10.4 update, you really don’t need to update as it’s only a depandancy update, see Update to 5.10.4? · Issue #80 · sanderdw/hassio-addons · GitHub
I missed the v5.11 update, but here it is 
:
2024-03-18: DSMR Reader Add-on v 1.11.0, DSMR-reader v5.11
Changelog here
2 Likes
Installed the latest version (1.11.0) together with Timescale 4.0.1 and a up and running MSQT broker ( 6.4.0). But when i look at the entry’s like sensor.dsmr_current_month_electricity1 or sensor.dsmr_current_month_gas they tell me : unknown . When i look at the MSQT messages (using MSQT explorer) there enough information available. I already restart the Timescale add-on etc etc but nothing happens. Somebody who can guide me the way where to look
Hey Sander,
Thanks for the update 3 weeks ago. But since Timescale 4.0.1 (2 weeks now) i’m getting the warning back like last year (see: Link). Addon is using a “old version” of the "pg_dump” backup tool. Timescale 4.0.1 is working with Postgresql 16.2
Thanks for looking in to it.
p.s. How is it going with your son?
pg_dump: error: aborting because of server version mismatch
pg_dump: detail: server version: 16.2; pg_dump version: 15.6
2024-03-31 17:39:40,310 ERROR schedule execute_scheduled_processes 39 | (AttributeError) dsmr_backup.services.backup.run errored: 'NoneType' object has no attribute 'read'
Working with HA in VM (Proxmox)
So you see the DSMR Reader putting messages on the MQTT broker? Did you follow these instructions? DSMR Reader - Home Assistant
As the underlying image needs to support this i created a feature request: Postgresql client Upgrade (pg_dump) · Issue #351 · xirixiz/dsmr-reader-docker · GitHub
After this is done i can release a new version.
Thank you for asking, my son is doing really great and his older brother is taking good care of him 
.
3 Likes
Good to hear that all is going good Sander 
So mom and dad have a easy life 
And thanks for making the the request. We will see the update eventually 