BlitzWolf SHP2 V3.3 no energy monitoring data

[jfrogg]

PROBLEM DESCRIPTION

I've got a BlitzWolf SHP2 with PCB marked V3.3. Basic functions are working (button, relay, LED), however no energy monitoring data displayed.
Monitoring chip is HJL-01 and the board is similar to the one pictured here
Chip placement is different comparing to the other SHP2 devices.

REQUESTED INFORMATION

• [Y ] Read the Contributing Guide and Policy and the Code of Conduct
• [Y] Searched the problem in issues
• [Y] Searched the problem in the wiki
• [Y] Searched the problem in the forum
• Searched the problem in the chat
• Device used (e.g., Sonoff Basic): BlitzWolf SHP
• Tasmota binary firmware version number used: 7.1.2
  • [Y] Pre-compiled
  • Self-compiled
    • IDE / Compiler used: _____
• Flashing tools used: _____
• Provide the output of command: Backlog Template; Module; GPIO 255:

19:08:43 RSL: RESULT = {"NAME":"BlitzWolf SHP","GPIO":[56,255,158,0,130,133,0,0,0,17,132,21,0],"FLAG":0,"BASE":45}
19:08:43 RSL: RESULT = {"Module":{"45":"BlitzWolf SHP"}}
19:08:43 RSL: RESULT = {"GPIO0":{"56":"Led1i"},"GPIO1":{"0":"None"},"GPIO2":{"158":"LedLinki"},"GPIO3":{"0":"None"},"GPIO4":{"0":"None"},"GPIO5":{"134":"BL0937 CF"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"131":"HLWBL SELi"},"GPIO13":{"17":"Button1"},"GPIO14":{"132":"HLWBL CF1"},"GPIO15":{"21":"Relay1"},"GPIO16":{"0":"None"}}

• If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

  Rules output here:

• Provide the output of this command: Status 0:

  STATUS 0 output here:

• Provide the output of the Console log output when you experience your issue; if applicable:
  (Please use weblog 4 for more debug information)

  Console output here:

TO REPRODUCE

Steps to reproduce the behavior:

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

[meingraham]

This is likely due to a different hardware rev level for the same model device.

Please address this to the Tasmota Support Discord Chat. The chat is a better and more dynamic channel for helping you. Github issues are best used for Tasmota software feature requests and bug reporting. Troubleshooting and setup assistance is more effective using an interactive forum.

Please check the Contributing Guideline and Policy and the Support Guide.

Thanks.

Support Information

See Wiki for more information.
See Chat for more user experience.
See Community for forum.
See Code of Conduct