Add-On Fenecon2Mqtt - Connect Fenecon Home (OpenEMS) energy storage systems to Homeassistant

Those listed as Beladeleistung (negativ) oder Ladeleistung (positiv) in your output. Each phase is also available right below that. Unless I misinterpret the sensor name :slight_smile:

Hello forum members,

I would like to rename an entity and also change the unit. Of course, the value must also be adjusted to the new unit. How do I do this?

Example:

Renaming is easy:

_sum/ConsumptionActiveEnergy → Self-consumption kWh

_sum/ConsumptionActiveEnergy;;;;;Self-consumption kWh

But how do I adjust the values? _sum/ConsumptionActiveEnergy is in Wh and should be displayed as kWh

1500Wh → 1.5kWh

You can use the value template in the overwrites to do the conversion, here is an example how I use it:

sensor_overwrite:
  - channel;device_class;state_class;device_unit;value_template;name
  - >-
    battery0/Tower0PackVoltage;voltage;measurement;V;{{value | int /
    10}};Live-FEMS: battery0/Tower0PackVoltage
  - >-
    ctrlGridOptimizedCharge0/TargetEpochSeconds;timestamp;measurement;;{{value |
    int(0) | as_datetime()}};Live-FEMS:
    ctrlGridOptimizedCharge0/TargetEpochSeconds

Or you could just use a template sensor, which can be configured easily in Home-Assistant UI as a helper nowadays.

Could you please explain this to me in more detail, preferably using my values ​​as an example, I’m still a complete beginner. :wink:

Got it, thank you thank you thank you

1 Like

Here is a finished example, works wonderfully:

  • _sum/ConsumptionActiveEnergy;;;kWh;{{ (value | int / 1000) | round (2) }};Eigenverbrauch Energie

One more question, how can I find out which channels there are? Is there a command that returns all available channels? If so, where do I have to enter it?

Oh, it’s a Primus system with Kaco Hybrid TL3 from Energy-Depot, based on OpenEMS and works quite well with the Fems plugin.

You can use a request like this one:

curl -s http://x:[email protected]:80/rest/channel/.*/.* -o channel-names.txt

You can also use an API tester as shown in the fenecon docs with the wildcard channel name: FEMS App REST/JSON Lese-/Schreibzugriff :: FENECON Dokumente

Am I doing something wrong here?

“curl http://x:[email protected]:80/rest/channel/.*/.* -o” C:\channel-names.txt

Hmm first of all, you there is not supposed to be a space between the second star and the dot.
Maybe it works then. If it still doesn’t work, then it might be possible that the REST-API is different or not supported on the non FEMS System

I had already seen and tested the thing with the star and the space (last entries in the command window). Then this query doesn’t seem to work for me. What a pity.

Hmm, you can try it with 8084 for the port instead of 80, maybe the web server there does not forward the rest API.

Unfortunately without success, testet with 8084, 8884, 8883, 1883, 1884

Do you get a 404 on Port 8084 as well or another error?

No, this:
curl: (7) Failed to connect to 192.168.168.138 port 8084 after 2083 ms: Could not connect to server

Ok, could you please send me (maybe privately) a screenshot of the page when you click on the top right corner on the online or offline portal? There should be a list of all the installed components.

Do you mean this:

Zähler

PV DC charger0

KACO blueplanet hybrid 10.0 TL3 DC Charger

hy-switch meter0

KACO blueplanet hybrid 10.0 TL3 Grid Meter

PV AC pv0 (Komponente ist inaktiv!)

KACO blueplanet hybrid 10.0 TL3 PV Inverter

Speichersysteme

Storage ess0

KACO blueplanet hybrid 10.0 TL3 Ess

Externe Schnittstellen

ctrlApiWebsocket0

Controller Api Websocket

Cloud-Schnittstellen

ctrlBackend0

Controller Api Backend

ctrlBackend1

Controller Api Backend

Geräte-Schnittstellen

kacoCore0

KACO blueplanet hybrid 10.0 TL3 Core

Standard-Komponenten

ctrlDebugLog0

Controller Debug Log

rrd4j0

Timedata RRD4J

scheduler0

Scheduler All Alphabetically

Weitere

Core.AppManager _appManager

Core App-Manager

Core.ComponentManager _componentManager

Core Component-Manager

Core.Cycle _cycle

Core Cycle

Core.Energy _energy

Core Energy Scheduler

Evcs.SlowPowerIncreaseFilter _evcsSlowPowerIncreaseFilter

EVCS Power

Core.Host _host

Core Host

Kaco Update _kacoUpdate

PRIMUS Update Handler

Core.Meta _meta

Core Meta

Ess.Power _power

ESS Power

Core.PredictorManager _predictorManager

Core Predictor-Manager

Yes, that is what I meant. There actually doesn’t seem to be the REST-API. Can you check if there is maybe an option in the settings to enable it or something like that?

If you can’t find anything, then you could try to view the network analysis in your browser and search for the websocket request after reloading the page. Then you can click it and go to the response tab and find the line with “subscribeChannels”. There you can see all the channels that the Web UI requests.