leeyuentuen / alfen_wallbox Goto Github PK

Installed the component via HACS (version 2.6.14 because I'm already on HASS 2023.9).

When configuring the component I get the following error:

2023-09-07 07:23:05.734 ERROR (MainThread) [custom_components.alfen_wallbox.config_flow] Unexpected error creating device
Traceback (most recent call last):
File "/config/custom_components/alfen_wallbox/config_flow.py", line 43, in _create_device
await device.init()
^^^^^^^^^^^^^
TypeError: AlfenDevice.init() missing 1 required positional argument: 'hass'

Any idea what could be wrong? In case you need more information, feel free to reach out to me 🙂

if having 32A license, allowed value to 32, otherwise set max value to 16A

It seems I can't set it other than 0.6 and 0.7 Euro by clicking the up- and down arrows. Not something on the Eurocent level like 0.61 Euro. Or am I missing something here?

Hi there and thanks for your effort .

Could it be that ones you done the integration in AH . you cant loging with the alfen tool ?

change comfort min level from 1400 to 1330

Hello there dear friends ;)

I have since a week a Alfen Eve single Pro line (NG910-60027) charger at home. I succesfully installed the Home Assistant integration (V2.3.2) through HACS, everything seems to work pretty well! There is only one problem, every +/- 8 hours my Alfen Charger does a automatic reboot. The logbook in the ACE Service Installer application show as cause "Watchdog reset". I am not very familiar with all the technical terms in the logbook, so I can’t figure out why this problem accurse every +/- 8 hours. The problem only shows up when the Home Assistant integration is enabled, so it must have something to do with this add-on. But I LOVE this add-on so disabling it, is not a (preferred) option.

Is this problem know already? It seems that more people (with different forks of this integration) have similar problems.
(example: egnerfl#3). I dont know if it is the exact same problem, the logs seem to differ a little. Under this line you will find a very small part of my logbook, where you can see the error.

Feel free to ask for more information if necessary.

And first of all Thank you!!

2023-08-01T14:12:52.906Z:RESET:application.c:364:==========================================
2023-08-01T14:12:52.917Z:INFO:application.c:372:build: May 23 2023 14:55:11
2023-08-01T14:12:52.925Z:INFO:application.c:373:version: 6.3.0-4185
2023-08-01T14:12:52.933Z:INFO:application.c:374:compiler: gcc 4.8.3
2023-08-01T14:12:52.941Z:INFO:application.c:237:fwu state inactive
2023-08-01T14:12:52.949Z:INFO:application.c:244:Bootloader version 1.2.0
2023-08-01T14:12:53.347Z:USER:taskCANopen.c:235:Persistent configuration retrieved, 274 items
2023-08-01T14:12:53.363Z:INFO:application.c:280:FLASH read protection 0xcc level 2 (permanent)
2023-08-01T14:12:53.371Z:USER:application.c:423:Using P1 port
2023-08-01T14:12:53.378Z:INFO:application.c:316:System boot #12, cause Watchdog reset
2023-08-01T14:12:53.386Z:INFO:board_ng9xx.c:1497:Registered timeout getHardware
2023-08-01T14:12:53.410Z:WARNING:bspI2c.c:670:I2C slave not responding #-3 MMA8451@0x000d, attempting bus recovery
2023-08-01T14:12:53.425Z:WARNING:bspI2c.c:689:Device MMA8451@0x000d not available
2023-08-01T14:12:53.445Z:WARNING:bspI2c.c:670:I2C slave not responding #-3 BMA456Q@0x0000, attempting bus recovery
2023-08-01T14:12:53.460Z:WARNING:bspI2c.c:689:Device BMA456Q@0x0000 not available
2023-08-01T14:12:56.875Z:ERROR:board_ng9xx.c:5206:Socket 1: Timeout while waiting for Lock motor
2023-08-01T14:12:58.085Z:INFO:board_ng9xx.c:5202:Socket 1: No Cover motor installed
2023-08-01T14:12:59.191Z:INFO:board_ng9xx.c:5577:Socket 1: emergency relays check OK
2023-08-01T14:12:59.699Z:INFO:board_ng9xx.c:1524:Unregistered timeout getHardware

You cant set the Load Balancing Max Current higher than 32A in the plugin. I've set mine to 40A in the MyEve app.

I think the max should be set to something like 80A since thats the max for small companies (in The Netherlands atleast). Larger companies can have more but I don't think thats needed.

I have tried to add my alfen Wallbox to Home Assistant. I get the error :
Unexpected error creating device.

i've just found this integration, and am trying to get it working together with the EV Smart Charging integration (https://github.com/jonasbkarlsson/ev_smart_charging/).

is it possible to add a switch that Start/Stops the charging?

Hi,

I have a 2 port Alfen Wallbox (Eve Double Pro-line), the sensor meter reading and Active Power Total only seem to be taken port 1 into account and not port 2. Most of the other sensors do have a 1 and 2 variant.

Hello, Are there any other values you can retrieve in the integration? Such as: Static-LoadBalancing, Active-LoadBalancing, MbsSlaveTCPIPMode. Thanks in advance for your reply.

When you set the Prices per kWh etc. they don't stick. When I look at debug logging I see errors when it's trying to update through the Alfen API's. Setting the 3 different tariffs results in the following error log:

2023-09-13 20:14:13.334 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] POST with login
2023-09-13 20:14:13.335 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Send Post Request
2023-09-13 20:14:14.541 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Login response <ClientResponse(https://192.168.1.51/api/login) [200 OK]>
<CIMultiDictProxy('Content-Type': 'alfen/json; charset=UTF-8', 'Connection': 'keep-alive', 'Content-Length': '0')>

2023-09-13 20:14:14.541 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Send Post Request
2023-09-13 20:14:14.608 ERROR (MainThread) [custom_components.alfen_wallbox.alfen] Unexpected error on UPDATE VALUE Connection closed
2023-09-13 20:14:15.760 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Login response <ClientResponse(https://192.168.1.51/api/login) [200 OK]>
<CIMultiDictProxy('Content-Type': 'alfen/json; charset=UTF-8', 'Connection': 'keep-alive', 'Content-Length': '0')>

2023-09-13 20:14:15.760 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Send Post Request
2023-09-13 20:14:15.832 ERROR (MainThread) [custom_components.alfen_wallbox.alfen] Unexpected error on UPDATE VALUE Connection closed
2023-09-13 20:14:16.752 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] POST with login
2023-09-13 20:14:16.752 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Send Post Request
2023-09-13 20:14:17.651 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] POST with login
2023-09-13 20:14:17.652 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Send Post Request
2023-09-13 20:14:18.797 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Login response <ClientResponse(https://192.168.1.51/api/login) [200 OK]>
<CIMultiDictProxy('Content-Type': 'alfen/json; charset=UTF-8', 'Connection': 'keep-alive', 'Content-Length': '0')>

2023-09-13 20:14:18.797 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Send Post Request
2023-09-13 20:14:18.868 ERROR (MainThread) [custom_components.alfen_wallbox.alfen] Unexpected error on UPDATE VALUE Connection closed

number.alfen_eve_single_pro_line_current_limit
Not possible to change te number to 0
Adjust via service Alfen Wallbox: set_current_limit still works. but number.alfen_eve_single_pro_line_current_limit is not able to show the number 0

I get an error when I push reboot button. Is this a bug?

Change in backoffice configuration key 'language'. Now the options 'cz_CZ, hu_HU,
is_IS' are also available.

in version 2.5.4 when i number.alfen_eve_single_pro_line_power_connector_max_current goes from 0A to 16A it goes after a few seconds back to 0A.

In version 2.5.2 it still works fine.

My values seems not to update regularly.
I have installed the addin just today and got some values, but they seems to stay fixe for longer time.

I also get an error:
"Updating alfen_wallbox select took longer than the scheduled update interval 0:00:30"

If I try to change a setting through Home Assistant, I get also an error (and the values do not change in the Alfen):
"Update for select.alfen_solar_charging_mode fails"
"Update for sensor.alfen_status_code fails"

I have an Alfen Single S-line

Display error on prop_id 3190

Would be nice to integrate a service or input_select for the different charging modes;

• Disabled
• Green
• Comfort

Is it possbile to create a service for this feature?
I tried to add a service but it's not working for me, I'll add it to this repo as soon as I have the time.

How should I handle the issue when the IP address of my Wallbox changed due to a new internet modem/router?

see discussion #32

Hi,
By default the max amp is set to 16. Is there a way to have the slider go up to 32? Sorry, new to this.

Thanks!

Hi, I see this is a fork, is this version more up to date with new sensors/services? Or will it be merged soon?

Thnx for info, just wanted to know what version I need to install when they are coming to install our Alfen in next weeks

Adding two Alfen devices in Home Assistant is generating errors, because not all identities have unique ids. Resulting in ignored entities for subsequent devices. Not all entity categories are affected, but according my log files the following categories don't have unique ids:

• number
• switch
• select

2023-07-24 15:27:13.996 ERROR (MainThread) [homeassistant.components.select] Platform alfen_wallbox does not generate unique IDs. ID None_lb_solar_charging_boost already exists - ignoring select.charger_wand_solar_charging_boost
2023-07-24 15:27:14.000 ERROR (MainThread) [homeassistant.components.select] Platform alfen_wallbox does not generate unique IDs. ID None_alb_phase_connection already exists - ignoring select.charger_wand_active_load_balancing_phase_connection
2023-07-24 15:27:14.002 ERROR (MainThread) [homeassistant.components.select] Platform alfen_wallbox does not generate unique IDs. ID None_auth_mode already exists - ignoring select.charger_wand_authorization_mode
2023-07-24 15:27:14.006 ERROR (MainThread) [homeassistant.components.select] Platform alfen_wallbox does not generate unique IDs. ID None_load_balancing_mode already exists - ignoring select.charger_wand_load_balancing_mode
2023-07-24 15:27:14.009 ERROR (MainThread) [homeassistant.components.select] Platform alfen_wallbox does not generate unique IDs. ID None_lb_active_balancing_received_measurements already exists - ignoring select.charger_wand_load_balancing_received_measurements
2023-07-24 15:27:14.012 ERROR (MainThread) [homeassistant.components.select] Platform alfen_wallbox does not generate unique IDs. ID None_display_language already exists - ignoring select.charger_wand_display_language
2023-07-24 15:27:14.015 ERROR (MainThread) [homeassistant.components.select] Platform alfen_wallbox does not generate unique IDs. ID None_bo_network_1_connection_priority already exists - ignoring select.charger_wand_backoffice_network_1_connection_priority_ethernet
2023-07-24 15:27:14.018 ERROR (MainThread) [homeassistant.components.select] Platform alfen_wallbox does not generate unique IDs. ID None_bo_network_2_connection_priority already exists - ignoring select.charger_wand_backoffice_network_2_connection_priority_gprs
2023-07-24 15:27:14.022 ERROR (MainThread) [homeassistant.components.select] Platform alfen_wallbox does not generate unique IDs. ID None_socket_1_operation_mode already exists - ignoring select.charger_wand_socket_1_operation_mode
2023-07-24 15:27:14.025 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform alfen_wallbox does not generate unique IDs. ID None_system_date_light_savings already exists - ignoring binary_sensor.charger_wand_system_daylight_savings
2023-07-24 15:27:14.029 ERROR (MainThread) [homeassistant.components.switch] Platform alfen_wallbox does not generate unique IDs. ID None_enable_phase_switching already exists - ignoring switch.charger_wand_enable_phase_switching
2023-07-24 15:27:14.032 ERROR (MainThread) [homeassistant.components.switch] Platform alfen_wallbox does not generate unique IDs. ID None_dp_light_auto_dim already exists - ignoring switch.charger_wand_display_light_auto_dim
2023-07-24 15:27:14.035 ERROR (MainThread) [homeassistant.components.number] Platform alfen_wallbox does not generate unique IDs. ID alb_safe_current already exists - ignoring number.charger_wand_alb_safe_current
2023-07-24 15:27:14.038 ERROR (MainThread) [homeassistant.components.number] Platform alfen_wallbox does not generate unique IDs. ID current_limit already exists - ignoring number.charger_wand_current_limit
2023-07-24 15:27:14.042 ERROR (MainThread) [homeassistant.components.number] Platform alfen_wallbox does not generate unique IDs. ID max_station_current already exists - ignoring number.charger_wand_max_station_current
2023-07-24 15:27:14.044 ERROR (MainThread) [homeassistant.components.number] Platform alfen_wallbox does not generate unique IDs. ID max_smart_meter_current already exists - ignoring number.charger_wand_max_meter_current
2023-07-24 15:27:14.049 ERROR (MainThread) [homeassistant.components.number] Platform alfen_wallbox does not generate unique IDs. ID lb_solar_charging_green_share already exists - ignoring number.charger_wand_solar_green_share
2023-07-24 15:27:14.053 ERROR (MainThread) [homeassistant.components.number] Platform alfen_wallbox does not generate unique IDs. ID lb_solar_charging_comfort_level already exists - ignoring number.charger_wand_solar_comfort_level
2023-07-24 15:27:14.058 ERROR (MainThread) [homeassistant.components.number] Platform alfen_wallbox does not generate unique IDs. ID dp_light_intensity already exists - ignoring number.charger_wand_display_light_intensity
2023-07-24 15:27:14.063 ERROR (MainThread) [homeassistant.components.number] Platform alfen_wallbox does not generate unique IDs. ID lb_max_imbalance_current already exists - ignoring number.charger_wand_max_imbalance_current_between_phases```

Hi,

I am using the service wallbox.set_current_limit in some automations and I see after the next update of all entities a change in sensor.wallbox_active_power_total, but no change in number.wallbox_current_limit.

For example after setting set_current_limit to 8 I would expect, that wallbox_current_limit changes to 8A, at latest after the entitiy is fetched next time from the device. But nothing happens. Currently I still see wallbox_current_limit displaying 2A, even though I called the service (with value 8) 4 hours ago.

Am I missing something or is this a bug?

Regards,
Waldemar

Hi,

just a small UI improvement suggestion, resulting from upgrade to 32A:

The setting number.wallbox_max_station_current limits the max. available current the station can deliver. In my case this is set to 16A and is a limit given by the power grid.

The two sliders number.wallbox_current_limit and number.wallbox_alb_safe_current should adjust their upper limit according to number. wallbox_max_station_current. Currentl<, these sliders show both always 32A als max. value and allow accidently a setting of 32A, even in wallbox_max_station_current is 16A.

Is just a detail, but during the last few days I changed the value accidently multiple times to 32A and I simply don't know, how this is handled by the wallbox.

Regards,
Waldemar

I'm trying to add this integration to my HA setup, but it always gives me an error when creating the device. This is the error the log gives me:

  File "/config/custom_components/alfen_wallbox/config_flow.py", line 55, in _create_device
    await device.init()
  File "/config/custom_components/alfen_wallbox/alfen.py", line 43, in init
    await self.async_update()
  File "/config/custom_components/alfen_wallbox/alfen.py", line 65, in async_update
    await self._do_update()
  File "/config/custom_components/alfen_wallbox/alfen.py", line 121, in _do_update
    self._status = AlfenStatus(response_json_combined, self._status)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/alfen_wallbox/alfen.py", line 348, in __init__
    for prop in response["properties"]:
                ~~~~~~~~^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

I am using the ACE username + supplied password (QR code information supplied with the charger). The same information I use when connecting through ACE Service Installer.

Other relevant information:

Home Assistant 2023.7.1
Supervisor 2023.07.1
Operating System 10.3 (Home Assistant OS)
Frontend 20230705.1 - latest

This is a great plugin to use, but the learning curve is very steep.
Some documentation could ease the integration pain. I am willing to help with this, but I will need help myself.

And it begins with the simple stuff like:

• You cannot add the device in Home Assistant if the "ACE Service Installer" is connected to the device at the same time. You will get an unknown error when you try this, so first close the ACE Service Installer.
• Also it asks for a usename and password. This is the username "admin" alongside the "Owner" password.
  Simple information, but together with the first point, makes a hell in trying to find out why it will not connect.

Other stuff I don't know yet are:

• Does this plugin only uses the API or also modbus? Do I need to configure modbus and active loadbalancing or not?
• Is there a "push preferred settings" button so the integration configures the modbus and balancing settings to a default or preferred state?
• Are there examples of automations on how to best manage the amps so it stays under a certain Wattage or only uses a certain wattage compared to energy send back to the grid, energy used from the grid, production of solar, no charging if home battery not > 80% for example, etc...

Aside from very long form posts and a few lists in the github wiki, there is no sign of a much needed manual.

add authorization parts with whitelist, localist

also possibility to add plug&charge ID if we use Plug&charge option

In the screen shots on Github, I see "Safe current, Current limit, Max meter current, etc." are visible and adjustable.
None of these current fields are visible in my integration.
I added the integration manually and took the latest version (2.2.0).
Do you have any idea why I can't see these fields.

Thanks in advance for your response.

More or less same issue as #31.

The service call to set_current_limit, with the new entity number.wallbox_power_connector_max_current_socket_1 does not work.

The error is:

Logger: custom_components.alfen_wallbox.alfen
Source: custom_components/alfen_wallbox/alfen.py:287
Integration: Alfen Wallbox (documentation)
First occurred: 22:04:07 (1 occurrences)
Last logged: 22:04:07

Unexpected error on UPDATE VALUE Connection closed

Same happens, if I try to use the according slider:

After a HA reboot I see the value I was sending with the service call. This means, the value is set, but not updated in the UI?

I updated to the newest version 2.7.6 today.

Regards,
Waldemar

After updating to HA 2024.1 the following warning appears in the log:

2024-01-03 13:52:46.924 WARNING (MainThread) [homeassistant.components.sensor] DEVICE_CLASS_ENERGY was used from alfen_wallbox, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.ENERGY instead, please report it to the author of the 'alfen_wallbox' custom integration
2024-01-03 13:52:46.934 WARNING (MainThread) [homeassistant.components.sensor] DEVICE_CLASS_POWER was used from alfen_wallbox, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.POWER instead, please report it to the author of the 'alfen_wallbox' custom integration
2024-01-03 13:52:46.943 WARNING (MainThread) [homeassistant.components.sensor] DEVICE_CLASS_ENERGY was used from alfen_wallbox, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.ENERGY instead, please report it to the author of the 'alfen_wallbox' custom integration
2024-01-03 13:52:46.953 WARNING (MainThread) [homeassistant.components.sensor] DEVICE_CLASS_POWER was used from alfen_wallbox, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.POWER instead, please report it to the author of the 'alfen_wallbox' custom integration

When running alfen_wallbox with Home Assistant 2023.9 RC the integration fails to load:

2023-09-06 15:05:48.331 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration alfen_wallbox: Unable to import component: Exception importing custom_components.alfen_wallbox
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 818, in get_component
    ComponentProtocol, importlib.import_module(self.pkg_path)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1147, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/config/custom_components/alfen_wallbox/__init__.py", line 21, in <module>
    from .alfen import AlfenDevice
  File "/config/custom_components/alfen_wallbox/alfen.py", line 48, in <module>
    hass = core.HomeAssistant()
           ^^^^^^^^^^^^^^^^^^^^
TypeError: HomeAssistant.__new__() missing 1 required positional argument: 'config_dir'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 215, in _async_setup_component
    component = integration.get_component()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 826, in get_component
    raise ImportError(f"Exception importing {self.pkg_path}") from err
ImportError: Exception importing custom_components.alfen_wallbox

Most likely this will be the case for the final version. See https://developers.home-assistant.io/blog/2023/08/29/homeassistant-changed-signature/

We are having 2 RFID cards for authorization. For each one a different backend reimbursement process is triggered.
Does anyone know if there is already a sensor showing me which RFID card has authorized? Didn’t find any yet.

see discussion: #73

Since update to v2.6.8 (which keeps the https API connection open), I get Https timeouts. The sensor data isn’t updated anymore, nor am I able to change max current value for example.

Only way to get it running again, is to reload the HA integration.

Log:

This error originated from a custom integration.

Logger: homeassistant.helpers.entity
Source: custom_components/alfen_wallbox/alfen.py:147 
Integration: Alfen Wallbox (documentation) 
First occurred: 16:40:49 (2 occurrences) 
Last logged: 17:51:35

Update for sensor.laadpaal_2 fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 403, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 1053, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.11/site-packages/urllib3/connection.py", line 419, in connect
    self.sock = ssl_wrap_socket(
                ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/util/ssl_.py", line 453, in ssl_wrap_socket
    ssl_sock = _ssl_wrap_socket_impl(sock, context, tls_in_tls)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/util/ssl_.py", line 495, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/ssl.py", line 517, in wrap_socket
    return self.sslsocket_class._create(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/ssl.py", line 1075, in _create
    self.do_handshake()
  File "/usr/local/lib/python3.11/ssl.py", line 1346, in do_handshake
    self._sslobj.do_handshake()
TimeoutError: _ssl.c:985: The handshake operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
           ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 798, in urlopen
    retries = retries.increment(
              ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/util/retry.py", line 550, in increment
    raise six.reraise(type(error), error, _stacktrace)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/packages/six.py", line 770, in reraise
    raise value
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 714, in urlopen
    httplib_response = self._make_request(
                       ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 406, in _make_request
    self._raise_timeout(err=e, url=url, timeout_value=conn.timeout)
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 357, in _raise_timeout
    raise ReadTimeoutError(
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='192.168.xxx.xxx', port=443): Read timed out. (read timeout=10)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 699, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 938, in async_device_update
    await self.async_update()
  File "/config/custom_components/alfen_wallbox/sensor.py", line 950, in async_update
    await self._device.async_update()
  File "/config/custom_components/alfen_wallbox/alfen.py", line 129, in async_update
    await hass.async_add_executor_job(self._get_all_properties_value)
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/alfen_wallbox/alfen.py", line 196, in _get_all_properties_value
    response = self._get(url=self.__get_url(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/alfen_wallbox/alfen.py", line 147, in _get
    response = self._session.get(url, timeout=10)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/requests/sessions.py", line 602, in get
    return self.request("GET", url, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/requests/adapters.py", line 532, in send
    raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='192.168.xxx.xxx', port=443): Read timed out. (read timeout=10)

Hi, I'm missing a value that I followed earlier, but is not present.
It's the Max current that the EMS (flexio from lifepowr) is regulating.

"mainActiveMaxCurrent" alfen api ID: 212C_0

can you add it pls

grts

Could it be there is a new issue that was not there before. I have been using this Alfen integration for quite some time now and I love it. However, recently both of our EVs set off the alarm in the morning while they had been charging overnight. Checking what caused it, it seems both of their batteries had been completely drained! This has never happened to me before when using the exact same integration. I have Comfort Solar charging turned on as usual and I use Boost Solar Charging to have it charge overnight. Both cars will be charged fully somewhere in the middle of the night when I am asleep (as usual).
What I now see on the Alfen timeline is that about every 2 minutes it starts charging again although the main battery is at 100%...

This must clearly have killed the 12V battery in both my EVs. Again, this only started recently and I am thinking what could have happened? I did upgrade to the latest version that has some new stuff around Disconnects... could that be the issue here??
Again, it was working fine before in the exact same way. The Alfen has been on the latest firmware all along so no changes there!
So I am not saying this is the root cause, just wondering if such behavior (timeline) is normal and could be causing a dying battery?
In the meantime, I could try with a workaround automation that if the battery reaches 100% it will put the Charging Current to 0A or something similar to basically force stop charging. Any thoughts?

I installed this plugin by adding the repository as "custom repo" through HACS. By default, HACS will not show unstable releases. However, 2.6.2 is not marked as "prerelease", even though the release note says it's unstable. This means that right now, by default, version 2.6.2 will get installed, which does indeed not work. Since you don't get to see the release notes in HACS, it's not obvious what's going on and it took me a couple of hours before I realized what was going on. Not a big deal, but I figured I'd report it here since other people run into this.

Add entities

• Load balancing dsmr_smr interface
• load balancing data source
• installation max allowed phase
• installation direct external suspend signal
• charging profile random delay

rename entities:

- sensor.<wallbox>_lb_max_allowed_of_phases_socket_1 -> sensor.<wallbox>_connector_1_max_allowed_of_phases
- number.<wallbox>_max_meter_current -> number.<wallbox>_load_balancing_max_meter_current
- number.<wallbox>_current_limit -> number.<wallbox>_power_connector_max_current
- number.<wallbox>_max_meter_current -> number.<wallbox>_load_balancing_max_meter_current
- number.<wallbox>_max_imbalance_current_between_phases -> number.<wallbox>_installation_max_imbalance_current_between_phases
- switch.<wallbox>_enable_phase_switching -> switch.<wallbox>_load_balancing_enable_phase_switching