SHP2 switch control via MQTT

[LSR19]

The following MQTT /set commands are documented in the EcoFlow developer documentation for controlling the following SHP2 switches via the Ecoflow North America cloud (api-a): AC1, EPS Mode, Storm Mode, and Charge Now. The topic is: /open/${certificateAccount}/${sn}/set. Payloads are: (1) For AC1 - { "id": 123456789, "version": "1.0", "cmdCode": "PD303_APP_SET", "params": { "ch1EnableSet": 0 }} [note - use ch2 or ch3 for AC2 or AC3]; (2) Storm Guard - { "id": 123456789, "version": "1.0", "cmdCode": "PD303_APP_SET", "params": { "stormIsEnable": true }} [note - or :false]; (3) EPS switch - { "id": 123456789, "version": "1.0", "cmdCode": "PD303_APP_SET", "params": { "epsModeInfo": true }} [note - or false]; and (4) Charge Now - { "id": 123456789, "version": "1.0", "cmdCode": "PD303_APP_SET", "params": { "ch1ForceCharge": "FORCE_CHARGE_ON" }} [note - or FORCE_CHARGE_OFF; for ch2 & ch3, change ch1ForceCharge accordingly].

[foxthefox]

I will have a check how this will relate to the protobuf interface. The adapter does not use the developer api, but the messages are similar composed.
If some logs are needed, I will ask you.
Earliest on the weekend I have time for it.

[foxthefox]

Unfortunately I could not find a mapping within the protobuf.

can you put the adapter in debug mode and checkmark some items, as here explained:
doc/en/IOB_HA/logging.md

When you changes these "switches" in the APP you should have some entries in the log with "[set]" I would need these portions, including the raw string.
It might also be triggered when you use your approach.

[LSR19]

Unfortunately I no longer have the adapter installed to do this. I uninstalled it when I figured out how to toggle the switches directly from Home Assistant.

[mfugate1]

Logs when I turned AC2 off:

msg#0 => shp2cmd {}
msg#0 pdata: c80102
msg#0 header {"src":32,"dest":11,"dSrc":1,"dDest":1,"encType":1,"cmdFunc":12,"cmdId":33,"dataLen":3,"needAck":1,"seq":147371188,"productId":1,"version":19,"payloadVer":1,"from":"Android"}
stream has 1 message(s)
raw (hex): 0a2e0a03c801021020180b200128013001400c48215003580170b4e9a2467801800113880101ba0107416e64726f6964
msg#0 => shp2cmd {}
msg#0 pdata: c80102
msg#0 header {"src":32,"dest":11,"dSrc":1,"dDest":1,"encType":1,"cmdFunc":12,"cmdId":33,"dataLen":3,"needAck":1,"seq":147361187,"productId":1,"version":19,"payloadVer":1,"from":"Android"}
stream has 1 message(s)
raw (hex): 0a2e0a03c801021020180b200128013001400c48215003580170a39ba2467801800113880101ba0107416e64726f6964
msg#0 => shp2cmd {}
msg#0 pdata: c80102
msg#0 header {"src":32,"dest":11,"dSrc":1,"dDest":1,"encType":1,"cmdFunc":12,"cmdId":33,"dataLen":3,"needAck":1,"seq":134691186,"productId":1,"version":19,"payloadVer":1,"from":"Android"}
stream has 1 message(s)
raw (hex): 0a2e0a03c801021020180b200128013001400c48215003580170f2f29c407801800113880101ba0107416e64726f6964

Logs when I turned AC2 on:

msg#0 => shp2cmd {}
msg#0 pdata: c80101
msg#0 header  {"src":32,"dest":11,"dSrc":1,"dDest":1,"encType":1,"cmdFunc":12,"cmdId":33,"dataLen":3,"needAck":1,"seq":168671185,"productId":1,"version":19,"payloadVer":1,"from":"Android"}
stream has 1 message(s)
raw (hex):  0a2e0a03c801011020180b200128013001400c48215003580170d1efb6507801800113880101ba0107416e64726f6964
msg#0 => shp2cmd {}
msg#0 pdata: c80101
msg#0 header  {"src":32,"dest":11,"dSrc":1,"dDest":1,"encType":1,"cmdFunc":12,"cmdId":33,"dataLen":3,"needAck":1,"seq":168661184,"productId":1,"version":19,"payloadVer":1,"from":"Android"}
stream has 1 message(s)
raw (hex):  0a2e0a03c801011020180b200128013001400c48215003580170c0a1b6507801800113880101ba0107416e64726f6964
msg#0 => shp2cmd {}
msg#0 pdata: c80101
msg#0 header  {"src":32,"dest":11,"dSrc":1,"dDest":1,"encType":1,"cmdFunc":12,"cmdId":33,"dataLen":3,"needAck":1,"seq":146301183,"productId":1,"version":19,"payloadVer":1,"from":"Android"}
stream has 1 message(s)
raw (hex):  0a2e0a03c801011020180b200128013001400c48215003580170ffc1e1457801800113880101ba0107416e64726f6964

[foxthefox]

@mfugate1
Thank you very much. That helps and I can implement it.
Can you check if the datapoint "ch2EnableSet" is changing accordingly?
It should present probably wrong numbers 0: 'off?', 1: 'on?' and will show 2 as unnknown.
According to your snippet 1:'ON', 2'OFF' is to be corrected.
Is there a third value possible to set? E.g. AC2 to standby (which could be the 0) or may be 0 represents not connected?

[LSR19]

I may be able to answer your last inquiry. Based on the work I’ve done to control the DPU directly from Home Assistant, the ACx switches (AC1 via ch1EnableSet, etc.) have only 2 operative Boolean states - On (1) and Off (2). A third state (0) is documented as “no operation.” I am not aware of a ‘standby’ state. It is thus important for users to understand if ACx is not on, battery power will be disconnected from the SHP2. In the event of a grid outage, the battery with ACx off will not power the loads.

[foxthefox]

@LSR19 thanks for feedback.

Correction can be tested with the version 1.4.8 from github.