Contribute a HEMS

[christ0phd]

Hey,
we've just got out PV installed. It's an AlphaESS inverter with a HEMS from Energieversum. The modbus TCP interface of the inverter is blocked by the HEMS. But the HEMS should be available via EEBUS. This is why a found this project.
I would like to contribute to the project. At least with the data from the EV.cockpit HEMS.
As I am quite new to EEBUS as well as to the go language my question is: Is there any startup guide to fetch data of interest?
What I actually did was:

• clone all repositories of this project
• build devices-app and started it
• got the error Connecting ended in an error: websocket: close 1000 (normal) while trying to do pairing

Next I tried the binary provided as devices-app_1b42454_linux-amd64.tar.gz

• started the devices-app
• got no response in the shell after pressing "Start pairing process" in the web interface

My OS is a SuSE leap 15.6.

Christoph

[DerAndereAndi]

This project is basically a demo project to gather data about devices to see what kind of functionalities they actually make available.

EEBUS needs the user to pair devices with each other, on each side. Otherwise they will not talk to each other.

I am not sure what you mean with got no response in the shell after pressing "Start pairing process" in the web interface. Could you elaborate a bit more on what you actually do on which device and what happens when?

[christ0phd]

The SW build by me let me select the Brand & Model of my HEMS and switches to the second page. Here I can click on Start Pairing Process. Unfortunately this page emidetely show's the error message Connecting ended in an error: websocket: close 1000 (normal). In the shell where I startet the app from I get a huge bunch of output messages.
In contrast to this behaviour the progress indicator is running continously after clicking the Start Pairing Process button with the compiled SW. And in the shell I get only a few lines of output. So no response might be misleading. The amount is different.
But before posting lines of output I just want to make sure that I'm doing nothing totally wrong.
The last line of the shell output the pre-compiled SW gives me is:
DEBUG connection to 7624170828508219a693a0dcec86af4cfc0ed2dd failed: dial tcp: lookup 1u0022-se-986.local on 192.168.178.1:53: no such host
This is where I'm wondering as there is no computer with this name on the network and the steps before are only listing IP adresses.

[DerAndereAndi]

I don't think you are doing anything wrong. I'd need to see the trace log (running via command line is perfectly fine) to tell what's going on.

Right now it looks like the hostname mentioned in the mDNS record of the device, can not be resolved in your network. It should then try any of the reported IP addresses afterwards. If none of those work, it will retry the same after a few seconds and so on.

[christ0phd]

Ok, the output gathered from the pre-compiled SW is the following:

After startup:

2024/10/23 18:27:49 Web Server running at port 7050
2024/10/23 18:27:49 EEBUS Service running at port 4815
2024/10/23 18:27:49 Using certificate file ./cert.crt and key file ./cert.key
2024-10-23 18:27:49 INFO  Local SKI:  35127e13c1111d4be4e16ba2a7bbf83f981f585b
2024-10-23 18:27:49 DEBUG mdns: announce
2024-10-23 18:27:49 DEBUG mdns: using avahi
2024-10-23 18:27:49 DEBUG mdns: start search
2024-10-23 18:27:49 DEBUG starting websocket server on :4815
2024-10-23 18:27:49 DEBUG ski: 7624170828508219a693a0dcec86af4cfc0ed2dd name: MonitoringAppliance-1u0022-se-982 brand: Schneider_Electric model: HEMSlogic typ: HEMS identifier: 1u0022-se-982 register: false host: 1u0022-se-986.local port: 21599 addresses: [192.168.178.138]

After connecting to the webservice I get

2024/10/23 18:28:09 Sent:  {"name":"allowremote","ski":"","services":null,"enable":true}
2024/10/23 18:28:09 Received {"name":"serviceslist"}
2024/10/23 18:28:09 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"35127e13c1111d4be4e16ba2a7bbf83f981f585b","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":false,"state":0,"error":"","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}

And after pressing the Start Pairing button now I do not get any further output. In contrast to a few minutes ago :-(
The response from the try before was the following:

2024/10/23 18:15:52 Received {"name":"pair","ski":"7624170828508219a693a0dcec86af4cfc0ed2dd"}
2024/10/23 18:15:52 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"35127e13c1111d4be4e16ba2a7bbf83f981f585b","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":false,"state":1,"error":"","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}
2024-10-23 18:15:52 DEBUG trying to connect to 7624170828508219a693a0dcec86af4cfc0ed2dd at 192.168.178.138
2024-10-23 18:15:52 DEBUG initiating connection to 7624170828508219a693a0dcec86af4cfc0ed2dd at 192.168.178.138:21599
2024/10/23 18:15:52 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"35127e13c1111d4be4e16ba2a7bbf83f981f585b","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":false,"state":1,"error":"","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}
2024-10-23 18:15:52 DEBUG connection to 7624170828508219a693a0dcec86af4cfc0ed2dd failed:  websocket: bad handshake
2024-10-23 18:15:52 DEBUG trying to connect to 7624170828508219a693a0dcec86af4cfc0ed2dd at 1u0022-se-986.local
2024-10-23 18:15:52 DEBUG initiating connection to 7624170828508219a693a0dcec86af4cfc0ed2dd at 1u0022-se-986.local:21599
2024-10-23 18:15:53 DEBUG connection to 7624170828508219a693a0dcec86af4cfc0ed2dd failed: dial tcp: lookup 1u0022-se-986.local on 192.168.178.1:53: no such host

The output of the current and selfbuilt source is as follows:

Startup:

2024/10/23 18:34:32 Web Server running at port 7050
2024/10/23 18:34:32 EEBUS Service running at port 4815
2024/10/23 18:34:32 Using certificate file ./cert.crt and key file ./cert.key
2024-10-23 18:34:32 INFO  Local SKI: 9a6b215e6a0f73c5046dcc66bca9010991648907
2024-10-23 18:34:32 DEBUG starting websocket server on :4815
2024-10-23 18:34:32 DEBUG mdns: announce
2024-10-23 18:34:32 DEBUG mdns: using avahi
2024-10-23 18:34:32 TRACE mdns: avahi - process add service: MonitoringAppliance-1u0022-se-982 _ship._tcp local 1u0022-se-986.local 192.168.178.138 21599 map[brand:Schneider_Electric id:1u0022-se-982 model:HEMSlogic path:/ship/ register:false ski:7624170828508219a693a0dcec86af4cfc0ed2dd txtvers:1 type:HEMS]
2024-10-23 18:34:32 DEBUG mdns: new - ski: 7624170828508219a693a0dcec86af4cfc0ed2dd name: MonitoringAppliance-1u0022-se-982 brand: Schneider_Electric model: HEMSlogic typ: HEMS identifier: 1u0022-se-982 register: false host: 1u0022-se-986.local port: 21599 addresses: [192.168.178.138]
2024-10-23 18:34:33 TRACE mdns: avahi - process add service: EnbilityNet-Devices-App-123456789 _ship._tcp local majestix.local 127.0.0.1 4815 map[brand:EnbilityNet id:EnbilityNet-Devices-App-123456789 model:Devices-App path:/ship/ register:false ski:9a6b215e6a0f73c5046dcc66bca9010991648907 txtvers:1 type:EnergyManagementSystem]
2024-10-23 18:34:33 TRACE mdns: avahi - process add service: EnbilityNet-Devices-App-123456789 _ship._tcp local majestix.local 192.168.178.123 4815 map[brand:EnbilityNet id:EnbilityNet-Devices-App-123456789 model:Devices-App path:/ship/ register:false ski:9a6b215e6a0f73c5046dcc66bca9010991648907 txtvers:1 type:EnergyManagementSystem]

After connect

2024/10/23 18:35:33 Sent:  {"name":"allowremote","ski":"","services":null,"enable":true}
2024/10/23 18:35:33 Received {"name":"serviceslist"}
2024/10/23 18:35:33 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"9a6b215e6a0f73c5046dcc66bca9010991648907","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":false,"state":0,"error":"","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}

And after pressing Start pairing:

2024/10/23 18:35:55 Received {"name":"pair","ski":"7624170828508219a693a0dcec86af4cfc0ed2dd"}
2024/10/23 18:35:55 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"9a6b215e6a0f73c5046dcc66bca9010991648907","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":true,"state":1,"error":"","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}
2024-10-23 18:35:55 DEBUG trying to connect to 7624170828508219a693a0dcec86af4cfc0ed2dd at 1u0022-se-986.local
2024-10-23 18:35:55 DEBUG initiating connection to 7624170828508219a693a0dcec86af4cfc0ed2dd at 1u0022-se-986.local:21599/ship/
2024/10/23 18:35:55 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"9a6b215e6a0f73c5046dcc66bca9010991648907","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":true,"state":1,"error":"","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}
2024-10-23 18:35:56 TRACE 7624170828508219a693a0dcec86af4cfc0ed2dd SHIP state changed to: 1
2024-10-23 18:35:56 TRACE 7624170828508219a693a0dcec86af4cfc0ed2dd SHIP state changed to: 2
2024-10-23 18:35:56 TRACE Send: 7624170828508219a693a0dcec86af4cfc0ed2dd ship init
2024-10-23 18:35:56 DEBUG 7624170828508219a693a0dcec86af4cfc0ed2dd websocket read error:  websocket: close 1000 (normal)
2024-10-23 18:35:56 TRACE 7624170828508219a693a0dcec86af4cfc0ed2dd SHIP state changed to: 39
2024-10-23 18:35:56 DEBUG mdns: announce
2024-10-23 18:35:56 DEBUG mdns: using avahi
2024/10/23 18:35:56 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"9a6b215e6a0f73c5046dcc66bca9010991648907","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":true,"state":9,"error":"websocket: close 1000 (normal)","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}
2024-10-23 18:35:56 DEBUG delaying connection to 7624170828508219a693a0dcec86af4cfc0ed2dd by 9.93s to minimize double connection probability
2024/10/23 18:35:56 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"9a6b215e6a0f73c5046dcc66bca9010991648907","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":true,"state":9,"error":"websocket: close 1000 (normal)","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}
2024/10/23 18:35:56 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"9a6b215e6a0f73c5046dcc66bca9010991648907","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":true,"state":9,"error":"websocket: close 1000 (normal)","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}
2024/10/23 18:35:56 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"9a6b215e6a0f73c5046dcc66bca9010991648907","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""},{"ski":"7624170828508219a693a0dcec86af4cfc0ed2dd","trusted":true,"state":9,"error":"websocket: close 1000 (normal)","brand":"Schneider_Electric","model":"HEMSlogic","itself":false,"discovery":"","usecase":""}],"enable":false}

Do you need any further information?

[DerAndereAndi]

Once the app can get a connection to the HEMS, the HEMS is closing the connection right after start. I don't know why. Do you have to enable a pairing mode or anything like that on the device?

[christ0phd]

Well, I don't have any further information of this HEMS. It's just like a blackbox sent into my home ;-)
But I will ask this questin to the guys from the tec support and will come back with the answer as soon as possible.