pimdoos / ha-sessy Goto Github PK

2024-04-16 08:43:24.997 WARNING (MainThread) [homeassistant.components.group.sensor] Unable to use state. Only numerical states are supported, entity sensor.sessy_p33f_phase_1_consuming_power with value unavailable excluded from calculation in sensor.huidig_verbruik_op_alle_3_fases_meetpunt_hfd_meter
2024-04-16 08:43:24.997 WARNING (MainThread) [homeassistant.components.group.sensor] Unable to use state. Only numerical states are supported, entity sensor.sessy_p33f_phase_2_consuming_power with value unavailable excluded from calculation in sensor.huidig_verbruik_op_alle_3_fases_meetpunt_hfd_meter
2024-04-16 08:43:24.998 WARNING (MainThread) [homeassistant.components.group.sensor] Unable to use state. Only numerical states are supported, entity sensor.sessy_p33f_phase_3_consuming_power with value unavailable excluded from calculation in sensor.huidig_verbruik_op_alle_3_fases_meetpunt_hfd_meter
2024-04-16 16:13:44.907 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.sessy_p33f_phase_2_current (<class 'custom_components.sessy.sensor.SessySensor'>) took 0.430 seconds. Please create a bug report at https://github.com/PimDoos/ha-sessy/issues

• Min/max power settings
• Time of day restrictions

When the WiFi adapter is not connected, wifi_sta.rssi in the NETWORK_STATUS api is set to 'null'.
This causes the RSSI sensor to log an error on every update cycle.

Todo: Disable RSSI sensor in entity discovery if wifi_sta.rssi is null.

Update progress is displayed as a unit interval (float: 0,00000000-1,000000000) while it should be a percentage (float: 0,0-100,0)

Possible values:

• P1_NOT_CONNECTED
• P1_DATAVALIDITY_ERR
• P1_VERSION_ERR
• P1_PARSE_ERR
• P1_OK

(Source: https://github.com/PimDoos/ha-sessy-rest/blob/main/api-docs-p1.yaml)

I am unable to add the state of charge to a Statistics graph Card in HA. HA tells me that the developer should configure the entity so they know that they need to track statistics for that entity. Could you do so or maybe give a hint on how to add the state of charge percentage to a graph?

Link HA gives: https://developers.home-assistant.io/docs/core/entity/sensor#long-term-statistics

In v0.5.2 krijg ik mijn batterij niet meer gekoppeld.
de P1 dongle doet het wel gewoon.

bij apparaat toevoegen heb ik zowel het sessy-XXXX.local adres geprobeerd als het ip adres. Beide resulteren in een onbekende fout.
Onderstaande foutmelding heb ik uit de log gekregen
Mijn Sessy is ongeveer een week geleden geïnstalleerd. De eerste paar dagen werkte deze integratie nog wel.
De laatste firmware is geïnstalleerd op de Sessy.

Op de pagina van de Sessy zelf (zowel het IP adres als de sessy-XXXX.local) kan ik gewoon inloggen en zie ik ook gewoon de data van de sessy.

Deze fout is ontstaan door een aangepaste integratie.

Logger: custom_components.sessy.config_flow
Source: custom_components/sessy/config_flow.py:34
Integration: Sessy (documentation, issues)
First occurred: 10:51:22 (9 occurrences)
Last logged: 11:47:37

Unexpected exception
Traceback (most recent call last):
File "/config/custom_components/sessy/config_flow.py", line 94, in async_step_user
info = await validate_input(self.hass, user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/sessy/config_flow.py", line 34, in validate_input
device = await get_sessy_device(
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/sessypy/devices.py", line 131, in get_sessy_device
raise SessyNotSupportedException
sessypy.util.SessyNotSupportedException

After restarting HA today I received following warning:

This error originated from a custom integration.

Logger: custom_components.sessy.number
Source: custom_components/sessy/number.py:102
integration: Sessy (documentation, issues)
First occurred: 1:43:13 PM (1 occurrences)
Last logged: 1:43:13 PM

Error setting firmware specific settings: 'NoneType' object has no attribute 'get'

As described at PimDoos/sessypy#29

As discussed in sessypy PimDoos/sessypy#16, there are net P1 and CT endpoints with more data

Switching the unit for a voltage sensor from mV to V does not devide it's value by 1000 while it should.

This causes the sensor to show as '233000 V' while the actual value is 233000 mV, and thus 233 V.

When a device was setup using config flow before 0.3.2, it will not have a unique id yet. Zeroconf will cause a duplicate if it cannot match a unique id.

The specification of the Sessy is 1700W discharge on the website, but it can do more at high battery voltages.
The real restriction is the maximum current that the BIC power supply inside the Sessy can handle (37.5A).
So when battery voltage is above 45V (which is always), it can do more than 1700W.
When the battery is full, it will have around 54V, meaning we can discharge at 2025W

There is no harm in allowing to set 2000W via the API in Home Assistant. The Sessy will try to reach whatever you set, but will not go over the limits of the components inside the Sessy.

My request is that the limit of 1700W discharge is increased to 2000W

Ik draai op 0.1.0 van jouw integratie

Ik heb firmware 1.1.2 in de dongle en in de battery zitten, maar Device info toont 1.1.1

NU ben in geupdated naar jouw 0.1.2 en heb ik (verplicht) HA opnieuw opgestart. Nu toont het info panel wel de juiste versie.

My mistake, it is called simply “API” in the pull down menu an it is selectable.

I’ve noticed that the energy strategy named “home automation API” is not selectable from the list in HA. Is that am expected behavior?

Updating system settings entities fails on 'loud' Sessy due to an error validating 'allowed_noise_level'.
Loud Sessy has allowed_noise_level set to 101 in system settings, which is outside the expected value range 1-5.

{
	"status":	"error",
	"error":	"Allowed noise level out of range"
}

Currently, we use friendly_status_string as a transformation function on System State and P1 State sensors.
This should be moved to strings.json and translation files.

Bij het omzetten van stroom treden verliezen op, deze zijn afhankelijk van laden / ontladen en het vermogen. Is het mogelijk een efficiënte waarde toe te voegen om zo het perfecte laad en ontlaad vermogen vast te stellen?

New in Home Assistant 2023.04
https://developers.home-assistant.io/blog/2023/03/27/entity_name_translations/

Is there (a way to add) a temperature sensor inside the Sessy to monitor in HA?

Whatever I try I never get a succesful connection

I also tried it with the IP number

When I just use the url in the browser I get connected

Any other things I can try?

Now that winter is coming in the northern hemisphere, there will be days that the solar panels will not produce enough to charge the Sessy. Given the high/low-tariff system in The Netherlands, it would be nice if the Sessy can charge at night (lower tariff), when the next day will be a day with low/no solar power production, and discharge during the day (high tariff).

Although you can choose the manual strategy in the Sessy, it says something like: With great power comes great responsibility. Rightfully so. I don't wish to implement my own strategy (and control the Sessy). But I'd like to have a one-time-button with which I can say: Charge now until full, from net power. Yes, this is fully manual but at least the "damage" will be limited to one day, compared to a faulty strategy which keeps running.

Is this possible? Or would this be something that should be implemented on the Sessy itself? Perhaps @MartijnCharged can elaborate on this as well.

When turning the Eco NOM Charging Enabled switch on or off, the state is not written to Sessy's settings.

In de beschrijving van de aanpassingen:
Er is een nieuwe grid_setpoint, waarmee je de Sessy een waarde anders dan 0 kan geven, bijvoorbeeld als je extra wil laden of ontladen.

hoe krijg ik deze in mij Homeassistant?

Uit https://portal.sessy.nl/users/notifications/FirmwareUpdateNote/19:

Informatie slimme meter – De Sessy P1 meter kan nu extra informatie over het elektriciteitsnet en je verbruik doorgeven aan jouw ‘Smart Home’ systeem. (IP/api/v2/p1/details)
X op de meter – De modus “nul op de meter” probeert het verbruik van jouw huishouden op 0 te houden. Middels een nieuw API-endpoint op de P1 meter (/api/v1/meter/grid_setpoint) is het mogelijk om het doel van de regeling te wijzigen. Heb je een elektrische auto die je niet met de Sessy wilt opladen? Dan kan een ‘Smart Home’ systeem het vermogen (X) van de auto optellen bij de regeling.

Hot-reloading the integration causes the cache trackers to duplicate, causing poor performance on the API.

Add energy sensors (kWh meters)

• Battery Charged
• Battery Discharged

Renewable Energy meters:

• Phase # Energy Consumed
• Phase # Energy Produced

Hello, it appears that the state of charge is not correctly displayed at home assistant.

this results is viseable in home assistant, the battery status is empty but still gives a state of charge of 4.0 %

here are some logs;
this is the state of charge gathered directly from the api;

{
"status": "ok",
"sessy": {
"state_of_charge": 0.070000000298023224,
"power": -2036,
"power_setpoint": -2200,
"system_state": "SYSTEM_STATE_RUNNING_SAFE",
"system_state_details": "",
"frequency": 50030
},
"renewable_energy_phase1": {
"voltage_rms": 228020,
"current_rms": 337,
"power": 76

this is what is displayed at home assistant;
Sessy-D9C9 State of Charge
1 minuut geleden
7,0%

sinds twee weken krijg ik Sessy niet meer gekoppeld aan Home assistant. Alle entities waren niet meer bereikbaar, uiteindelijk heb ik de installatie opnieuw gestart, de P1 en de sessie worden discovered als new device, maar als ik ze probeer te adden met UN en PW dan krijg ik de melding "unexpected error" Sessy en P1 uit en aanzetten helpt ook niet. Via portal.sessy werkt alles wel. Sessy helpdesk heeft geen idee. Heb jij nog een idee hoe ik dit kan fixen? groeten Bas

Hi @PimDoos

When i try to install the integration via the UI.

I get this error:

Config flow could not be loaded: {"message":"Invalid handler specified"}

Restarted Home Assistant multiple times

Logs:

This error originated from a custom integration.

Logger: homeassistant.loader
Source: custom_components/sessy/init.py:21
Integration: Sessy (documentation, issues)
First occurred: 21:13:34 (4 occurrences)
Last logged: 21:16:48

Unexpected exception importing platform custom_components.sessy.config_flow
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 833, in get_platform
cache[full_name] = self._import_platform(platform_name)
File "/usr/src/homeassistant/homeassistant/loader.py", line 850, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
File "/usr/local/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 992, in _find_and_load_unlocked
File "", line 241, in _call_with_frames_removed
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/config/custom_components/sessy/init.py", line 21, in
PLATFORMS: list[Platform] = [Platform.SENSOR, Platform.SELECT, Platform.NUMBER, Platform.TIME, Platform.UPDATE]
File "/usr/local/lib/python3.10/enum.py", line 437, in getattr
raise AttributeError(name) from None
AttributeError: TIME

Do you know what went wrong?

Thanks in advance

This leads to values like '8000 A' on phase current sensors

Sessy CT Meter uses the same API endpoint as the P1 meter. This might change in the future, or it might not.
Might have to update the detection logic for now.

In the current version the total power sensor is a factor 1000 off. Its displaying watts as kW.

CT dongle firmware 1.5.3