The Wayback Machine - https://web.archive.org/web/20201129152451/https://github.com/arendst/Tasmota/pull/9166
Skip to content
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

Shelly 2.5 separate power measuring #9166

Open
wants to merge 2 commits into
base: development
from

Conversation

@cskarai
Copy link

@cskarai cskarai commented Aug 26, 2020

Hi Tasmota developers,

Tasmota doesn't support separate channel measuring for Shelly 2.5.
The problem is difficult, so this pull request is rather a patch for those who want to measure the channels separately.

Limitations:

  • EnergyReset1-3 equally splits the value amongst the channels
  • Only the webserver displays separate measurement data, MQTT, Domoticz are not covered
  • It measures only Shelly 2.5 separately, the other 3-phase products are not supported (yet)
  • Structural change in RtcSettings (backwards incompatibility)

I think, that in the long term separate power measuring for dual channel products is important. While it's not done, this temporary patch might handle the problem.

shelly2 5

Sync
@cskarai cskarai force-pushed the cskarai:shelly2.5 branch 2 times, most recently from 403688f to f4ffbee Aug 26, 2020
@cskarai cskarai force-pushed the cskarai:shelly2.5 branch from f4ffbee to 6c315e7 Aug 26, 2020
@sfromis
Copy link

@sfromis sfromis commented Aug 27, 2020

Nice. Without MQTT support, I'd say that the value of this is, well, limited.

@cskarai
Copy link
Author

@cskarai cskarai commented Aug 29, 2020

Nice. Without MQTT support, I'd say that the value of this is, well, limited.

I don't have millions of time to develop software that I will never use.
If the developers are open to merge this feature, then I can work a bit more on this pull request.

If you need this patch, I can continue the development, but I won't be angry if you reject this PR, as it's not suitable for the current code base.

@arendst
Copy link
Owner

@arendst arendst commented Oct 3, 2020

Currently uses too many resources for too little profit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.