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

Trying to integrate Tasmota BitShake SmartMeterReader #134

Open
mircsicz opened this issue Jul 31, 2023 · 0 comments
Open

Trying to integrate Tasmota BitShake SmartMeterReader #134

mircsicz opened this issue Jul 31, 2023 · 0 comments

Comments

@mircsicz
Copy link

mircsicz commented Jul 31, 2023

Hi hi,

I've successfully integrated my Gosund SP112 using your SP111 template.

My next target is to integrate my Utility-Meter

The MQTT Telegram looks like this:

{"Time":"2023-07-31T16:11:20","":{"Power_curr":1757,"total_in":28125.25}}

compared to the one of a SP112:

{"Time":"2023-07-31T15:13:14","ENERGY":{"TotalStartTime":"2023-07-13T12:07:17","Total":16.548,"Yesterday":0.682,"Today":0.492,"Period":6,"Power":67,"ApparentPower":140,"ReactivePower":123,"Factor":0.48,"Voltage":217,"Current":0.645}}

My main finding so far is that ENERGY in the field before the metric is missing...

Here's how I've tried to set it up:

mqtt:
  topic_path: tele/AMR/AMR_OVAG/SENSOR
  device_id_regex: "tele/AMR/(?P<deviceid>.*)/SENSOR"
  qos: 0
cache:
  timeout 24h
metrics:
  - prom_name: consumed_energy_kilowatthours_total
    mqtt_name: "total_in"
    help: "Total read kilowatthours"
    type: counter
  - prom_name: power_watts
    mqtt_name: "Power_curr"
    help: "Currently read power"
    type: gauge

But I don't see none of my two relevant values...

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

No branches or pull requests

1 participant