-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to set up integration for Deye SUN-12K-SG04LP3-EU #312
Comments
Hi, @rene-neimann, strange I have the same device and had no issue but try v24.12.08_11 and let me know. |
Thanks a lot, this fix solved my problem and I'm now able to integrate my inverter. However, this integration seems to be suffering from a similar issue as the other Solarman integration -- some values showing incorrect and unrealistic values: Has this issue been reported already or should I create a new issue thread? |
Can you show me screenshot of Device attributes like can be seen here? #281 (comment) |
|
Could you also give me a reading using Developer tools >> ACTIONS >> Solarman: Read Holding Registers (Modbus Function Code 3) w/ register: 0, quantity: 22. |
Returns:
`
` |
Fuuu, I wonder what is the deal w/ your environment... anyway: fix: The truth value of an array is ambiguous Will you be able to replace content of |
And correction to my request: register 0, quantity 23. |
I think the deal is that Docker/container HA Core installations are messed up after Core 2024.12 upgrade: I appreciate your patience with this! So far my Docker/container installation has worked pretty much flawlessly but it seems they've created a mess now. I've created a completely fresh new container today for testing purposes and it has the same issues with Solarman integration as my few-years-old container.
Replaced. New error when running register 0, quantity 23:
|
I'm gonna need to see that error w/ debug log enabled so I can locate the origin of it. |
Hmm, debug log enabled (and HA restarted just in case) but oddly, the level of details seems exactly the same:
|
Not sure if it helps in any way but I spotted a pattern. The incorrect unrealistic values occur with sensors that can have both, positive and negative values. For example, with my battery power sensor. In the example below, I was:
|
@rene-neimann you need to upload a file which is produced during debug disable. HA log won't show debug messages. 😉 And your observation seems to be correct, however I have the same device so I'm 100% sure that the problem is not w/ the integration... I have to say that I'm really clueless of what could be the culprit but it seems even more strange for it to be HA Core's fault... Can't you just try to run some older version maybe? |
Here's the debug log:
Yes, I'm considering it. It also seems like the clean Docker Container installation I created behaves better and less Solarman sensors are messed up. So it could be my older container has accumulated some clutter which is causing issues. |
Description
When trying to set up the integration for my Deye SUN-12K-SG04LP3-EU, the integration fails to load and returns 2 different types of errors:
I tried different profile YAMLs, same result (Auto, deye_hybrid, deye_p3).
The exact same configuration (IP, port, serial, slave id) works with https://github.com/StephanJoubert/home_assistant_solarman integration.
Reproduction Steps
Log
This error originated from a custom integration.
Logger: custom_components.solarman.coordinator
Source: helpers/update_coordinator.py:318
integration: Solarman (documentation, issues)
First occurred: 23:35:33 (17 occurrences)
Last logged: 23:42:08
Unexpected error fetching Deye Hybrid data
Traceback (most recent call last):
File "/config/custom_components/solarman/api.py", line 244, in get
responses[(code, start)] = await self.try_read_write(code, start, quantity, f"Querying {code:02X} ~ {start:04} - {end:04} | 0x{start:04X} - 0x{end:04X} # {quantity:03}", True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solarman/api.py", line 203, in try_read_write
while attempts_left > 0 and not response:
^^^^^^^^
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/solarman/api.py", line 140, in load
self.device_info = await self.profile.resolve(self.get)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solarman/provider.py", line 120, in resolve
f = lookup_profile(await request(-1, [set_request(*AUTODETECTION_REQUEST_DEYE)]), self.attributes) if self.auto and request else self.filename
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solarman/api.py", line 258, in get
raise Exception(f"[{self.config.serial}] {format_exception(e)}") from e
Exception: [OBFUSCATED_SERIAL] ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 318, in __wrap_async_setup
await self._async_setup()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 351, in _async_setup
return await self.setup_method()
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solarman/api.py", line 143, in load
raise Exception(f"[{self.config.serial}] Device setup failed. [{format_exception(e)}]") from e
Exception: [OBFUSCATED_SERIAL] Device setup failed. [Exception: [OBFUSCATED_SERIAL] ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()]
#########################################
Logger: homeassistant.config_entries
Source: config_entries.py:1663
First occurred: 23:35:33 (2 occurrences)
Last logged: 23:35:33
Config entry 'Deye Hybrid' from integration solarman has an invalid unique_id 'OBFUSCATED_SERIAL' of type int when a string is expected, please create a bug report at https://github.com/davidrapan/ha-solarman/issues
Version
24.12.08_10
Home Assistant Version
2024.12.1
The text was updated successfully, but these errors were encountered: