-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 - dual power metering #6160
Comments
How about this:
|
Very nice, thanks! Is it possible to get the energy totals per channel as well or does the device only track the combined total? |
* Change energy sensors for three phase/channel support * Add Shelly 2.5 energy dual channel support (#6160)
For now with consolidated Energy totals. |
Nice! Looking forward to it with the Shelly EM as well (same power chip) |
Did you try Shelly EM with template of Shelly 2.5?
|
I haven't yet but definitely bumping it up in my list for this week to test. |
How does Domoticz handle JSON "arrays"? In this
I'm having trouble setting up a JSON function to return a separate value for each channel of any particular metric. For example, I grasp how I would do it if it were formatted like Your insights much appreciated ;-) Mike |
I haven't tested rules using a JSON list but if it doesn't work I/someone have/has to find a solution. |
When you get around to testing this, can you see if HA can extract the individual values from the JSON payload? Otherwise, @arendst, might I suggest this Mike |
Nice suggestion but it takes too much space. When three phase devices are used it needs three value pairs for each power, voltage and current item. This makes the JSON string too long for both MQTT response and rule/script handling. JSON lists are handled succesfully in other tools so I guess we have to find a way to make it work with rules too. |
Time for the Rules/Scripting caped crusaders (@ascillato @laurentdong @gemu2015) to come to the rescue 😉 |
Quick test with
No idea how to filter the values with rules. |
Jsonpath can use index too. |
should already work in scripter e.g. var=ENERGY#Power[1] |
So what we miss is handling with normal rules? |
So cut (scripter) and paste (rule) should solve it. |
Yeah, stupid me used [1] and [2]. I thought it was unsupported syntax in OH when it was PEBCAK! |
Looks nice :) Small improvement: I would suggest to add the unit in the UI after every value, not just at the end, but maybe that's a matter of taste. To seperate the energy as suggested by @KaiserSoft would be very nice to :) |
Add JSON array index support to rules evaluation allowing trigger on ENERGY#POWER[2]>0.60 from JSON ..,"Power":[0.00,0.68],.. (#6160)
Closing this issue as the feature has been added. Thanks :) |
I know this issue is already closed, but I'm looking for a similar thing that is having Totals also split. |
Any way we can get a split total? |
What about the Split of the Totals. This is also needed for the Shelly EM and Shelly EM3 if you will be able to count the imports and exports separately ... |
Splitted totals added to Tasmota by Theo. |
I stumbled upon this: https://shelly.cloud/shelly-25-wifi-smart-relay-roller-shutter-home-automation/
"DUAL POWER METERING
Shelly 2.5 has two integrated precise power meters. You can measure the consumption for each channel separately."
With Tasmota it only shows one power metering (which seems to be a sum of both outputs?).
It would be nice if Tasmota supports both measurings seperately.
The text was updated successfully, but these errors were encountered: