Maybe some upgrade errors are because of skipping some intermediate versions. Try to uninstall the addon and install/reconfigure it again (just note down your settings somewhere).
Note, last addon version is 1.2.0 so press the “Check for Updates” button first in the Add-on Store.
copied the yaml configuration
and reinstalled and pasted back configuration on line 2 (ENABLE_INGRESS: false is new)
and it works again
(btw this ingress inclusion is really nice)
I had turned off the auto update after the timescaledb problems
so i was a bit hesitant with the autoupdate, but only skipped due to pending one update
I got no new readings… the website is working but no actual data. I use a ip slimmemetergateway that I also have in Domoticz. with the same settings I see there new readings. but the addon gives me an error in the log. (this is after the update to 2022.06 i think (after the update dsmr reader got no new readings)
022-06-02 23:12:57,120 ERROR mixins run_once 103 | dsmr_datalogger.management.commands.dsmr_datalogger: [!] Exception raised. Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/serial/urlhandler/protocol_socket.py", line 171, in read
raise SerialException('socket disconnected')
serial.serialutil.SerialException: socket disconnected
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/dsmr_backend/mixins.py", line 92, in run_once
self.run(data=self.data, **options)
File "/app/dsmr_datalogger/management/commands/dsmr_datalogger.py", line 29, in run
telegram = next(self.telegram_generator)
File "/app/dsmr_datalogger/scripts/dsmr_datalogger_api_client.py", line 53, in read_telegram
incoming_bytes = serial_handle.read(MAX_BYTES_PER_READ)
File "/usr/local/lib/python3.10/site-packages/serial/urlhandler/protocol_socket.py", line 178, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: socket disconnected
After months of flawless operation, my reader suddenly stopped working. I have tried re-installing the add-on, restarting the host, etc. But unfortunately that did not work out.
RuntimeError: ('Failed to connect: {}', SerialException(12, "could not open port /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A13LNT9A-if00-port0: [Errno 12] Out of memory: '/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A13LNT9A-if00-port0'"))
127.0.0.1 - - [04/Jun/2022:22:37:24 +0200] "GET /about HTTP/1.1" 200 19065 "-" "curl/7.80.0" "-"
127.0.0.1 - - [04/Jun/2022:22:37:29 +0200] "GET /about HTTP/1.1" 200 19065 "-" "curl/7.80.0" "-"
Starting DSMR Reader - datalogger...
Current logging level set to "ERROR". More information can be found here: https://dsmr-reader.readthedocs.io/en/latest/how-to/troubleshooting/enabling-debug-logging.html
127.0.0.1 - - [04/Jun/2022:22:37:35 +0200] "GET /about HTTP/1.1" 200 19065 "-" "curl/7.80.0" "-"
2022-06-04 22:37:35,334 ERROR mixins run_once 103 | dsmr_datalogger.management.commands.dsmr_datalogger: [!] Exception raised. Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/serial/serialposix.py", line 322, in open
self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
OSError: [Errno 12] Out of memory: '/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A13LNT9A-if00-port0'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/dsmr_datalogger/scripts/dsmr_datalogger_api_client.py", line 37, in read_telegram
serial_handle = serial.serial_for_url(url=url_or_port, timeout=MAX_READ_TIMEOUT, **serial_kwargs)
File "/usr/local/lib/python3.10/site-packages/serial/__init__.py", line 90, in serial_for_url
instance.open()
File "/usr/local/lib/python3.10/site-packages/serial/serialposix.py", line 325, in open
raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))
serial.serialutil.SerialException: [Errno 12] could not open port /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A13LNT9A-if00-port0: [Errno 12] Out of memory: '/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A13LNT9A-if00-port0'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/dsmr_backend/mixins.py", line 92, in run_once
self.run(data=self.data, **options)
File "/app/dsmr_datalogger/management/commands/dsmr_datalogger.py", line 29, in run
telegram = next(self.telegram_generator)
File "/app/dsmr_datalogger/scripts/dsmr_datalogger_api_client.py", line 39, in read_telegram
raise RuntimeError('Failed to connect: {}', error)
I have uninstalled reinstalled. And tested with ingress and normal.
In my config there is a USB but I use ipv4 slimme metergateway. Maybe my config can help?
I can’t remember that I have changed something and because of that I don’t know the config from last month…
I see that you specified some settings like ‘DSMRREADER_REMOTE_DATALOGGER_API_HOSTS’ which you don’t need.
As you are using a remote datalogger which sends data over to this addon, please reset the settings of the addon, configure your db settings, set the mode to receiver and open up the port in the network settings of the addon.
In the admin ui, you need to activate the API and get the KEY.
Then in the ‘slimme metergateway’ you configure the correct HA ip + port you opened up (7777?) and the KEY.
I’m on vacation. But emptied the fields, you said. The website is working, but no new meters and same error.
The gateway is working on the 82 up and port 23.
Hi, I would like to recalculate the prices but I can’t get it to change.
When I try to do it with ssh I get the following error: django.db.utils.OperationalError: could not translate host name “dsmrdb” to address: Name does not resolve
I use this command: python manage.py dsmr_stats_recalculate_prices
When I do this using portainer I get the same error.
Can someone point me in the right direction.
For me it would be a lot easier to have a button in the webinterface.