Feature request: include current in amps (in addition to watts) #273
Comments
|
can you describe your setup? and service?
ty
…On Thu, Apr 11, 2024 at 3:28 PM cmegalodon ***@***.***> wrote:
I noticed that the integration provides 1MIN power in watts, but in the
Emporia website it's possible to switch to amps.
My specific use case is monitoring power from a generator, and it's
important to know the current on each leg (since the house is an unbalanced
load).
—
Reply to this email directly, view it on GitHub
<#273>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGBTIUYJQG6RGNEFCVXLS2DY43P55AVCNFSM6AAAAABGC4EP7OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTQNBRGM3DMMY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Yes, I'm in Canada, using 120V split phase power (+120 and -120, same as the U.S.). I've got a 12kW standby generator which is rated at 50 amps (120V/50A each leg). The Emporia integration provides total power in watts, but in reality the generator will trip its breaker if either leg exceeds 6kW. In the Emporia app it's possible to "switch units" and see the amps on each leg (currently 12.8 amps and 20.5 amps on each leg, but about 3.8 kW). In the app it's reported as "Total Usage_A" and "Total Usage_B". I'd like to set up Home Assistant to trigger an alert if either leg exceeds a certain current (say, 40 amps). |
|
it shows you two amperages off main cts? or you have individual circuit
cts on gen?
…On Thu, Apr 11, 2024 at 3:47 PM cmegalodon ***@***.***> wrote:
Yes, I'm in Canada, using 120V split phase power (+120 and -120, same as
the U.S.). I've got a 12kW standby generator which is rated at 50 amps
(120V/50A each leg). The Emporia integration provides total power in watts,
but in reality the generator will trip its breaker if either leg exceeds
6kW.
In the Emporia app it's possible to "switch units" and see the amps on
each leg (currently 12.8 amps and 20.5 amps on each leg, but about 3.8 kW).
In the app it's reported as "Total Usage_A" and "Total Usage_B".
I'd like to set up Home Assistant to trigger an alert if either leg
exceeds a certain current (say, 40 amps).
—
Reply to this email directly, view it on GitHub
<#273 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGBTIU24FFAGEP352A6M42LY43SFTAVCNFSM6AAAAABGC4EP7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJQGQYDMMZUGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Yes, it shows me the amps off of the main CTs
Here's the two views in the app to see. Ignore L1+L2, those are additional CTs. |
|
Ill be damned it shares a/b data that way let me pull it on api. will
check after watching golf :)
Valid use case / way to get data imho.
Someone else asked something similar awhile ago..
…On Thu, Apr 11, 2024 at 3:53 PM Daniel Drury ***@***.***> wrote:
it shows you two amperages off main cts? or you have individual circuit
cts on gen?
On Thu, Apr 11, 2024 at 3:47 PM cmegalodon ***@***.***>
wrote:
> Yes, I'm in Canada, using 120V split phase power (+120 and -120, same as
> the U.S.). I've got a 12kW standby generator which is rated at 50 amps
> (120V/50A each leg). The Emporia integration provides total power in watts,
> but in reality the generator will trip its breaker if either leg exceeds
> 6kW.
>
> In the Emporia app it's possible to "switch units" and see the amps on
> each leg (currently 12.8 amps and 20.5 amps on each leg, but about 3.8 kW).
> In the app it's reported as "Total Usage_A" and "Total Usage_B".
>
> I'd like to set up Home Assistant to trigger an alert if either leg
> exceeds a certain current (say, 40 amps).
>
> —
> Reply to this email directly, view it on GitHub
> <#273 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BGBTIU24FFAGEP352A6M42LY43SFTAVCNFSM6AAAAABGC4EP7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJQGQYDMMZUGQ>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
|
It's the only part of the app that shows it, you can't graph the amps. If the Emporia API can exposes it, I think it would be a great addition. Thank you for being so responsive :) |
|
Using units of AmpHours gives the following output. This data is useful for certain applications to see the load on A and B power feeds. (Both sides of the center tap transformer in US). I believe this is the only way you can retrieve the readings of both CTs on the mains. { |
|
Yeah it's definitely possible, there's another issue out there I think for this request. On my list of things to do but haven't gotten to it yet. Really this is only helpful for the Vue device, not channels or plugs, so to keep noise down I'd probably only add the different phases to whatever vues are on the account. |
|
Agree, it's a shame that the getdeviceusages with kw doesn't give watts of these two cts independantly. Not sure if every user would want/need this. Think it is more of a data point for those with generator backup. Seems like a lot of requests and data to basically get 2 data points. |
|
Its just these two data points, its a shame they don't come through with the power request.. Been looking at code, annoying from that side of it.. { |
|
Just want to let you know that I added a VUE Gen3 and this HA integration worked perfectly. |
|
I didn't forget about you.. still thinking about you... its just somewhat annoying this doesn't come through on the kw feed, as we are under requests per day request from emporia for the code here. |
its more the amps for phase a and b on the main cts that this topic is about. The rest if you really care you can math with template yourself in ha if you really care... volts doesn't come across at all in the api btw. :) |
|
Thanks for the updates! I really appreciate everything you are doing for the HA community! |
I noticed that the integration provides 1MIN power in watts, but in the Emporia website it's possible to switch to amps.
My specific use case is monitoring power from a generator, and it's important to know the current on each leg (since the house is an unbalanced load).
The text was updated successfully, but these errors were encountered: