Open christiankropf opened 1 year ago
I can confirm the problem with core 2023.5.0
Solaredge SE6000H inverter with a connected meter, exporting models 101, 203 and 701
I have since downgraded to 2023.4.6 to keep monitoring going, but I can go back to 2023.5 to gather more information if needed.
Same issue here !
Same here. Worked properly with Kaco Blueplanet inverter until update to 2023.5. Since then data refresh from inverter obviously dysfunctional .
Hi all, same problem for me; SMA sunnyboy 6.0 + Sunny boy storage 5.0; sunspec data stop refresh; data refresh only once after a reboot; problem started with version 2023.05. If you want some help please tell me for sending other informations, log and so on.
Same here with Kaco bp 10.0 NX3 M2. No refreshing after initial update.
Hi everybody.
I can confirm the issue : no refresh since 2023.05 update. I have to do it manually.
Through : SE7K-RW0TEBEN4 from SolarEdge.
If it's possible doing something in the code locally, waiting an update, that's ok.
Thanks many times for the work and the answers. ;)
Hi everybody.
I can confirm the issue : no refresh since 2023.05 update. I have to do it manually.
Through : SE7K-RW0TEBEN4 from SolarEdge.
If it's possible doing something in the code locally, waiting an update, that's ok.
Thanks many times for the work and the answers. ;)
Ok replying to myself.
Done an automation doing that in the meanwhile.
If you're interested search more about the service :
homeassistant.reload_config_entry
Using "Config entry id".
The id of the integration is in the URL, when you click on a device of the integration Sunspec. _(after configentry=)
Here the log entry, may it could help.
Logger: homeassistant.components.sensor
Source: components/sensor/__init__.py:583
Integration: Sensor (documentation, issues)
First occurred: 19:26:05 (18 occurrences)
Last logged: 19:35:58
Error adding entities for domain sensor with platform sunspec
Error while setting up sunspec platform for sensor
Error adding entities for domain sensor with platform volkswagencarnet
Error while setting up volkswagencarnet platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 579, in state
numerical_value = int(value)
ValueError: invalid literal for int() with base 10: ''
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 455, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 731, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 846, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 585, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 649, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 591, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 583, in state
raise ValueError(
ValueError: Sensor sensor.fg2410ak3l_201_ac_meter_events has device class None, state class None unit and suggested precision None thus indicating it has a numeric value; however, it has the non-numeric value: (<class 'str'>)
Same problem here.
Seems like HA is more picky about data types now, the integration is now handling enum data types properly so this error should be fixed in 0.0.23.
Confirm fixed in 0.0.23. And now we also have proper history for enums... Yay!
I can confirm it is fixed in 0.0.23. Thank you for the quick fixing!
I would vote for reopen.
thx in advance: A part is working, another not:
Logger: homeassistant.components.sensor
Source: components/sensor/__init__.py:561
Integration: Sensor (documentation, issues)
First occurred: 12:13:40 (2 occurrences)
Last logged: 12:13:40
Error adding entities for domain sensor with platform sunspec
Error while setting up sunspec platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 455, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 731, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 846, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 585, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 649, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 591, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 561, in state
raise ValueError(
ValueError: Sensor sensor.pikoiq42_mppt_module_0_operating_state provides state value '0', which is not in the list of options provided
Interesting:
up to the „error“ sensor it is ok, all others afterwards are not updating;
@CJNE I tried to find in which file the dct events, but not really sure: https://github.com/sunspec/models/blob/cd7767e199ef5e7909f7d6aa17dd76b865a185b9/json/model_160.json#L160
So before it was on MPPT, I do not how the value would be mapped to the option.
Oh, it looks like I missed to change the value property to use the enum values, this might have caused issues still. Version 0.0.24 is out with a fix! If you still have problems, please acivate debug logging and see what options it says are allowed for the sensor:
Edit configuration.yaml and add debug logging for SunSpec logger: ... logs: custom_components.sunspec: debug ...
Let me know if you need more, the Fronius seems to be with no errors but the kostal piko.
Same here using a Kostal Plenticore.
Logger: homeassistant
Source: components/sensor/__init__.py:561
First occurred: 16:31:26 (316 occurrences)
Last logged: 19:27:25
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 204, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 349, in _async_refresh
self.async_update_listeners()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 146, in async_update_listeners
update_callback()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 406, in _handle_coordinator_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 585, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 649, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 591, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 561, in state
raise ValueError(
ValueError: Sensor sensor.mppt_module_0_operating_state provides state value '0', which is not in the list of options provided
Do you need more details? The values are not updating. Only once you reload the integration or boot HA.
Oh, it looks like I missed to change the value property to use the enum values, this might have caused issues still. Version 0.0.24 is out with a fix! If you still have problems, please acivate debug logging and see what options it says are allowed for the sensor:
Edit configuration.yaml and add debug logging for SunSpec logger: ... logs: custom_components.sunspec: debug ...
Hi, why i can't get result when last value Unavailable. Soo i need to restart HA and i can get result again. SunSpec version 0.0.24
Thanks,
Is there a fix for the plugin? In some other plugins, the problem was in the phyton version.
After Updating the entity "Solaredge inverter Watts" does not refresh properly. After reloading the integration it works for some minutes.