search

dm82m / hass-Deltasol-KM2

Custom component for retrieving sensor information from Resol KM1/KM2, DL2/DL3, VBus/LAN, VBus/USB
MIT License
25 stars 6 forks source link

Error #43

Closed freddy357 closed 3 months ago

freddy357 commented 3 months ago

--- VERSIONS --- add-on version: 0.0.7 nodejs version: v22.3.0 npm version: 10.8.1 --- DEVICES --- /dev/ttyUSB0 ls: cannot access '/dev/ttyACM*': No such file or directory --- json-live-data-server --- debug: Starting server... debug: Connect to VBus data source... error: Main function returned with error: error: Error: Unable to connect at cleanup (/bin/resol-vbus/src/serial-connection.js:157:28) at SerialPort.onSerialPortError (/bin/resol-vbus/src/serial-connection.js:94:17) at SerialPort.emit (node:events:520:28) at SerialPort._error (/bin/resol-vbus/node_modules/@serialport/stream/dist/index.js:78:18) at /bin/resol-vbus/node_modules/@serialport/stream/dist/index.js:111:18

Logger: py.warnings Source: util/loop.py:131 First occurred: 19:44:49 (1 occurrences) Last logged: 19:44:49

/config/custom_components/deltasol/sensor.py:50: SyntaxWarning: invalid escape sequence '\d' vol.Optional(CONF_API_KEY): config_validation.matches_regex("\d\d"),

dm82m commented 3 months ago

Would say that your config file is not correct, this is more related to neolink, please file an issue at Andy’s repo: https://github.com/QuantumEntangledAndy/neolink/issues see further comments

freddy357 commented 3 months ago

I will do that, thanks

Op do 13 jun 2024 om 19:56 schreef Dirk @.***>:

Would say that your config file is not correct, this is more related to neolink, please file an issue at Andy’s repo: https://github.com/QuantumEntangledAndy/neolink/issues

— Reply to this email directly, view it on GitHub https://github.com/dm82m/hass-Deltasol-KM2/issues/43#issuecomment-2166449017, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEEGW4DWF3HOLOCJ56BITKTZHHMNJAVCNFSM6AAAAABJI37YXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRWGQ2DSMBRG4 . You are receiving this because you authored the thread.Message ID: @.***>

freddy357 commented 3 months ago

Oke so there is no neolink error or indication that it even tried to start neolink.

So do you now where i can solve this issue?

--- VERSIONS --- add-on version: 0.0.7 nodejs version: v22.3.0 npm version: 10.8.1 --- DEVICES --- /dev/ttyUSB0 /dev/ttyACM0 --- json-live-data-server --- debug: Starting server... debug: Connect to VBus data source... error: Main function returned with error: error: Error: Unable to connect at onSocketTermination (/bin/resol-vbus/src/tcp-connection.js:368:26) at Socket.onError (/bin/resol-vbus/src/tcp-connection.js:401:17) at Socket.emit (node:events:520:28) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

dm82m commented 3 months ago

Please reinstall the addon so that you are on version 0.0.9

dm82m commented 3 months ago

Ahhhhh stop it. I was wrong! You are trying to use the resol stuff. Has nothing todo with Andy or neolink.

You need to ask for help here: https://github.com/danielwippermann/resol-vbus/issues

dm82m commented 3 months ago

And please also directly post your config there. I assume that the config is wrong or my addon cannot reach your resol device.

dm82m commented 3 months ago

Continues here: https://github.com/danielwippermann/resol-vbus/issues/103