logo elektroda
logo elektroda
X
logo elektroda

OpenBeken Support for Tuya 3 Phase Powermeter (ZGMISMART-SPM02)?

vincenzoernst1 2313 38
ADVERTISEMENT
  • #31 21102692
    p.kaczmarek2
    Moderator Smart Home
    can you enable verbose logging and give log again? Somehow channel value is lost?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #32 21102888
    vincenzoernst1
    Level 6  

    found it in the logs! my fault. typo. sorry!

    next step is to put it to real 3 phase mains. will report back.
  • #33 21102900
    p.kaczmarek2
    Moderator Smart Home
    What kind of typo was that? Can you show your current autoexec.bat for clarity?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #34 21102909
    vincenzoernst1
    Level 6  

    I ALWAYS update the config in the opening post!

    I swapped dplds L2 voltage was...err..... 105 ......must happen when I cleared config, cause it worked before
  • ADVERTISEMENT
  • #35 21274110
    vincenzoernst1
    Level 6  
    @p.kaczmarek2

    im missing the openbeken  build in HA info. it shows "unkown", also the IP doesnt show up in HA. since the info is in mqtt there might be a glitch in the posted topic?

    Diagnostic screen showing Build as unknown in the application.

    Added after 58 [minutes]:

    >>21095146

    @divadiow

    im trying to get the rest of the dpid working. now im searching for reasonable channel types for:

    "DPID 6,7,8: "phase", raw,
    9: "code": "fault", "type": "bitmap",
    "DPID 17,18,19": { "code": "alarm_set_1", "type": "raw",

    any suggestions on what channels to use?

    "DPID 2": { "code": "cur_neutral", "type": "value", this is not reasonablecause this unit has a neutral but its ONLY for self powering the unit. there you only can measure the units power consumption. this is not very usefull.

    16 is "switch" but how?! this is physically simply not possible by design?!?!



    maybe like so?

    //phase_a
    setChannelLabel 14 "L1"
    setChannelType 14 OpenClosed_Inv
    linkTuyaMCUOutputToChannel 6 raw 14
    
    // breaker_id
    setChannelLabel 17 " breaker_id"
    setChannelType 17 ReadOnly
    linkTuyaMCUOutputToChannel 19 string 17
    
    // fault
    setChannelLabel 18 "device fault"
    setChannelType 18 ReadOnly
    linkTuyaMCUOutputToChannel 9 bitmap 18
    


    breaker id shows 0. also its shown as: "Channel breaker_id". channel is not a nice wording here.
    for "OpenClosed_Inv" setChannelLabel 14 "L1" is NOT working. it shows "CLOSED (ch14)". Why?
  • #36 21274799
    p.kaczmarek2
    Moderator Smart Home
    Does executing publishAll fix the missing information in MQTT HA (with a delay)?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #37 21275240
    vincenzoernst1
    Level 6  
    @p.kaczmarek2

    with publishAll build is shown correctly. 👍 is this a bug or does it intended behave this way?
    Diagnostic interface displaying software version, signal strength, temperature, and uptime.


    IP doesnt show up though. so the link ("Besuchen" / "visit" in the english version, i guess) to the OB gui does link to the wrong IP:

    Screenshot of a user interface displaying device and sensor information.
  • #38 21275585
    p.kaczmarek2
    Moderator Smart Home
    I was almost sure that "publishAll" does the same what is done if you enable "broadcast self state on MQTT connect", so it's most likely a bug, but it's very strange... I will need to triple-check it.
    Helpful post? Buy me a coffee.
  • #39 21275591
    vincenzoernst1
    Level 6  
    can i help to check?

Topic summary

The discussion revolves around the compatibility of OpenBeken firmware with the Tuya 3 Phase Powermeter model ZGMISMART-SPM02. The user seeks to determine if OpenBeken can effectively handle and display metrics for three-phase power, voltage, current (both forward and reverse), and frequency, given that Tasmota does not support this functionality. Participants in the forum provide insights on flashing the device with OpenBeken, configuring the TuyaMCU interface, and creating custom HTML panels. They discuss the mapping of data points (dpIDs) for voltage and current readings, troubleshooting issues with displaying all three voltages, and scripting capabilities for data processing. The conversation also touches on the need for proper channel types and the potential for custom scripting to enhance functionality.
Summary generated by the language model.
ADVERTISEMENT