GithubHelp home page GithubHelp logo

diginrg_esphome's People

Contributors

digiblur avatar kozoke avatar redwngsrul avatar shampeon avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

diginrg_esphome's Issues

Realy leaking current

Anyone else experiencing leakage with the Wyze Outdoor Plug ?

Maybe nothing we can do and this is hardware but when I plug a LED controller, it always stays ON.

Anyone measured the leaking current of the relays ?

`gain_voltage` values are too high for the 2 channel monitor sample YAML

The example for the 2 channel monitor and the 100A/50ma CTs uses this setting:

gain_voltage: 32428

This results in a voltage reading of 655V for my setup in the US (split phase 240V at 60Hz), throwing all the wattage calculations off by a large margin.

Setting gain_voltage to 3900 results in a much more sane voltage output of 120.

Incorrect gain_pga settings in yaml example for using ct clamps over 65A

According to CiricuitSetup's Github

The max value for current that the meter can output is 65.535. If you expect to measure current over 65A,
divide the gain_ct by 2 (120A CT) or 4 (200A CT) and multiply the current and power values by 2 or 4 by uncommenting the filter below

So for measuring and using CT clamps over 65A, gain_pga should be 1X and an additional x2 multiplier is needed under the current sensor to produce a correct reading.

Add to the Readme for Home Assistant

For ease of use for others you may want to edit your readme and add that the following attributes are needed to integrate this into HA new Energy.

state_class: measurement
device_class: energy
last_reset: 1970-01-01T00:00:00+00:00

Check in developers tools and look for the new sensor. If it does not have the three attributes you need to add them in the customize.yaml (if you have this file)
Mine customized section for this sensor is:

sensor.jcpl_house_kwh:
  last_reset: '1970-01-01T00:00:00+00:00'
  state_class: measurement
  device_class: energy

Feature Request: Sensor Data from Both Chips to Publish at the Same Time.

Firstly, thanks for this implemetation, which I've now been using for a couple of months.

However, I have one remaining issue, which is proving a real pain to resolve.
I have a sensor which is calculated by subtracting one clamp from another.
Unfortunately the clamps in question are on different chips of the board, which don't update at the same time.
This means that it's possible for the calculated sensor to be a negative value. Hopefully the below screen grab from Grafana will clearly show the issue.

image

Total (CT1) = Incoming cable from the grid
Ground & 1st Floors (CT6) = Cable into primary fuse board
2nd Floor (calculated) = Should be what my separate fuse board, for the 2nd floor, is consuming. Total - Ground & 1st Floors.

I don't have a spare channel (using all 6) to actually clamp on to the cable into the secondary fuse board, which services the second floor.

Is there any way to ensure sensors on both channels/chips publish at the same time please?

Many thanks.

digi_nrg_6chan32 has no access to power factor or reactive power

It seems that while the splitcore implimentation of atm90e32as impliments power factor and reactive power for each phase, these are not available on the 6 channel version. My understanding is they both utilise the same chip (atm90e32as) and hense both reference the same registers over spi, but for some reason the registers are not available on the 6 channel version?

Ive included a log printout from esphome along with the added lines of code to include the reactive power and power factor into the yaml;

`sensor:

  • platform: wifi_signal
    name: ${disp_name} WiFi
    update_interval: 60s
  • platform: atm90e32
    cs_pin: 5
    phase_a:
    reactive_power:
    name: ${disp_name} Reactive Power
    id: ic1ReactivePower
    power_factor:
    name: ${disp_name} Power Factor
    id: ic1PowerFactor

    voltage:
    name: ${disp_name} Volts A
    id: ic1Volts
    accuracy_decimals: 1
    current:
    name: ${disp_name} CT1 Amps
    id: ct1Amps
    gain_voltage: 27845

Voltage using a 9VAC power transformer

Note: If you can not get the voltage correct with the highest gain of 65535, uncomment the 2.0 multiply filter above and lower the gain as needed

  gain_ct: 25753`

`INFO Reading configuration /config/esphome/mcu_powermeter.yaml...
INFO Detected timezone 'AEDT' with UTC offset 11
INFO Generating C++ source...
INFO Compiling app...
INFO Running: platformio run -d /config/esphome/mcu_powermeter
Processing mcu_powermeter (board: nodemcu-32s; framework: arduino; platform: [email protected])

HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
Dependency Graph
|-- 1.1.1
|-- 1.0
| |-- 1.0
|-- 1.0
|-- 1.2.6
| |-- 1.1.1
| |-- 1.0
| |-- 1.0
| |-- 5.13.3
|-- 5.13.3
|-- 1.0
|-- 1.0
|-- 1.0
Compiling /data/mcu_powermeter/.pioenvs/mcu_powermeter/src/main.cpp.o
Archiving /data/mcu_powermeter/.pioenvs/mcu_powermeter/lib715/libAsyncTCP-esphome_ID6798.a
Compiling /data/mcu_powermeter/.pioenvs/mcu_powermeter/lib789/WiFi/WiFiClient.cpp.o
Compiling /data/mcu_powermeter/.pioenvs/mcu_powermeter/lib789/WiFi/WiFiGeneric.cpp.o
Compiling /data/mcu_powermeter/.pioenvs/mcu_powermeter/lib789/WiFi/WiFiMulti.cpp.o
Compiling /data/mcu_powermeter/.pioenvs/mcu_powermeter/lib789/WiFi/WiFiSTA.cpp.o
src/main.cpp: In function 'void setup()':
src/main.cpp:597:31: error: 'class esphome::atm90e32::ATM90E32Component' has no member named 'set_react_pow_sensor'
atm90e32_atm90e32component->set_react_pow_sensor(0, ic1ReactivePower);
^
src/main.cpp:609:31: error: 'class esphome::atm90e32::ATM90E32Component' has no member named 'set_pf_sensor'
atm90e32_atm90e32component->set_pf_sensor(0, ic1PowerFactor);
^
Compiling /data/mcu_powermeter/.pioenvs/mcu_powermeter/lib789/WiFi/WiFiScan.cpp.o
Compiling /data/mcu_powermeter/.pioenvs/mcu_powermeter/lib789/WiFi/WiFiServer.cpp.o
*** [/data/mcu_powermeter/.pioenvs/mcu_powermeter/src/main.cpp.o] Error 1
========================== [FAILED] Took 5.88 seconds ==========================`

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.