I dumped the CT003 for a HomeWizzard P1 ...
The CT003 was way to unstable for me

it would be nice if USR woulld combine the DR134 software with wifi and release an update for the DR164 that includes the functions needed ...

I also use a powerline adapter to get to my garage where my Marstek is ...
the wifi part of that powerline adapter makes the Marstel connection to my wifi way more stable too !!!
So it is just waiting for PUSR to release firmware for the DR164 that supports the same as the DR134

I just tried the PUSR-DR164 and at least the menu's are totally different. I doubt if that one is going to work, perhaps some other device ???? there is some mqtt but no "point" menu where the modbus registers can be configured no edge menu either ... Screenshot 2025-08-03 at 15.21.18.png

I also have a wifi version of the adapter, I will power it on and compare

tnx @walthervl http://IP/json.htm?type=command&param=getdevices&rid=225 that is the battery device, gives (not complete) { "AddjMulti" : 1.0, "AddjMulti2" : 1.0, "AddjValue" : 0.0, "AddjValue2" : 0.0, "BatteryLevel" : 255, "Counter" : "102.150", "CounterDeliv" : "83.230", "CounterDelivToday" : "2 ...

Ok, the reason for not showing up is that an attribute is not filled for this device. each device type has a certain amount of attributes that can be filled. I still can not find a list of devices with there attributes and how to fill them ... in the dzevents examples there is -- kWh, Electricity ...

Hi @RNEE it is indeed working. But, not all, for example : MPWR is not returning any value thru mqttmapper... {"params":{"dir":"up","id":"02103225071800005978","r_data":[{"name":"batterySOC","value":"31","err":"0"},{"name":"ACpower","value":"289","err":"0"},{"name":"MTCE","value":"10185","err":"0 ...

found it !

had /Marstek as topic, it seems to be working now

Sorry, what do you mean ?

So today I received my PUSR-DR134 setting up needed a windows laptop here because the PUSR-DR134 default does NOT use dhcp but starts on 192.168.0.7 ... after using the setuptool from the PUSR website on windows it is working on DHCP following the instructions on https://github.com/RneeJ/Domoticz ...

Nice work @RNEE ...
Hope to receive my PUSER-DR134 soon and follow your work to get stuff going.

add the following lines to /opt/stacks/domoticz/config/customstart.sh

echo installing python requirements for solaredge-modbus-tcp
cd /opt/domoticz/userdata/plugins/domoticz-solaredge-modbustcp-plugin/
python3 -m pip install -r requirements.txt --upgrade
echo done

RNEE wrote: ↑Wednesday 23 July 2025 13:36 The data in the Marstek app, are not available anymore when the modbus connection is used.
Thats oke for me when i can get them into Domoticz.

Is it only the "sluggish" presentation in the app ?
The app is needed to connect to wifi and to a p1, or are those fields availiable in mqtt ?

I have the following json description "Modes": { "topic": "myhome/topic/Modes", "type": "244", "subtype": "62", "switchtype": "18", "options": {"SelectorStyle":"0", "LevelOffHidden": "true", "LevelNames":"Off|normal|turbo|quiet"}, "mapping": {"item": "", "default": "0", "values": {"Off": "0 ...

I recently started playing with mqttmapper and I found it really nice.
transformed the nodered implementation for my HaierAC into mqttmapper and that works realy well

I had the same issue with the Battery, it had a too weak wifi signal. Putting an old accesspoint close to it made it work much better ... I also swapped the CT003 for a HomeWizzard P1 ... Looks it is stable for a couple of days now. The original app is sluggish ... My modbus-wifi adapter arrived ...

tnx, this addition to the documentation is exactly what I was looking for.

I hoped that flags like "Protected" and "icon type" for a switch where setable but they are not (yet) in the list.

I am running the jvdz version on my docker/bookworm domoticz. Works fine here

tnx for the suggestions but this is not what I am looking for ...

a list of all "options" that can be used in MqttMapper.json while creating a device ...
that is not documented on the MqttMapper documentation and would be very nice to have.