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
- Provide as many details as possible. Paste logs, configuration samples and code into the backticks.
3
+
DO NOT DELETE ANY TEXT from this template! Otherwise, your issue may be closed without comment.
4
+
-->
5
+
## The problem
6
+
<!--
7
+
Describe the issue you are experiencing here to communicate to the
8
+
maintainers. Tell us what you were trying to do and what happened.
9
+
-->
10
+
11
+
12
+
## Environment
13
+
<!--
14
+
Provide details about the versions you are using, which helps us to reproduce
15
+
and find the issue quicker. Version information is of homeassistant found in the
16
+
Home Assistant frontend: Settings -> About. The installed version of the integration can be found via HACS -> Victron GX modbus TCP
17
+
-->
18
+
19
+
- Home Assistant Core release with the issue:
20
+
- Last working Home Assistant Core release (if known):
21
+
- Integration version causing this issue:
22
+
23
+
## Problem-relevant `configuration dialog`
24
+
<!--
25
+
An example configuration that caused the problem for you. Fill this out even
26
+
if it seems unimportant to you. Please be sure to remove personal information
27
+
like passwords, private URLs and other credentials. You can provide it as text or as an screenshot.
28
+
-->
29
+
30
+
```yaml
31
+
32
+
```
33
+
34
+
## Traceback/Error logs
35
+
<!--
36
+
Enable debug logging and perform steps to trigger the bug to occur. Download the debug logging and provide it and any other relevant HA core erors logs as an attachment to this issue
37
+
-->
38
+
39
+
```txt
40
+
41
+
```
42
+
43
+
## In case of unit ID issue, missing devices or non-updating devices
44
+
<!--
45
+
Go to Settings -> Services -> Modbus TCP on your GX device and provide an screenshot of the devices listed under "Available services"
46
+
-->
47
+
48
+
## Additional information
49
+
50
+
<!--
51
+
Any other relevant information for the bug you are experiencing
0 commit comments