gluap/pyess

Python library for communication with LG ESS power converters

pyess's Issues

Support new Battery mode "Weather forecast"

Due to the additional battery setting "weather forecast" calling self.set_batt_settings({"alg_setting": "on"}) doesn't work anymore.

No module named 'aiomqtt.error'

Hi,
after an upgrade my Rhaspberry Pi 4 to the latest Debian Bookworm version, I had to reinstall pyess. Installation via virtual environment runs without problems. But the test fails:

pi@raspberry2:~/pyess/bin $ ./essmqtt --mqtt_server 192.168.2.115 --ess_host=192.168.176.3 --ess_password mypassword Traceback (most recent call last): File "/home/pi/pyess/bin/./essmqtt", line 5, in <module> from pyess.essmqtt import main File "/home/pi/pyess/lib/python3.11/site-packages/pyess/essmqtt.py", line 9, in <module> import aiomqtt.error ModuleNotFoundError: No module named 'aiomqtt.error'

I tried to reinstall aiomqtt via pip install aiomqtt but the error doesn't vanish. Any idea? Thank you!

How to install

Good evening!
This is not really an issue as much as it's more of a question, but I figured this was the best place to get the support I needed.
I have an LG ESS at home and would like to connect it to Home Assistant.
This integration sounds like it's exactly what I need.
How would I go about installing this integration in my Home Assistant instance? Can you give me some steps or guidance to where I could get started?
Thanks in advance

essmqtt stops updating values after 38 hours of runtime

I'm still running essmqtt at a 2 seconds update cycle for both "common" and "home". 3rd day in a row essmqtt stops updating the values after 38 hours of runtime (1 day, 14 hours). The MQTT server keeps on running as far as I can tell and restarting the server doesn't fix the problem. The service needs to be restarted (systemctl restart essmqtt.service). Immediatley after restarting the values are being updated in the server.
systemctl status essmqtt.service doesn't deliver any hint regarding the issue.:

 essmqtt.service - ESS MQTT Communication
   Loaded: loaded (/etc/systemd/system/essmqtt.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2020-05-22 23:04:44 CEST; 1 day 17h ago
 Main PID: 50198 (essmqtt)
    Tasks: 1 (limit: 2290)
   CGroup: /system.slice/essmqtt.service
           └─50198 /home/user/essmqtt/bin/python3 /home/user/essmqtt/bin/essmqtt --mqtt_server 192.168.0.....

May 22 23:04:44 iobroker-vm systemd[1]: Started ESS MQTT Communication.
May 22 23:04:50 iobroker-vm essmqtt[50198]: INFO:pyess.aio_ess:fetching auth key
May 22 23:04:51 iobroker-vm essmqtt[50198]: INFO:pyess.essmqtt:starting send loop

How to connect on different subnet

Hello,
I installed pyess and I have an MQTT server running somewhere (without homeassistant, I just want to use the commandline). pyess and MQTT are running on 192.168.2.xx subnet, ESS is hooked to 192.168.176.3. How do I tell pyess to communicate with ESS on the 176.3 address?

The PW of ESS is known to me through other channels.

Thanks.

Improve documentation on statuses

@fu-zhou brought this up in #3: currently there is no knowledge what the statues mean:
E.g. when pcs_status=3, what does the 3 stand for? That also applies to e.g. mqtt.0.ess.common.BATT.status and the like. The values come out of the API but we don't know what they mean. Find out and add it to the documentation. A way to approach the issue would be to compare app readings when the status changes or plotting the status value together with the power flows. Likely status changes can be seen when powerflow directions change (e.g. Charging battery vs no current to battery vs battery discharging.)

switch-tasks not working

It seems that the switch-tasks are not working. I'm trying to switch on "Fast charging" using

mosquitto_pub -h localhost -p 1883 -t /ess/control/fastcharge -m True

I also tried

mosquitto_pub -h localhost -p 1883 -t /ess/control/active -m False  
mosquitto_pub -h localhost -p 1883 -t /ess/control/fastcharge -m True  
mosquitto_pub -h localhost -p 1883 -t /ess/control/active -m True

Unfortunately, neither I see any reaction at the PCS/BATT nor the reported status changes.

Has anyone successfully tested the manipulation of settings?

ESSmqtt as daemon

Hi, I have a problem where my ESS keeps dropping off my WiFi, so I tried to follow your instructions to set up essmqtt as a system daemon. essmqtt works when I run it from Terminal.

The essmqtt.conf file is located in /etc/
The essmqtt file is located in /home/pguich/.local/bin/

I've created a essmqtt.service file in /etc/systemd/system. This is the file:

[Unit]
Description=ESS MQTT wrapper test

[Service]

all essmqtt command line arguments can be used here. it is recommended to con>

for this use case

ExecStart=/home/pguich/.local/bin/essmqtt

Restart will keep the service alive for instance in case the mqtt server goes>

when esmqqt starts

Restart=on-failure

a sensible restart delay prevents fast restart loops potentially denial-of-se>

RestartSec=10

[Install]

we'd like to start, but only after network is up

WantedBy=default.target
Wants=network-online.target

When I check the status of the service, I get this - and I'm not sure, but it looks to me it's not working as it should:

● essmqtt.service - ESS MQTT wrapper test
Loaded: loaded (/etc/systemd/system/essmqtt.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2023-08-04 10:59:36 BST; 793ms ago
Process: 6215 ExecStart=/home/pguich/.local/bin/essmqtt (code=exited, status=1/FAILURE)
Main PID: 6215 (code=exited, status=1/FAILURE)
CPU: 117ms

to me this doesn't look right, and I can confirm that after my ESS lost connection with the WiFi temporarily, the service didn't restart , I had to do it manually with the essmqtt command.

I've searched/googled what i might be doing wrong, but I'm at my wit's end.

Thanks for your help!

Two MQTT servers

Is it possible to publish the ess results to two MQTT servers?

I’m migrating my home assistant to another Raspberry, but I want to run both in parallel for a few hours to see if everything works before I turn off the old one. Pyess is running on an entirely different Raspberry.

btw, I’m extremely happy with pyess. Now if only the Wi-Fi connection on the ESS weren’t so unstable :(

Hassio 3023.09.3 ERROR:asyncio:Task exception was never retrieved

Since I have updated my HA OS to 3023.09.3 and the addon to 0.0.6 simultaneously any sensors are available anymore.

The log says the following. What’s the problem?

-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[11:33:53] INFO: Initialize the essmqtt configuration...
INFO:pyess.aio_ess:fetching auth key
INFO:pyess.essmqtt:starting send loop
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-17' coro=<_main..handle_control() done, defined at /usr/local/lib/python3.8/site-packages/pyess/essmqtt.py:180> exception=MqttError('Disconnected during message iteration')>
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pyess/essmqtt.py", line 182, in handle_control
async for msg in messages:
File "/usr/local/lib/python3.8/site-packages/aiomqtt/client.py", line 857, in _generator
raise MqttError(msg)
aiomqtt.error.MqttError: Disconnected during message iteration
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-18' coro=<_main..handle_control() done, defined at /usr/local/lib/python3.8/site-packages/pyess/essmqtt.py:180> exception=MqttError('Disconnected during message iteration')>
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pyess/essmqtt.py", line 182, in handle_control
async for msg in messages:
File "/usr/local/lib/python3.8/site-packages/aiomqtt/client.py", line 857, in _generator
raise MqttError(msg)
aiomqtt.error.MqttError: Disconnected during message iteration
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-19' coro=<_main..handle_control() done, defined at /usr/local/lib/python3.8/site-packages/pyess/essmqtt.py:180> exception=MqttError('Disconnected during message iteration')>
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pyess/essmqtt.py", line 182, in handle_control
async for msg in messages:
File "/usr/local/lib/python3.8/site-packages/aiomqtt/client.py", line 857, in _generator
raise MqttError(msg)
aiomqtt.error.MqttError: Disconnected during message iteration
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-23' coro=<_main..handle_control() done, defined at /usr/local/lib/python3.8/site-packages/pyess/essmqtt.py:180> exception=MqttError('Disconnected during message iteration')>
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pyess/essmqtt.py", line 182, in handle_control
async for msg in messages:
File "/usr/local/lib/python3.8/site-packages/aiomqtt/client.py", line 857, in _generator
raise MqttError(msg)
aiomqtt.error.MqttError: Disconnected during message iteration
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-24' coro=<_main..handle_control() done, defined at /usr/local/lib/python3.8/site-packages/pyess/essmqtt.py:180> exception=MqttError('Disconnected during message iteration')>
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pyess/essmqtt.py", line 182, in handle_control
async for msg in messages:
File "/usr/local/lib/python3.8/site-packages/aiomqtt/client.py", line 857, in _generator
raise MqttError(msg)
aiomqtt.error.MqttError: Disconnected during message iteration
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-25' coro=<_main..handle_control() done, defined at /usr/local/lib/python3.8/site-packages/pyess/essmqtt.py:180> exception=MqttError('Disconnected during message iteration')>
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pyess/essmqtt.py", line 182, in handle_control
async for msg in messages:
File "/usr/local/lib/python3.8/site-packages/aiomqtt/client.py", line 857, in _generator
raise MqttError(msg)
aiomqtt.error.MqttError: Disconnected during message iteration
WARNING:pyess.essmqtt:Expected exception while talking go ESS or MQTT server, restarting in 60 seconds.Usually this means the server is slow to respond or unreachable.
INFO:pyess.aio_ess:fetching auth key
INFO:pyess.essmqtt:starting send loop

Feature Request: Multiple Inverters

I have a setup with two ESS inverters. One of them is now integrated into Home Assistant. I would like to integrate the other one.

I don't think this is possible atm, because I am using a systemd service, and would need to call another service for the other inverter.

Furthermore, the ESS sends its state to mqtt using the topic "/ess/...". I imagine adding the second one would result in a few issues regarding the mqtt integration.

pyess/pyess/essmqtt.py

Line 55 in 182a17b

await recursive_publish_dict(mqtt_client, "ess/home", home)

I took a quick glance over the code and noticed this hardcoded mqtt topic. Would it be enough to change this topic and creating a new systemd service?

Run pyess as daemon/service under Linux, comments

I got my system up and running now, essmqtt is awesome, thanks for all the effort put in so far!
I have a couple of requests/ comments meanwhile:

• 1.) can essmqtt or esscli be run as service/daemon during startup under Linux? Currently I have to open a terminal, start the command and keep the terminal open. I tried a couple of entries in "etc/systemd/system" based on generic instructions from the internet but always failed. I put the essmqtt call in a shell script which works, but starting it as service doesn't work:

● essmqtt.service - ESS MQTT Communication
   Loaded: loaded (/etc/systemd/system/essmqtt.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2020-05-02 09:24:18 CEST; 3s ago
  Process: 20364 ExecStart=/home/user/essmqtt.sh (code=exited, status=1/FAILURE)
 Main PID: 20364 (code=exited, status=1/FAILURE)

May 02 09:24:18 iobroker-vm systemd[1]: Started ESS MQTT Communication.
May 02 09:24:18 iobroker-vm essmqtt.sh[20364]: Traceback (most recent call last):
May 02 09:24:18 iobroker-vm essmqtt.sh[20364]:   File "/home/user/.local/bin/essmqtt", line 5, in <module>
May 02 09:24:18 iobroker-vm essmqtt.sh[20364]:     from pyess.essmqtt import main
May 02 09:24:18 iobroker-vm essmqtt.sh[20364]: ModuleNotFoundError: No module named 'pyess'
May 02 09:24:18 iobroker-vm systemd[1]: essmqtt.service: Main process exited, code=exited, status=1/FAILURE
May 02 09:24:18 iobroker-vm systemd[1]: essmqtt.service: Failed with result 'exit-code'.

• 2.) The MQTT Broker updates all the values according to the set interval_seconds, but doesn't show that it is connected to the essmqtt client. As soon as I start mosquitto_sub, the MQTT Broker recognizes mosquitto_sub and shows it as client and mosquito_sub receives all the data from essmqtt split into #4

• 3.) Minor: typos in
  mqtt.0.ess.common.PCS.pcs_stauts is supposed to be pcs_status, I guess
  mqtt.0.ess.common.LOAD.today_batt_discharge_enery = energy

• 4.) Is there a clue what the satusses mean? E.g. pcs_status 3, what does the 3 stand for? That also applies to e.g. mqtt.0.ess.common.BATT.status split into #5

Thanks again for all the effort put in here!

V1.7: Error messages in Service status

I installed V1.7, MQTT communication with the server works however the following error messages are shown in systemctl status essmqtt:

● essmqtt.service - ESS MQTT Communication
   Loaded: loaded (/etc/systemd/system/essmqtt.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-05-30 19:05:05 CEST; 2min 40s ago
 Main PID: 126215 (essmqtt)
    Tasks: 1 (limit: 2290)
   CGroup: /system.slice/essmqtt.service
           └─126215 /home/user/essmqtt/bin/python3 /home/user/essmqtt/bin/essmqtt --mqtt_server 192.168.0.50 --ess_passwor

May 30 19:07:43 iobroker-vm essmqtt[126215]: ERROR:pyess.essmqtt:exception while sending to mqtt
May 30 19:07:43 iobroker-vm essmqtt[126215]: Traceback (most recent call last):
May 30 19:07:43 iobroker-vm essmqtt[126215]:   File "/home/user/essmqtt/lib/python3.8/site-packages/pyess/essmqtt.py", lin
May 30 19:07:43 iobroker-vm essmqtt[126215]:     await mqtt_client.publish("ess/home/" + key + "/" + key2, home[key][key2]
May 30 19:07:43 iobroker-vm essmqtt[126215]: TypeError: string indices must be integers
May 30 19:07:45 iobroker-vm essmqtt[126215]: ERROR:pyess.essmqtt:exception while sending to mqtt
May 30 19:07:45 iobroker-vm essmqtt[126215]: Traceback (most recent call last):
May 30 19:07:45 iobroker-vm essmqtt[126215]:   File "/home/user/essmqtt/lib/python3.8/site-packages/pyess/essmqtt.py", lin
May 30 19:07:45 iobroker-vm essmqtt[126215]:     await mqtt_client.publish("ess/home/" + key + "/" + key2, home[key][key2]
May 30 19:07:45 iobroker-vm essmqtt[126215]: TypeError: string indices must be integers

everytime I look into the status, the errors have the current time stamp, i.e. it seems as if the errors occur continously.
From what I understood the config file is optional, I can still work with the command line, right?

Cannot connect to ESS

My ESS is connected to a Fritzbox 7490 with ip address 192.168.178.45.
The pyess package is installed on Ubuntu 18.4 with python 3.8.
The default ip address 192.168.23.1 does not exist and cannot be ping'ed on my system.

esscli --action list_ess is able to find my device:
Searching for LG ESS devices on the network
found 1 devices:
1 DE2201BKRE017808

esscli --action get_password
failed: unable to connect to local ESS

Detailed messages:
Fetching ess password. For this you must be connected to the ESS wifi (or recently have been connected to it)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 159, in _new_conn
conn = connection.create_connection(
File "/usr/lib/python3/dist-packages/urllib3/util/connection.py", line 84, in create_connection
raise err
File "/usr/lib/python3/dist-packages/urllib3/util/connection.py", line 74, in create_connection
sock.connect(sa)
OSError: [Errno 101] Network is unreachable

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 665, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 376, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 996, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 314, in connect
conn = self._new_conn()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 171, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x7fb26efd98e0>: Failed to establish a new connection: [Errno 101] Network is unreachable
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 719, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='192.168.23.1', port=443): Max retries exceeded with url: /v1/user/setting/read/password (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fb26efd98e0>: Failed to establish a new connection: [Errno 101] Network is unreachable'))

This looks to me to be a wrong ip address of 192.168.23.1.
I changed the ip address from 192.168.23.1 to 192.168.178.45 to be able to connect to my local ESS, then again compiled with
pip install pyess.

However, still the old ip address appears, so what is the right way to recompile everything?

Thanks in advance.

Register last will and testament for essmqtt

@fu-zhou requets in #3 to have essmqtt register as a client with the mqtt server. I believe the way to do so would be to set a last will and testament. Currently the mqtt library used does not allow to do this, but I am splitting off this feature request to keep it in mind.

data missing in app/web while using mqtt

Hi,

recently I started to use the mqtt feature; I observed afterwards that the data during the time of my experiments is not available in the enervu app/web - a zero line in that period.

I assume that using the mqtt integration the data is no longer transmitted to the outside (or maybe not even stored on the device anymore?).

Ideally I would be interested in having both - the data in app/web plus some own integration
I wonder if this seems possible ..

and thanks for the work already done

unit of measurement wrong for homeassistant

Hi,

In essmqtt.py there is a wrong attribute:

if "enegy" in sensor or "energy" in sensor:  # typo in ess json
    description["**unit_of_measuremnt**"] = "Wh"
    description["icon"] = "mdi:gauge"

please set it to
if "enegy" in sensor or "energy" in sensor: # typo in ess json
description["unit_of_measurement"] = "Wh"
description["icon"] = "mdi:gauge"

Thanks for the great work!

Patrick

Connection to the ESS seems to be blocked

Hello,

thanks a lot for this great project, I use it for about an Year and had absolutely no problems with it.
Until yesterday... I had to restart my Fritz!Box and since then pyess has absolutely no communication with the ESS anymore.
I got an update some Days ago:
PCS Ver.: S/W: LG 04.00.01.00 R130 1.126.3
PMS Ver.: S/W: 10.05.7250
The Cloud is showing Data, so the connection is there. I can ping the ip from any computer, but not from my two Raspberry-Pi Boards, the one is Pi4 with 8GB and has pyess on it, the other ist Pi3b+ with Display. Both get lost all of the Ping Packets.
Does someone of you encounter such problems?
Any idea how I can solve this?

Greetings Jack

Typo still needs fixing

There was earlier fix to json typo in essmqtt.py

if "enegy" in sensor or "energy" in sensor or sensor.endswith("_sum"): # typo in ess json

but this does not fix the issue since there is typo in the fix afaik. The typo in ess json is "enery" not "enegy". I am not sure if this "enegy" typo exists but it would be possible to fix this changing code to

if "enegy" in sensor or "enery" in sensor or "energy" in sensor or sensor.endswith("_sum"): # typo in ess json

try to use with new resu system

Hi, i try to use this method with new LG resu system, but nothing happen, in terminal this is the result:
File "ess.py", line 64
def get_graph(self, device: str, timespan: str, date: datetime.datetime):

Access to installer settings

Hello!
@gluap
I saw that in the disclaimer you say that you only have customer-level access to your LG ESS inverter.
I actually found on a website that the password protected installer settings in the LG EnerVu Plus 1.3.2 android app can be accessed by typing in the "Registration NO." that is printed on the right side of the inverter (on the same sticker as the WLAN Password, just below it.) My Registration NO. for example is a 16 character sequence that starts with DE2011B... and the last 6 characters are integers.

For anyone who is reading this just be careful NOT TO CHANGE ANYTHING IF YOU DO NOT KNOW EXACTLY WHAT YOU ARE DOING because changes made in this menu can have more significant consequences and potentially break things.

Can

Communication with high PCS CPU Load

It seems that on my system (with a high alternating load during the day) the PCS has a lot to do managing the energy flow: charge battery, discharge, get from grid, feed to grid etc. The poll time of 10 seconds regularly leads to very low, unrealistic values for the load or power from the PV modules. Increasing the time to 20 seconds improves the stability of the transmitted values, but with a high load on the PCS's CPU, the communication seems not to be executed with a high priority. This still leads to a few unrealisticly low values being transmitted. There is no need to receive the daily or monthly accumulated values every 10 seconds, but for instance the load, PV power and active grid power would be good to have reliably every 5 seconds or even faster (I control the load with those values). Is there a way to define multiple intervall_times by e.g. starting two instances of essmqtt with limited data points each? Unfortunately the PCS's CPU load isn't part of the protocol and I have no idea if transmitting a few values with 5 seconds and the rest with 60 seconds would be handled reliably by the PCS. I would test the scenario but have no clue how to set that up.

Can't find ESS

Hi!

We have a V1 ESS (DE1704SVA00165) which is connected via LAN.
Unfortunately, running "esscli --action list_ess" can't find any ESS.

I know the local IP of the inverter - can I manually setup a connection or isn't it even compatible with this version?

Thanks

Can't run essmqtt anymore. error message about coroutine 'ClientSession.close' was never awaited.

I'm stumped. the Raspberry Pi where the MQTT broker is located shut down. After I restart, I can no longer run essmqtt on a different Rasperry pi. This is the error message I get:

pguich@pibackup:~ $ essmqtt
INFO:pyess.aio_ess:fetching auth key
Traceback (most recent call last):
File "/home/pguich/.local/bin/essmqtt", line 8, in
sys.exit(main())
File "/home/pguich/.local/lib/python3.9/site-packages/pyess/essmqtt.py", line 120, in main
asyncio.run(_main(arguments))
File "/usr/lib/python3.9/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
return future.result()
File "/home/pguich/.local/lib/python3.9/site-packages/pyess/essmqtt.py", line 194, in _main
await launch_main_loop(args, ess, handle_control, switch_active, switch_fastcharge, switch_winter)
File "/home/pguich/.local/lib/python3.9/site-packages/pyess/essmqtt.py", line 213, in launch_main_loop
async with Client(args.mqtt_server, port=args.mqtt_port, logger=logger, username=args.mqtt_user,
File "/home/pguich/.local/lib/python3.9/site-packages/aiomqtt/client.py", line 893, in aenter
await self.connect()
File "/home/pguich/.local/lib/python3.9/site-packages/aiomqtt/client.py", line 422, in connect
raise MqttError(str(error)) from None
aiomqtt.error.MqttError: [Errno 111] Connection refused
/home/pguich/.local/lib/python3.9/site-packages/pyess/aio_ess.py:205: RuntimeWarning: coroutine 'ClientSession.close' was never awaited
ERROR:asyncio:Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0xf623add8>
ERROR:asyncio:Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0xf50d5598>, 774.392811266)]']
connector: <aiohttp.connector.TCPConnector object at 0xf62fcd78>

The connection is refused, because of an Unclosed client session. What can I do? I'm a complete beginner, the fact that I was able to install and run press to begin with was a stroke of luck.

Many thanks for your help, and kind regards,

Pascal