foxthefox

Perfect! Now there is the missing other telegram ``` { "DisplayPropertyUpload": { "errcode": 0, "powInSumW": 135, "powOutSumW": 135, "energyBackupEn": false, "energyBackupStartSoc": 50, "powGetQcusb1": 0, "powGetQcusb2": 0, "powGetTypec1": 0, "powGetTypec2": 0,...

Very good if you have the setup made successfully. In general there are hints in the readme of the adapter/gift repo. In the section for HA is additionally a link...

@AlphaZuluNRW It would be good, if you open a new issue for delta3 in my repo (the right place for this discussion ;-) ). Nevertheless the log should contain at...

Correct, gen 3 devices are not yet in this integration. It is only through the iobroker adapter and its gateway to HA.

I think that only energy values should be connected to the energy dashboard, not power values. I will check if there is something missing, to make them compatible. Something like...

I have checked the situation. In the current set of data is no entitity which can be used for the energy dashboard. There should be a datastructure incomming with the...

I have created a new version 1.4.0 on npm and git (to be installed via expert mode). There are some more values, but no energy (except accuChg/Dsg). There is a...

Indeed River2 is not yet implemented because of sample missing data to this device. Therefore I would need some data. If I remember right you did some actions with the...

Once again, the river2 is not implemented in the adapter. That’s means that the trial with other devices may work in terms of data reception, but especially with commands it...

Would it be possible that you enable the debug mode and activate msgSetGet and msg update plus debug enable on River2Max(River2). That should show the JSON messages of the River2....