Intégration micro-onduleur StepupTech SPD800 via tuya-local : récupérer les données depuis iot tuya?

Mariolhand2 · Avril 22, 2025, 4:02

Salut Mateo,

Vu que tu as réussi, peux tu m’aider stp, moi je bloque toujours apres l’etape d’integration de tuya local…
Merci !

Mateo · Avril 22, 2025, 7:27

J’ai commencé à me faire un tutoriel ici en partant de zéro vu que je débute aussi

J’espère que cela t’aidera

saglagla · Mars 3, 2026, 2:48

Hello à tous,

Le mainteneur de Tuya Local refuse mon correctif …

github.com/make-all/tuya-local

stepuptech_solar_inverter_v2 : wrong scale for kwh unit production

ouvert 10:15AM - 19 Jan 26 UTC

fermé 10:20AM - 19 Jan 26 UTC

samsam-rolon

### Description Hello, My stepuptech_solar_inverter_v2 produce more than I see… in the HA dashboard. There is a x100 factor between information in Tuya and Tuya Local Integration. I've edit the YAML file to make it works correctly. ### Steps to reproduce _No response_ ### Expected behaviour ``` yaml name: Solar inverter products: - id: 2zkyfrpmfxmex896 manufacturer: Stepuptech model: SPD-800 entities: - entity: sensor class: energy dps: - id: 108 type: integer name: sensor unit: Wh class: total_increasing mapping: - scale: 1 - id: 10 type: integer optional: true # labelled total, but range is much smaller than above name: daily mapping: - scale: 100 - id: 103 type: integer optional: true name: product_category - id: 106 type: string optional: true name: market - id: 111 type: string optional: true name: meter_id - id: 112 type: string optional: true name: model - entity: sensor class: voltage dps: - id: 101 type: integer optional: true name: sensor class: measurement unit: V mapping: - scale: 100 - entity: sensor name: PV1 voltage class: voltage category: diagnostic dps: - id: 114 type: integer name: sensor unit: V mapping: - scale: 100 - entity: sensor class: current dps: - id: 102 type: integer optional: true name: sensor unit: A class: measurement mapping: - scale: 100 - entity: sensor name: PV1 current class: current category: diagnostic dps: - id: 115 type: integer name: sensor unit: A mapping: - scale: 100 - entity: sensor class: frequency category: diagnostic dps: - id: 116 type: integer name: sensor unit: Hz class: measurement - entity: sensor name: PV2 voltage class: voltage category: diagnostic dps: - id: 117 type: integer name: sensor unit: V mapping: - scale: 100 - entity: sensor name: PV2 current class: current category: diagnostic dps: - id: 118 type: integer name: sensor unit: A mapping: - scale: 100 - entity: sensor class: temperature dps: - id: 107 type: integer name: sensor class: measurement - id: 113 type: string optional: true name: unit mapping: - dps_val: fahrenheit_degree value: F - value: C - entity: sensor name: AC voltage class: voltage category: diagnostic dps: - id: 104 type: integer name: sensor unit: V mapping: - scale: 100 - entity: sensor name: AC current class: current category: diagnostic dps: - id: 105 type: integer name: sensor unit: A mapping: - scale: 100 - entity: switch name: Inverter switch category: config dps: - id: 6 type: boolean name: switch optional: true - entity: binary_sensor class: problem category: diagnostic dps: - id: 7 type: bitfield optional: true name: sensor mapping: - dps_val: 0 value: false - value: true - id: 7 type: bitfield optional: true name: fault_code - entity: select translation_key: temperature_unit category: config dps: - id: 113 type: string optional: true name: option mapping: - dps_val: centigrade value: celsius - dps_val: fahrenheit_degree value: fahrenheit - entity: select translation_key: currency category: config dps: - id: 109 type: string optional: true name: option mapping: - dps_val: Euro value: eur - dps_val: USD value: usd - dps_val: RMB value: cny - entity: text name: Cost per kWh category: config class: monetary dps: - id: 110 type: string optional: true name: value ``` ### Additional context _No response_ ### Confirmation - [x] I am sure this is a bug or improvement, that is well enough described that it can be implemented. - [x] This report is for tuya-local, **not** for localtuya. - [x] If this is for a specific device, the device config filename is mentioned above, or diagnostics are included. - [x] Log messages or diagnostics relevant to the issue are included. - [x] This is not requesting addition of a new device.

Pouvez-vous lui confirmer le bug svp … je ne comprends pas son attitude alors que j’ai fourni TOUTES les données

pascal_ha · Mars 3, 2026, 10:58

Salut

Tu peux essayer de créer une entrée template capteur de modèle dans UI qui reprend ton entité energy / 100.

Puis tu utilise cet entité corrigé dans ton dashboard énergie.

En attendant que la correction soit faite dans make all tuya.