Open lordvalium opened 10 months ago
kellerza
commented
10 months ago Both debugs clearly show a timeout.
pymodbus.logging send: 0x1 0x3 0x0 0x3 0x0 0x5 0x75 0xc9I can fix the retry mechanism in the first log, but it won't solve your issue. Have you looked at the fault-finding page on the docs?
kellerza
commented
10 months ago The traceback in your first log should be solved now. But you will still have to look at the fault finding guide to get this working
Niruservices
commented
9 months ago Morning - I need some help please. I have an issue with opening the connection to the solarman dongle; "pysolarmanv5.pysolarmanv5.NoSocketAvailableError: Cannot open connection to 192.168.1.186" The connect call fails and I read that it could be something to do with the encryption on the dongle - I am trying via a RPi. If I use a the RS485 - which port to use (CAN is occupied with BMS)? Also, where can I get the applicable cable?
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
On MQTT:
023-09-26 07:48:10: Sending PINGRESP to 0Loy1diDJ1jYSdF5mD9cav
2023-09-26 07:49:10: Received PINGREQ from 0Loy1diDJ1jYSdF5mD9cav
2023-09-26 07:49:10: Sending PINGRESP to 0Loy1diDJ1jYSdF5mD9cav
2023-09-26 07:49:52: New connection from 172.30.32.2:48572 on port 1883.
2023-09-26 07:49:52: Client
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun sunsynk (no readiness notification)
s6-rc: info: service legacy-services successfully started
20:21:31 INFO Loading configuration: /data/options.json
20:21:31 INFO sunsynk library version: 0.6.4
20:21:31 INFO Schedules:
+-----------+-----+------+--------+-----------+----------+------------+
| Key | src | Read | Report | Change by | Change % | Change any |
+-----------+-----+------+--------+-----------+----------+------------+
| date_time | | 60 | 60 | | | True |
| rw | | 5 | 300 | | | True |
| w | * | 20 | 60 | 80 | | |
| kwh | | 300 | 300 | | | |
| any_unit | | 15 | 300 | | | |
| no_unit | | 15 | 300 | | | True |
+-----------+-----+------+--------+-----------+----------+------------+
20:21:31 INFO Using three phase sensor definitions.
20:21:31 ERROR Unknown sensor specified: aux_power
20:21:31 ERROR Unknown sensor specified: essential_power
20:21:31 ERROR Unknown sensor specified: grid_connected
20:21:31 ERROR Unknown sensor specified: inverter_current
20:21:31 ERROR Unknown sensor specified: load_frequency
20:21:31 ERROR Unknown sensor specified: non_essential_power
20:21:31 INFO Added hidden sensors as other sensors depend on it: Rated power, Serial
20:21:31 INFO Connecting to tcp://192.168.1.186:8899
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/pysolarmanv5/pysolarmanv5_async.py", line 68, in connect
self.reader, self.writer = await asyncio.open_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/streams.py", line 48, in openconnection
transport, = await loop.create_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1085, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1069, in create_connection
sock = await self._connect_sock(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 973, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 634, in sock_connect
return await fut
^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 674, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.1.186', 8899)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "
Niruservices
commented
9 months ago Sorry, some copy error.... MQTT in the wrong place;
Niruservices
commented
9 months ago Add-on (multi) Deye 12Kw 3 Phase
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
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun sunsynk (no readiness notification)
s6-rc: info: service legacy-services successfully started
20:21:31 INFO Loading configuration: /data/options.json
20:21:31 INFO sunsynk library version: 0.6.4
20:21:31 INFO Schedules:
+-----------+-----+------+--------+-----------+----------+------------+
| Key | src | Read | Report | Change by | Change % | Change any |
+-----------+-----+------+--------+-----------+----------+------------+
| date_time | | 60 | 60 | | | True |
| rw | | 5 | 300 | | | True |
| w | * | 20 | 60 | 80 | | |
| kwh | | 300 | 300 | | | |
| any_unit | | 15 | 300 | | | |
| no_unit | | 15 | 300 | | | True |
+-----------+-----+------+--------+-----------+----------+------------+
20:21:31 INFO Using three phase sensor definitions.
20:21:31 ERROR Unknown sensor specified: aux_power
20:21:31 ERROR Unknown sensor specified: essential_power
20:21:31 ERROR Unknown sensor specified: grid_connected
20:21:31 ERROR Unknown sensor specified: inverter_current
20:21:31 ERROR Unknown sensor specified: load_frequency
20:21:31 ERROR Unknown sensor specified: non_essential_power
20:21:31 INFO Added hidden sensors as other sensors depend on it: Rated power, Serial
20:21:31 INFO Connecting to tcp://192.168.1.186:8899
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/pysolarmanv5/pysolarmanv5_async.py", line 68, in connect
self.reader, self.writer = await asyncio.open_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/streams.py", line 48, in openconnection
transport, = await loop.create_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1085, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1069, in create_connection
sock = await self._connect_sock(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 973, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 634, in sock_connect
return await fut
^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 674, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.1.186', 8899)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "
Niruservices
commented
9 months ago MQTT:
2023-09-26 07:52:10: Sending PINGRESP to 0Loy1diDJ1jYSdF5mD9cav
2023-09-26 07:53:11: Received PINGREQ from 0Loy1diDJ1jYSdF5mD9cav
2023-09-26 07:53:11: Sending PINGRESP to 0Loy1diDJ1jYSdF5mD9cav
2023-09-26 07:53:52: New connection from 172.30.32.2:57820 on port 1883.
2023-09-26 07:53:52: Client
kellerza
commented
9 months ago @Niruservices - are you sure you have the corretc IP for your dongle?
OSError: [Errno 113] Connect call failed ('192.168.1.186', 8899)
Niruservices
commented
9 months ago Evening,
It is really odd – as it shows the correct MAC & shows connection speeds on the router – yet – not able to ping it either.
BR;
Nico
From: Johann Kellerman @.> Sent: Tuesday, September 26, 2023 7:21 PM To: kellerza/sunsynk @.> Cc: Niruservices @.>; Mention @.> Subject: Re: [kellerza/sunsynk] Cant start the Add-on on my Deye 12kW 3phases (Issue #180)
@Niruservices https://github.com/Niruservices - are you sure you have the corretc IP for your dongle?
OSError: [Errno 113] Connect call failed ('192.168.1.186', 8899)
— Reply to this email directly, view it on GitHub https://github.com/kellerza/sunsynk/issues/180#issuecomment-1735969335 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BCZGBF7IEKCTOYDRCNC65DTX4MFGFANCNFSM6AAAAAA4NTSTBQ . You are receiving this because you were mentioned. https://github.com/notifications/beacon/BCZGBF4T26I52256N25JTFLX4MFGFA5CNFSM6AAAAAA4NTSTBSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTHPDFDO.gif Message ID: @. @.> >
Niruservices
commented
9 months ago Morning,
BTW, if I use RS485 – which bus to select py or U?
BR;
Nico
From: Nico Steenkamp @.> Sent: Tuesday, September 26, 2023 7:33 PM To: 'kellerza/sunsynk' @.>; 'kellerza/sunsynk' @.> Cc: 'Mention' @.> Subject: RE: [kellerza/sunsynk] Cant start the Add-on on my Deye 12kW 3phases (Issue #180)
Evening,
It is really odd – as it shows the correct MAC & shows connection speeds on the router – yet – not able to ping it either.
BR;
Nico
From: Johann Kellerman @. @.> > Sent: Tuesday, September 26, 2023 7:21 PM To: kellerza/sunsynk @. @.> > Cc: Niruservices @. @.> >; Mention @. @.> > Subject: Re: [kellerza/sunsynk] Cant start the Add-on on my Deye 12kW 3phases (Issue #180)
@Niruservices https://github.com/Niruservices - are you sure you have the corretc IP for your dongle?
OSError: [Errno 113] Connect call failed ('192.168.1.186', 8899)
— Reply to this email directly, view it on GitHub https://github.com/kellerza/sunsynk/issues/180#issuecomment-1735969335 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BCZGBF7IEKCTOYDRCNC65DTX4MFGFANCNFSM6AAAAAA4NTSTBQ . You are receiving this because you were mentioned. https://github.com/notifications/beacon/BCZGBF4T26I52256N25JTFLX4MFGFA5CNFSM6AAAAAA4NTSTBSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTHPDFDO.gif Message ID: @. @.> >
kellerza
commented
9 months ago You can use either, whichever is the most reliable for you.
I have found that the recent pymodbus is fairly reliable for direct serial.
umodbus has always worked well (via some gateway like mbusd, but not direct serial)
kellerza
commented
9 months ago @lordvalium did you manage to get it running?
lordvalium
commented
8 months ago no unfortunately not @kellerza Have bought that addon https://www.amazon.de/dp/B08DXRKFZR but its not recognized in Homeassistant
Issue related to
Sunsynk / mbusd Home Assistant Add-On
Describe the issue/bug
My issue is that after a proper configuration my Addon stops (HALT).
Expected behavior Should provide information via Entities
Your environment
Adaptor details:
(set and found via Debug)
You configuration
Logs
Edit: logs before i click update