You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: www/docs/guide/fault-finding.md
+38-16
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ The addon follows the following startup process:
6
6
7
7
1. Load config, sensor definitions and schedules
8
8
9
-
The logs will show if you use any unknown or deprecated sensors, if you have anything wrong in your custom sensors, and the intended schdule for reading sensors.
9
+
The logs will show if you use any unknown or deprecated sensors, if you have anything wrong in your custom sensors, and the intended schedule for reading sensors.
10
10
11
11
2. Connect to the Inverter
12
12
@@ -30,44 +30,66 @@ The addon follows the following startup process:
30
30
31
31
If this step fails, you will not see any entities in Home Assistant and you need to check your MQTT server settings.
32
32
33
-
Once the startup is complete, the addon will continue to read & publish sensor data. During this process you will occasianally see read failures. As long as this does not happen on every read, you can probably continue using the addon, but can consider reducing sesnors, relaxing the read schedules, etc.
33
+
Once the startup is complete, the addon will continue to read & publish sensor data. During this process you will occasianally see read failures. As long as this does not happen on every read, you can probably continue using the addon, but can consider reducing sensors, relaxing the read schedules, etc.
34
34
35
35
If you fail to get a reply from the inverter, typically if step #2 fails, please check the following:
36
36
37
-
## (a) Only a single connection to the serial port
37
+
## (A) Cabling & connection
38
+
39
+
While fault finding use as short as possible cable, outside any sprague/trunking. Once
40
+
everything is working, you can switch to a more permanent, much longer cable.
41
+
42
+
If you cannot establish a connection, check the RS485 adaptor and cabling. Are you
43
+
plugged into the correct port, is your connector crimped correctly?
44
+
45
+
::: tip
46
+
47
+
The newer inverters have a combined RS485 and CAN-BUS port. If your battery is already using the port for its CAN-BUS communications, you need to split the cable to connect your RS485 connector. The following articles explains the wiring of the port:
Other factors that might impact connection, or reliability:
55
+
56
+
- Use a RJ45 converter with a GROUND pin. Ensure the ground is connected.
57
+
- Re-crimp your RJ45 connector.
58
+
- Use a good quality solid CAT5e/CAT6 cable.
59
+
- Ensure the data line is using a twisted pair.
60
+
- Ensure your RS485 cable does not run parallel to other electrical cables (AC or DC), to reduce interference. e.g. in trunking.
61
+
- If interference is a problem, are you using a twisted pair in the cable?
62
+
- If interference is a problem, it could also help to use a shielded cable. Ground the shield at ONE end only (i.e. on the USB adaptor side and then just use normal plastic RJ45 connector on the inverter side.)
63
+
- If you still fail to make a connection, test the line voltage resistor (see Reducing timeouts below)
64
+
65
+
## (B) Configuration
66
+
67
+
### Only a single connection to the serial port
38
68
39
69
Ensure you only have a single addon connected to the serial port. The following can all potentially access the USB port: mbusd, Node RED, the normal and dev addon version.
40
70
41
71
If you need to have multiple connections to the serial port: ONLY connect mbusd to the serial port. Connect all addons to mbusd (e.g. tcp://192.168.1.x:503).
42
72
43
-
## (b) Check the Modbus Server ID
73
+
### Check the Modbus Server ID
44
74
45
75
Ensure the Modbus Server ID (`MODBUS_ID` config setting) matches the configured **Modbus SN** value of the inverter. This value must not be zero.
46
76
47
77
View/update the Modbus server ID on your inverter under "Advanced Settings" / "Multi-Inverter".
48
78
49
79
Please note that this can be reset to zero after a software upgrade on your inverter, and this will stop the addon from reading data from your inverter. Resetting it to the previous value (the value the value in `MODBUS_ID` if you had this working previously), and then restarting the inverter should fix the [issue](https://powerforum.co.za/topic/15779-home-assistant-no-longer-getting-data-after-sunsynk-firmware-update-solved/).
If you get many timeouts, or if the addon does not read all your sensors on startup (i.e. you see **Retrying individual sensors** in the log), you can try the following:
56
86
57
87
- Set `READ_SENSORS_BATCH_SIZE` to a smaller value, i.e. 8.
58
88
- The most reliable way to connect is to use mbusd to the serial port & connect the addon to mbusd at `tcp://<ip>:502`. The mbusd instance/addon can be on the same physical device or a remote device.
59
89
60
-
The hardware and cabling also has a big impact:
61
-
62
-
- Use a RJ45 converter with a GROUND pin. Ensure the ground is connected.
63
-
- Ensure the data line is on a twisted pair.
64
-
- Re-crimp your RJ45 connector.
65
-
- Use a good quality solid CAT5e/CAT6 cable.
66
-
- Ensure your RS485 cable does not run parallel to other electrical cables (AC or DC), to reduce interference. e.g. in trunking.
67
-
- It could also help to use a shielded cable. Ground the shield at ONE end only (i.e. on the USB adaptor side and then just use normal plastic RJ45 connector on the inverter side.)
68
-
- While fault finding use as short as possible cable, completely outside any sprague/trunking etc.
90
+
Check the cabling and connection again. Use a 1m cable and stand next to the inverter while testing.
69
91
70
-
## (d) Check line voltage / termination resistor
92
+
### Check line voltage / termination resistor
71
93
72
94
If your RS485 adapter has a termination resistor (typically 120 ohms), try removing it.
0 commit comments