New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Control of the Output wattage (API/MQTT/Webhooks) #25
Comments
Apparently you can set the "outputLimit" via MQTT. In the MQTT Explorer I have seen the following under: xxxxxxxx/sensor/device/yyyyyyyoutputLimit/config { I just can't get a flow built in NodeRed to set the value with. But I´am also new to the topic. |
Has anyone tried this option ? To me this is feature is a deal breaker - would I buy this product or not. I am monitoring use of my electricity with Shelly3em(two of them), so I know what is the usage of my electricity. Having an option to control the output of SF would basically compensate the usage(on 3 phases). If we could control this inside of our LAN would be even better, without using cloud MQTT. |
Hi Robert, I also use a Shelly pro 3EM and want to achieve the same. The API of Zendure seems to be readonly and a direct way to the device is not known at the moment. But I would also be happy if it goes through the cloud MQTT server. Especially since I only use Solar Flow in my guest wifi, because the box probably can not log into a WPA3/WPA2 Fritz.Box wifi because of missing PMF support. I already have a ticket at Zendure. It must go via MQTT, when I played around yesterday, I managed with a syntax to set the outputLimit to 0W. Unfortunately I don't know enough about JSON and MQTT to develop this without help. |
When is this working? This is the most essential feature—still nothing. |
Does someone have one of these satellite plugs?? |
Still no update. When does Zendure add at least an REST api to the device for direct communication? |
Any news? thanks |
Output wattage control (battery charge&inverter output)
webhooks:
Shelly 3EM power meter
…
mqtt:
nodered
…
api:
etc.
The text was updated successfully, but these errors were encountered: