Dokumentation request

[Hofyyy]

Hello Martin,

first of all. Thanks for the great project. I try to connect a "Powerfox" Grid meter to my Victron management system. Until now I have a MQTT Topic which updates every 3 sec. the WATT number from all phases.

I am not sure if this questions are right in the Issue section, but i did not find a discussion page or something like that.

Now I have to ask stupid questions. But maybe this helps to enhance the documentation.

1. clientId

   • On which MQTT server or client is this generated?
   • How can I find it? At the moment I use my own mosquito, Redflow and MQTT Explorer to try to generate exact the tuple your driver would need. So I play locally before pushing wrong data to your driver.

2. And maybe you could also add a "grid" example?

3. "devices/*" vs "device" In the documentation I am not sure which is the right MQTT root path. device"s" vs. device?

[freakent]

I have no problem with people Raising Issues to ask for help. Better here than on Victron forum as I get automatic alerts from GitHub.

[freakent]

The ClientId is actually up to you. Just pick a meaningful name, but don't use any special characters like :-/ etc as DBUS will complain.

In theory it would be good to use the same Client Id in your MQTT initialisation but because of the DBUS special character limitations I didn't enforce that.

[freakent]

An example for Grid is a good idea. The Grid support was contributed by @stundenblume, perhaps he can provide an example too.

[freakent]

The correct MQTT topic is “device” singular. Thanks for finding the typo!

[Hofyyy]

One more typo. In the "Install and Setup" section you use the "Install Version" that makes trouble after each release.

Current examples:

• wget -O dbus-mqtt-devices.zip https://github.com/freakent/dbus-mqtt-devices/archive/refs/tags/**v0.4.1.zip**
• ./dbus-mqtt-devices-0.3.1/bin/setup.sh
• ln -s /data/drivers/dbus-mqtt-devices-0.2.1/bin/service /service/dbus-mqtt-devices

Idea: Maybe you could remove the version from the install folder. And add it into the executable. "./dbus-mqtt-devices -v" would output "0.4.1"

This would also support easier updates, because the driver links for autom. starting will stay stable.

[freakent]

Thanks for finding these. I clearly need to find a way to update all of these when I update the version number. I'll put some thought to it.

[stundenblume]

An example for Grid is a good idea. The Grid support was contributed by @stundenblume, perhaps he can provide an example too.

Hi @Hofyyy, you should connect to the victronOS via MQTT-Explorer, so you can observe the devices created with this driver. After that, you can write to the corresponding topics with the software of your choice. A grid device looks like this: Some notes:

1. the victronOS sends for 60sec MQTT data after writing something to R/<portalID>/system/0/Serial
2. writing the L1 power to a grid meter is done with topic W/<portalID>/grid/<assignedInstance>/Ac/L1/Power and W/<portalID>/grid/<assignedInstance>/Ac/Power Payload: {"value": 100} Notice the leading W!

Is that clear? Are you the one who would like to use the Tasmota device? Than I can provide you my rules.

[Hofyyy]

Thank you for the Detailed Information. I use Powerfox for Grid and two tasmota behind the pv inverter.

So yes. Tasmota examples would be great

Bit I can not test AT the Moment because I got install errors. See second github issue

[stundenblume]

OK, a friend of mine will read his smartmeter with Tasmota and will use this driver for venusOS. I use this driver for my inverters. For me the install for 4.0.0.1 on venusOS works without issues.

Tasmota rules:

1. get your instance number ON System#Boot DO Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON
2. this is the example for my inverter, on grid you will have all three phases ON System#Boot DO Backlog mem1 <VRM portalID>; mem2 <assignedInstance>; mem3 <phase[1,2,3]>; mem4 <maxKwp>;PowerDelta 101; TelePeriod 0 ENDON

minimal rule set:

Rule1 
   ON System#Boot DO Backlog mem1 <VRM portalID>; mem2 <assignedInstance>; mem3 <phase[1,2,3]> ENDON

   ON System#Boot DO Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON

   ON Energy#Power[2] DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON

full set an a Sonoff DUAL R3:

Rule1 
 ON System#Boot DO Backlog mem1 <VRM portalID>; mem2 <assignedInstance>; mem3 <phase[1,2,3]>; mem4 <maxKwp>;PowerDelta 101; TelePeriod 0 ENDON

 ON System#Boot DO Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON

 ON Energy#Power[2] DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON

 ON Energy#Current[2] DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Current {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/Current {"value": %value%} ENDON
 ON Energy#Voltage DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Voltage {"value": %value%} ENDON
 ON Energy#Total DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Energy/Forward {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Energy/Forward {"value": %value%} ENDON

[Hofyyy]

Maybe total stupid question. Which Software handels the rulessets you described?

[stundenblume]

Tasmota itself

[Hofyyy]

Ahh thats great. Then I could have a cool Setup. For Grid I will use an EM24 original Meter. but for the two inverter I have tasmota. So I should be able to get that working

[stundenblume]

That is exactly my setup. EM24 for grid and three Tasmota devices as pvinverters. The friend refused to by the expensive EM24. There we will use a Tasmota device which reads his SML Smartmeter and writes via the rules into the venusOS. By the way, we ( 6 persons with growing PV installations) are located near Oldenburg.

[Hofyyy]

Cool. #Hannover. Thats Sounds great. I hope I will be able to install it Direct on my gxcc. because I will add one 800W multiplus 24V With 2x60kg 210ah AGM Truck Batterie. Thanks for the Support.

[stundenblume]

Some of us are using Pylontech Batterys and others pure Lifepo Cells. Are you using new AGM Batteries or used ones?

Here is a ruleset for a pvinverter where no further action should be required. Right now it doesn't work because Tasmota reads the "VRM portalID" in upper case and you have to input it yourself.

Rule1 
 ON System#Init DO Backlog mem3 1; mem4 0.25; PowerDelta 101; TelePeriod 0 ENDON

 ON mqtt#connected DO Backlog Subscribe DBusInfo, device/%deviceid%/DBus; Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON
 ON Event#DBusInfo#portalId DO mem1 <VRM portalID> ENDON
 ON Event#DBusInfo#deviceInstance#wr DO mem2 %value% ENDON

 ON System#Boot DO Publish W/%mem1%/pvinverter/%mem2%/Ac/MaxPower {"value": %mem4%} ENDON

 ON Energy#Power[2] DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON

 ON Energy#Current[2] DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Current {"value": %value%} ENDON
 ON Energy#Voltage DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Voltage {"value": %value%} ENDON

 ON Energy#Total DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Energy/Forward {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Energy/Forward {"value": %value%} ENDON

[Hofyyy]

THX. New Batteries Direct from the Research and Produktion line. My Familie works in a big Company In Hannover. So I get some test Batteries.

[Hofyyy]

PowerDelta

Hello @stundenblume I try to understand every rule now. Could you explain me what the PoweDelta does and why it is 101?

If I understand this correct, it defines a threshold until when further things are reportet. Because my panels are 0W to 600W on one tasmota I would set the threshhold to 5W!?!

Best regards

[stundenblume]

PowerDelta: 1 - 100 means 1 to 100% change of the power. From 101 it means power change in W with a offset of 100W. 1 = 1% 10 = 10% 100 = 100% 101 = 1W 110 = 10W 2100 = 2000W

I don't know if it's really mandatory to set that parameter.

TelePeriod 0 is to not overload the Victron MQTT Broker.

After talking to some people who know Tasmota, it's unlikely that it will be possible to read the VRM portalID with rules. Rules will always parse and change to upper case.

Here the latest version. Just fill mem1, mem3 and mem4:

Rule1 
 ON System#Init DO Backlog mem1 <VRM deviceID>; mem3 <phase[1,2,3]>; mem4 <kWpMax>; PowerDelta 101; TelePeriod 0 ENDON

 ON mqtt#connected DO Backlog Subscribe DBusInfo, device/%deviceid%/DBus; Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON
 ON Event#DBusInfo#deviceInstance#wr DO mem2 %value% ENDON

 ON System#Boot DO Publish W/%mem1%/pvinverter/%mem2%/Ac/MaxPower {"value": %mem4%} ENDON

 ON Energy#Power[2] DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON

 ON Energy#Current[2] DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Current {"value": %value%} ENDON
 ON Energy#Voltage DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Voltage {"value": %value%} ENDON

 ON Energy#Total DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Energy/Forward {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Energy/Forward {"value": %value%} ENDON

[Hofyyy]

Thanks!

Id as String? "ABC" or ABC Phases=1 KWP=0.6 or 600W?

[stundenblume]

ON System#Init DO Backlog mem1 b7eb8b3b; mem3 1; mem4 0.6; PowerDelta 101; TelePeriod 0 ENDON

[stundenblume]

On which device did you flash Tasmota? If you just have one channel for power your rule looks a little different ("Energy#Power" vs "Energy#Power[2]" (for channel 2)). This would be a minimal version:

Rule1 
 ON System#Init DO Backlog mem1 <VRM deviceID>; mem3 <phase[1,2,3]> ENDON

 ON mqtt#connected DO Backlog Subscribe DBusInfo, device/%deviceid%/DBus; Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON
 ON Event#DBusInfo#deviceInstance#wr DO mem2 %value% ENDON

 ON Energy#Power DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON

current, voltage, energy counter, maxPower are all just optinal

I hope not to confuse you. :-D

[Hofyyy]

No. All is fine

Gosund SP1 v23

[Hofyyy]

Bähm! Its working perfekt on the test mosquito server now. I can test it finally, wen the driver does work on my real CCXG. Then I will switch the MQTT Server

[stundenblume]

Perfect!

[freakent]

Great collaboration here, guys 👏👏. I wonder if we should have a wiki page on this project where you can share all this knowledge? @stundenblume, If I set it up would you add your Grid tips?

[Hofyyy]

Just for Info: This tasmota helper tool is amasing: https://github.com/jziolkowski/tdm/

[stundenblume]

Great collaboration here, guys clapclap. I wonder if we should have a wiki page on this project where you can share all this knowledge? @stundenblume, If I set it up would you add your Grid tips?

Yes, I would fill it with information for "pvinverter" and later "grid" when I had a change to gain some experience. I already have a small documentation for myself. I also would like to write something on the victron forum to gain some attention to your extremely useful project.

[freakent]

@stundenblume, do you see an edit button here? https://github.com/freakent/dbus-mqtt-devices/wiki/PV-Inverter

[stundenblume]

@stundenblume, do you see an edit button here? https://github.com/freakent/dbus-mqtt-devices/wiki/PV-Inverter

Yes, thanks!

[Hofyyy]

@stundenblume Now I was able to do a real test. Registration is running.

But the Values are not on the right topic. Is used the ClientID instead of the deviceinstance in the MQTT Path .. any idea? So MEM2 seems to be wrong ...

Rule1 ON System#Init DO Backlog mem1 IDIDIDIIDIDID; mem3 1 ENDON

ON mqtt#connected DO Backlog Subscribe DBusInfo, device/%deviceid%/DBus; Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON ON Event#DBusInfo#deviceInstance#wr DO mem2 %value% ENDON

ON Energy#Power DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON

[Hofyyy]

@stundenblume Hello, short summary. All is working very well now.

Two small open points: 1. I need to set "mem2 manually" -> mem2 1 and mem2 2 then all is working fine. If I understand it correct: "DO mem2 %value% ENDON" is not working.

2. I get mqtt updates in my Tasmota every 200ms. Can I change the update intervall of the Rule?

But it works already amazing!

[stundenblume]

@stundenblume Hello, short summary. All is working very well now.

Two small open points: 1. I need to set "mem2 manually" -> mem2 1 and mem2 2 then all is working fine. If I understand it correct: "DO mem2 %value% ENDON" is not working.

I get mqtt updates in my Tasmota every 200ms. Can I change the update intervall of the Rule?

But it works already amazing!

1. In Tasmota on ESP8266 devices "subscribe" is not included in the precompiled binaries. So Event#DBusInfo#deviceInstance#wr will never be triggered an mem2 won't be filled with the "instanceID". Solutions:

   1. Set mem2 manually on the first line in Rule1 after you know it. ON System#Init DO Backlog mem1 <VRMdeviceID>; mem2 <deviceInstance>; mem3 <phase[1,2,3]>; mem4 <kWpMax>; PowerDelta 101; TelePeriod 0; VoltRes 1; SetOption129 1 ENDON
   2. compile a binary with

      #ifndef SUPPORT_MQTT_EVENT
      #define SUPPORT_MQTT_EVENT
      #endif

   3. use ESP32 hardware
2. 1. You can use Time#Minute as trigger
   2. You can prefix the sensor witch Tele- then it will be send with every TelePeriod

This example should send every 11 seconds:

Rule1 
 ON System#Init DO Backlog mem1 <VRMdeviceID>; mem2 <deviceInstance>; mem3 <phase[1,2,3]>; mem4 <kWpMax>; TelePeriod 11 ENDON

 ON mqtt#connected DO Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON

 ON Tele-Energy#Power DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON

You can change TelePeriod by typing teleperiod 11 into the web console.

I ordered your hardware, than I can test it myself.

[Hofyyy]

Thank you for the perfect answer. I will change mem2 to hardcoded value. Thats totaly fine for me.

And I will try to change the intervall to 2 seconds. I think that should be more then enough.

[stundenblume]

TelePeriod: See current value and force publish STATE and SENSOR 0 = disable telemetry 1 = reset telemetry period to firmware default (TELE_PERIOD)10..3600 = set telemetry period in seconds (default = 300)

[stundenblume]

With RuleTimers it would be possible to get intervals < 10 sec. Will send later an example.

[stundenblume]

This should work (untested). Just set mem5 2:

Rule1 
 ON System#Init DO Backlog mem1 <VRMdeviceID>; mem2 <deviceInstance>; mem3 <phase[1,2,3]>; mem5 <intervall> TelePeriod 0NDON

 ON mqtt#connected DO Backlog Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}}; RuleTimer1 %mem5% ENDON

 ON Rules#Timer=1 DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %var1%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %var1%}; RuleTimer1 %mem5% ENDON

 ON Energy#Power DO var1 %value% ENDON

[Hofyyy]

Darf ich fragen was die letzte Zeile tut?

[stundenblume]

The last line updates var1 on every new "Power" reading/update. As far as I know, there is no shorter way.

[Hofyyy]

If I see it correct, I only have mem1, mem2 and mem3. Further more 10 sec. are fine.

I will test the following rules tomorrow

PV1

Rule1 ON System#Init DO Backlog mem1 ; mem2 1; mem3 1; PowerDelta 101; TelePeriod 10 ENDON

ON mqtt#connected DO Backlog Subscribe DBusInfo, device/%deviceid%/DBus; Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON

ON Tele-Energy#Power DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON ON Tele-Energy#Current DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Current {"value": %value%} ENDON ON Tele-Energy#Voltage DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Voltage {"value": %value%} ENDON

PV2

Rule1 ON System#Init DO Backlog mem1 ; mem2 2; mem3 1; PowerDelta 101; TelePeriod 10 ENDON

ON mqtt#connected DO Backlog Subscribe DBusInfo, device/%deviceid%/DBus; Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON

ON Tele-Energy#Power DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON ON Tele-Energy#Current DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Current {"value": %value%} ENDON ON Tele-Energy#Voltage DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Voltage {"value": %value%} ENDON

[stundenblume]

Gosund SP1 v23

@Hofyyy My Gosund devices SP1-C_V2.4 arrived today. Was it possible to use Tuya-Convert or did you flash it via serial adapter?

[Hofyyy]

I di it With some wlan hack without open the Device.

[stundenblume]

OK. The first one I flashed via serial adapter. The next one I will try Tuya-Convert. Did you use that software or something else?

The SP1 is a very nice and well designed device. It could be a bit smaller but the price is also very good and suited for 16A is always on the safe site.

[Hofyyy]

Hey, I flashed the software some years ago. so i do not know what i used. sorry. But Tuya convert sounds good. yea 16A was also a reason from my side.

[Hofyyy]

@stundenblume I had the problem that after a "power shutdown", that the devices were not registeres anymore in the Victron. A second manual reboot of the SP1s solved the issue.

It seems to be that the SP1s booted first, after power was on again (ok they shoult boot fast). Could you test to power down the Victron Main System or reboot it?

Maybe its also a bug in the driver, because the driver may start after the MQTT broker on the system. But the SPs1 do register right after MQTT broker is online?!? So we might need a registration delay of some seconds in the rule ...

I would like to get it 100% robust. And I do not want to have a fixed boot order.

Testing with reboot confirmed it on my side. I opened one more issue.

[stundenblume]

See my answer here.

[stundenblume]

@Hofyyy today I noticed that "powerDelta" overrides "telePeriod". That means if you set PowerDelta 110 you will get updates of the power reading if it changed by 10W, even faster than 10sec.

[Hofyyy]

@stundenblume Thank you for the information. My feeling was that to much changes are not so good for this device. And from my point of view I do not need updates so often, because it is not a grid device.

You fill find my current rule below. I will now delete the PowerDelta Setting?!

Rule1 ON System#Init DO Backlog mem1 "dsffddffs"; mem2 1; mem3 1; PowerDelta 101; TelePeriod 10 ENDON

ON mqtt#connected DO RuleTimer1 10 ENDON ON Rules#Timer=1 DO Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON

ON Tele-Energy#Power DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON ON Tele-Energy#Current DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Current {"value": %value%} ENDON ON Tele-Energy#Voltage DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Voltage {"value": %value%} ENDON

[Hofyyy]

I did not remove PowerDelta. Further more I changed it to "0" which means off.

[stundenblume]

Rule1 ON System#Init DO Backlog mem1 "dsffddffs"; mem2 1; mem3 1; PowerDelta 101; TelePeriod 10 ENDON

ON mqtt#connected DO RuleTimer1 10 ENDON ON Rules#Timer=1 DO Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON

ON Tele-Energy#Power DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON ON Tele-Energy#Current DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Current {"value": %value%} ENDON ON Tele-Energy#Voltage DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Voltage {"value": %value%} ENDON

@Hofyyy You also should publish your "Total Energy", I think otherwise VRM won't be able the show/graph you pv data.

[Hofyyy]

@stundenblume Thanks for the info. I am not sure if that was necessary.

Thats at the moment my final rule.

Rule1 ON System#Init DO Backlog mem1 "VICTRONID"; mem2 1; mem3 1; PowerDelta 0; TelePeriod 10 ENDON

ON mqtt#connected DO RuleTimer1 30 ENDON ON Rules#Timer=1 DO Publish device/%deviceid%/Status {"clientId":"%deviceid%","connected":1,"version":"v1.0 ALPHA","services":{"wr":"pvinverter"}} ENDON

ON Tele-Energy#Power DO Backlog Publish W/%mem1%/pvinverter/%mem2%/Ac/Power {"value": %value%}; Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Power {"value": %value%} ENDON ON Tele-Energy#Current DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Current {"value": %value%} ENDON ON Tele-Energy#Voltage DO Publish W/%mem1%/pvinverter/%mem2%/Ac/L%mem3%/Voltage {"value": %value%} ENDON ON Tele-Energy#Total DO Publish W/%mem1%/pvinverter/%mem2%/Ac/Energy/Forward {"value": %value%} ENDON