search

twonk / MyEnergi-App-Api

Investigation of the MyEnergi App
134 stars 26 forks source link

cgi-jstatus-Z json properties #14

Open LeiChat opened 3 years ago

LeiChat commented 3 years ago

Hi. Thanks for this very helpful resource.

Sharing a couple of observations in case they are of use for your Wiki.

"fwv":"3560S3.142", -- I currently have v3.142 "vol":2343,

For my device, the "fwv" value appears to include a four digit number, followed by an S and then the firmware version that shows on the device and the "vol" is returning a four digit integer, rather than a double.

Here are some additional properties which I didn't spot in your Wiki that appear in the response for me:

"bsm":0, "bss":0, "ectt5":"None", "ectt6":"None", "pwm":5300, "rac":4, "rrac":-4, "tz":0, "zs":1026, "zsh":4, "zsl":2,

rob0101 commented 1 year ago

I'm also seeing these for Zappi:

batteryDischargeEnabled: 0 beingTamperedWith : 0 newAppAvailable : 0 newBootloaderAvailable : 0 rdc : 1

HLFCode commented 2 months ago

Is cgi-jstatus-Z still showing the extended data like these shown in the doc?

        "ectp4": 2143,      //Physical CT connection 4 value Watts
        "ectp5": 2143,      //Physical CT connection 5 value Watts
        "ectp6": 2143,      //Physical CT connection 6 value Watts

When I call cgi-jstatus-Z I get the same contents as the zappi part of cgi-jstatus-*

My Zappi has the option for 3 "user" CTs plus the internal one. I can't see how to read the h/w CT3 in the api even though it is showing a valid power on the zappi h/w. (Note there's a mismatch between the api and the Zappi h/w, in the api CT1 is called "Internal Load" but in the Zappi h/w CT1 is a user CT)