custom file for eMylo 3-Phase Smart Wifi Energy Meter

[dnwalker68]

Hello everyone,
unfortunately I have absolutely no idea in this area. I read the documentation on how to write such a file, but I didn't really understand it. So don't kill me if I ask a stupid question.

I have a Make eMylo smart meter here. However, it is not the 1-phase device that is already in the device database but a 3-phase device. Here is a link to the device on Amazon.

https://www.amazon.de/dp/B0D4DT8V37?tag=operapc-def-sp-co2-de-21

Here is an excerpt of the data from the Tuya Developer Tool

`ResponseCopy
{
"result": [
{
"active_time": 1726762981,
"bind_space_id": "61381298",
"category": "dlq",
"create_time": 1726762981,
"custom_name": "",
"icon": "smart/icon/ay1553162414592ZG6Kk/ed250f82f5259b55a100ffa430d9ef49.png",
"id": "bf7ad3617f2502b02foktb",
"ip": "xxx.xxx.xxx.xxx",
"is_online": true,
"lat": "51.01",
"local_key": "xxxxxxxxxxxx",
"lon": "6.89",
"model": "",
"name": "Metering_3PN_WiFi",
"product_id": "fzxonzodwjiugioz",
"product_name": "SDM01_WiFi+485_V1",
"sub": false,
"time_zone": "+02:00",
"update_time": 1726762984,
"uuid": "d35dcc51f1f47a5e"
}
],
"success": true,
"t": 1726764507945,
"tid": "fe89f5ca76a611ef88b02ac421ecbce6"
}

######################################################################

{
"result": {
"properties": [
{
"code": "forward_energy_total",
"custom_name": "",
"dp_id": 1,
"time": 1726763247371,
"type": "value",
"value": 30
},
{
"code": "phase_a",
"custom_name": "",
"dp_id": 6,
"time": 1726764314860,
"type": "raw",
"value": "CQUAAAAAAAA="
},
{
"code": "phase_b",
"custom_name": "",
"dp_id": 7,
"time": 1726764315103,
"type": "raw",
"value": "CQkAAAAAAAA="
},
{
"code": "phase_c",
"custom_name": "",
"dp_id": 8,
"time": 1726764315232,
"type": "raw",
"value": "CQMAAAAAAAA="
},
{
"code": "fault",
"custom_name": "",
"dp_id": 9,
"time": 1726763247371,
"type": "bitmap",
"value": 0
},
{
"code": "clear_energy",
"custom_name": "",
"dp_id": 12,
"time": 1726763325450,
"type": "bool",
"value": true
},
{
"code": "alarm_set_1",
"custom_name": "",
"dp_id": 17,
"time": 1726763342221,
"type": "raw",
"value": "BwAAGQ=="
},
{
"code": "alarm_set_2",
"custom_name": "",
"dp_id": 18,
"time": 1726763342315,
"type": "raw",
"value": "AQAAZAIBAA8DAQD9BAAAtAUAAAAHAQAA"
},
{
"code": "breaker_id",
"custom_name": "",
"dp_id": 19,
"time": 1726763325714,
"type": "string",
"value": "fzx24010001"
},
{
"code": "reverse_energy_total",
"custom_name": "",
"dp_id": 23,
"time": 1726763325131,
"type": "value",
"value": 0
},
{
"code": "active_power",
"custom_name": "",
"dp_id": 29,
"time": 1726763743826,
"type": "value",
"value": 0
},
{
"code": "supply_frequency",
"custom_name": "",
"dp_id": 32,
"time": 1726764315274,
"type": "value",
"value": 5001
},
{
"code": "online_state",
"custom_name": "",
"dp_id": 35,
"time": 1726762980993,
"type": "enum",
"value": "online"
},
{
"code": "power_factor",
"custom_name": "",
"dp_id": 50,
"time": 1726763325435,
"type": "value",
"value": 99
},
{
"code": "device_locating",
"custom_name": "",
"dp_id": 101,
"time": 1726763325466,
"type": "bool",
"value": false
},
{
"code": "data_report_duration",
"custom_name": "",
"dp_id": 102,
"time": 1726763325479,
"type": "value",
"value": 15
},
{
"code": "cur_voltage_x",
"custom_name": "",
"dp_id": 103,
"time": 1726764315290,
"type": "value",
"value": 2309
},
{
"code": "cur_current_x",
"custom_name": "",
"dp_id": 104,
"time": 1726764315305,
"type": "value",
"value": 0
},
{
"code": "cur_power_x",
"custom_name": "",
"dp_id": 105,
"time": 1726764315326,
"type": "value",
"value": 0
},
{
"code": "power_factor_x",
"custom_name": "",
"dp_id": 108,
"time": 1726764315449,
"type": "value",
"value": 99
},
{
"code": "x_total_import_energy",
"custom_name": "",
"dp_id": 109,
"time": 1726764315492,
"type": "value",
"value": 10
},
{
"code": "x_total_export_energy",
"custom_name": "",
"dp_id": 110,
"time": 1726764318186,
"type": "value",
"value": 0
},
{
"code": "cur_voltage_y",
"custom_name": "",
"dp_id": 112,
"time": 1726764315328,
"type": "value",
"value": 2313
},
{
"code": "cur_current_y",
"custom_name": "",
"dp_id": 113,
"time": 1726764315338,
"type": "value",
"value": 0
},
{
"code": "cur_power_y",
"custom_name": "",
"dp_id": 114,
"time": 1726764315394,
"type": "value",
"value": 0
},
{
"code": "power_factor_y",
"custom_name": "",
"dp_id": 117,
"time": 1726764315465,
"type": "value",
"value": 99
},
{
"code": "y_total_import_energy",
"custom_name": "",
"dp_id": 118,
"time": 1726764315567,
"type": "value",
"value": 10
},
{
"code": "y_total_export_energy",
"custom_name": "",
"dp_id": 119,
"time": 1726764315583,
"type": "value",
"value": 0
},
{
"code": "cur_voltage_z",
"custom_name": "",
"dp_id": 121,
"time": 1726764315409,
"type": "value",
"value": 2307
},
{
"code": "cur_current_z",
"custom_name": "",
"dp_id": 122,
"time": 1726764315421,
"type": "value",
"value": 0
},
{
"code": "cur_power_z",
"custom_name": "",
"dp_id": 123,
"time": 1726764315436,
"type": "value",
"value": 0
},
{
"code": "power_factor_z",
"custom_name": "",
"dp_id": 126,
"time": 1726764315478,
"type": "value",
"value": 99
},
{
"code": "z_total_import_energy",
"custom_name": "",
"dp_id": 127,
"time": 1726764315593,
"type": "value",
"value": 10
},
{
"code": "z_total_export_energy",
"custom_name": "",
"dp_id": 128,
"time": 1726764315611,
"type": "value",
"value": 0
},
{
"code": "current_unbalance",
"custom_name": "",
"dp_id": 130,
"time": 1726764315622,
"type": "value",
"value": 0
},
{
"code": "rs485_address",
"custom_name": "",
"dp_id": 131,
"time": 1726763325520,
"type": "value",
"value": 247
},
{
"code": "rs485_baut_rate",
"custom_name": "",
"dp_id": 132,
"time": 1726763325536,
"type": "enum",
"value": "9600"
},
{
"code": "rs485_data_format",
"custom_name": "",
"dp_id": 133,
"time": 1726763325550,
"type": "enum",
"value": "N81"
}
]
},
"success": true,
"t": 1726764318959,
"tid": "8de7f36a76a611efb77736033862a1ba"
}
`

I've now tried to create a config file.

F_Tuya_Local_Metering_3PN_WiFi.yaml.pdf

Now when I try to install the device under HomeAssistant I get the following error in the log

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: custom_components.tuya_local.helpers.device_config
Quelle: custom_components/tuya_local/helpers/device_config.py:998
Integration: Tuya Local (Dokumentation, Probleme)
Erstmals aufgetreten: 17:50:44 (1 Vorkommnisse)
Zuletzt protokolliert: 17:50:44

Parse error in Metering_3PN_WiFi.yaml

So there is an error somewhere in the file. Unfortunately I can't get any further now. It would be nice if you could help me here.
Please excuse my bad English.

Thank you and best regards

[dnwalker68]

Yes, it's a shame that no one can help...

[make-all]

I think very few people have the time to spend playing spot the syntax error in a PDF printout of someone else's YAML config.

I suggest pasting your code into a validator such as https://yamlchecker.com/

[dnwalker68]

I have already run my code through various code checkers and no errors are displayed. I've already come up with the idea.

[dnwalker68]

Even when I try, I get the error message "Parse error in meter1.yaml"

`name: eMylo meter
products:

• id: fzxonzodwjiugioz
  name: Metering-3PN-WiFi
  primary_entity:
  entity: sensor
  class: energy
  dps:
  • id: 1
    type: value
    name: sensor
    unit: kWh
    class: total_increasing
  • id: 6
    type: raw
    name: phase_a
    optional: true
    force: true
  • id: 7
    type: raw
    name: phase_b
    optional: true
    force: true
  • id: 8
    type: raw
    name: phase_c
    optional: true
    force: true
    secondary_entities:
• entity: sensor
  name: Current A
  class: current
  category: diagnostic
  dps:
  • id: 104
    type: value
    name: sensor
    unit: kW
    class: measurement
• entity: sensor
  name: Current B
  class: current
  category: diagnostic
  dps:
  • id: 113
    type: value
    name: sensor
    unit: kW
    class: measurement
• entity: sensor
  name: Current C
  class: current
  category: diagnostic
  dps:
  • id: 122
    type: value
    name: sensor
    unit: kW
    class: measurement
• entity: sensor
  name: Voltage A
  class: voltage
  category: diagnostic
  dps:
  • id: 103
    type: value
    name: sensor
    unit: V
• entity: sensor
  name: Voltage B
  class: voltage
  category: diagnostic
  dps:
  • id: 112
    type: value
    name: sensor
    unit: V
• entity: sensor
  name: Voltage C
  class: voltage
  category: diagnostic
  dps:
  • id: 121
    type: value
    name: sensor
    unit: V
• entity: sensor
  name: Power A
  class: power
  category: diagnostic
  dps:
  • id: 105
    type: value
    name: sensor
    unit: kW
• entity: sensor
  name: Power B
  class: power
  category: diagnostic
  dps:
  • id: 114
    type: value
    name: sensor
    unit: kW
• entity: sensor
  name: Power C
  class: power
  category: diagnostic
  dps:
  • id: 123
    type: value
    name: sensor
    unit: kW
• entity: sensor
  name: Total power
  class: power
  category: diagnostic
  dps:
  • id: 29
    type: value
    name: sensor
    unit: kW
    class: measurement
• entity: button
  name: Clear_Energy
  category: config
  class: restart
  dps:
  • id: 12
    type: boolean
    name: button
    optional: true`

[dnwalker68]

Here I have the file again as a zip
meter1.zip

[make-all]

"raw" and "value" are not valid types.

[dnwalker]

Thanks for the help...yes, I should read carefully.
Now I created a new file and ran it through a checker. In terms of syntax, there shouldn't be a problem, but now the file is perceived as not matching when installing the device and the file from qoto_03_sprinkler is offered with a match of 16% for the device. My file is not offered in the selection. What am I doing wrong again? It would be great if you could help me further here. Here is the new file...

`name: Metering_3PN_WiFi
products:

• id: fzxonzodwjiugioz
  name: SDM01_WiFi+485_V1
  primary_entity:
  entity: sensor
  name: Total energy
  class: energy
  dps:
  • id: 1
    type: integer
    name: sensor
    unit: kWh
    class: total_increasing
    mapping:
    • scale: 100

secondary_entities:

• entity: sensor
  name: phase_a_total_import_energy
  class: energy
  dps:

  • id: 109
    type: integer
    unit: kWh
    mapping:
    • scale: 100

• entity: sensor
  name: phase_b_total_import_energy
  class: energy
  dps:

  • id: 118
    type: integer
    unit: kWh
    mapping:
    • scale: 100

• entity: sensor
  name: phase_c_total_import_energy
  class: energy
  dps:

  • id: 127
    type: integer
    unit: kWh
    mapping:
    • scale: 100

• entity: sensor
  name: active_power
  class: power
  category: diagnostic
  dps:

  • id: 29
    type: integer
    name: sensor
    unit: kW
    class: measurement

• entity: sensor
  name: current a
  class: current
  category: diagnostic
  dps:

  • id: 104
    type: base64
    name: sensor
    optional: true
    unit: A
    mapping:
    • mask: "0000FFFFFF000000"
      scale: 1000

• entity: sensor
  name: current b
  class: current
  category: diagnostic
  dps:

  • id: 113
    type: base64
    name: sensor
    optional: true
    unit: A
    mapping:
    • mask: "0000FFFFFF000000"
      scale: 1000

• entity: sensor
  name: current c
  class: current
  category: diagnostic
  dps:

  • id: 122
    type: base64
    name: sensor
    optional: true
    unit: A
    mapping:
    • mask: "0000FFFFFF000000"
      scale: 1000

• entity: sensor
  name: voltage a
  class: voltage
  category: diagnostic
  dps:

  • id: 103
    type: base64
    name: sensor
    optional: true
    unit: V
    mapping:
    • mask: "FFFF000000000000"
      scale: 10

• entity: sensor
  name: Voltage B
  class: voltage
  category: diagnostic
  dps:

  • id: 112
    type: base64
    name: sensor
    optional: true
    unit: V
    mapping:
    • mask: "FFFF000000000000"
      scale: 10

• entity: sensor
  name: Voltage C
  class: voltage
  category: diagnostic
  dps:

  • id: 121
    type: base64
    name: sensor
    optional: true
    unit: V
    mapping:
    • mask: "FFFF000000000000"
      scale: 10

• entity: sensor
  name: Power A
  class: power
  category: diagnostic
  dps:

  • id: 105
    type: base64
    name: sensor
    optional: true
    unit: kW
    mapping:
    • mask: "0000000000FFFFFF"
      scale: 1000

• entity: sensor
  name: Power B
  class: power
  category: diagnostic
  dps:

  • id: 114
    type: base64
    name: sensor
    optional: true
    unit: kW
    mapping:
    • mask: "0000000000FFFFFF"
      scale: 1000

• entity: sensor
  name: Power C
  class: power
  category: diagnostic
  dps:

  • id: 123
    type: base64
    name: sensor
    optional: true
    unit: kW
    mapping:
    • mask: "0000000000FFFFFF"
      scale: 1000

• entity: sensor
  name: Energy import A
  class: energy
  category: diagnostic
  dps:

  • id: 109
    type: integer
    name: sensor
    unit: kWh
    class: total_increasing
    mapping:
    • scale: 100

• entity: sensor
  name: Energy import B
  class: energy
  category: diagnostic
  dps:

  • id: 118
    type: integer
    name: sensor
    unit: kWh
    class: total_increasing
    mapping:
    • scale: 100

• entity: sensor
  name: Energy import C
  class: energy
  category: diagnostic
  dps:

  • id: 127
    type: integer
    name: sensor
    unit: kWh
    class: total_increasing
    mapping:
    • scale: 100

• entity: sensor
  name: Energy export A
  class: energy
  category: diagnostic
  dps:

  • id: 110
    type: integer
    name: sensor
    unit: kWh
    class: total_increasing
    mapping:
    • scale: 100

• entity: sensor
  name: Energy export B
  class: energy
  category: diagnostic
  dps:

  • id: 119
    type: integer
    name: sensor
    unit: kWh
    class: total_increasing
    mapping:
    • scale: 100

• entity: sensor
  name: Energy export C
  class: energy
  category: diagnostic
  dps:

  • id: 128
    type: integer
    name: sensor
    unit: kWh
    class: total_increasing
    mapping:
    • scale: 100

• entity: button
  name: Clear_Energy
  category: config
  class: restart
  dps:

  • id: 12
    type: boolean
    name: button
    optional: true
    `

[dnwalker]

and as zip file...
Metering_3PN_WiFi.zip