Tasmota
Tasmota copied to clipboard
Shelly 1PM power monitoring not working after first flash
PROBLEM DESCRIPTION
Similar to issue https://github.com/arendst/Tasmota/issues/5592, after first flashing the current Tasmota 12.1.1 firmware to my Shelly 1PM, I see only incomplete power monitoring data.
I took the devices from the grid and waited a few minutes, but the situation did not change.
SerialLog is disabled.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
- [ x] Read the Contributing Guide and Policy and the Code of Conduct
- [ x] Searched the problem in issues
- [ x] Searched the problem in discussions
- [ x] Searched the problem in the docs
- [ ] Searched the problem in the chat
- [ ] Device used (e.g., Sonoff Basic): Shelly 1PM
- [ ] Tasmota binary firmware version number used: 12.1.1
- [ x] Pre-compiled
- [ ] Self-compiled
- [ ] Flashing tools used: https://github.com/yaourdt/mgos-to-tasmota
- [ ] Provide the output of command:
Backlog Template; Module; GPIO 255
:
Configuration output here:
16:00:43.085 MQT: stat/tasmota_E588CD/RESULT = {"NAME":"Shelly 1PM","GPIO":[320,0,0,0,192,2720,0,0,0,0,0,224,0,4736],"FLAG":0,"BASE":18}
16:00:43.284 MQT: stat/tasmota_E588CD/RESULT = {"Module":{"0":"Shelly 1PM"}}
16:00:43.539 MQT: stat/tasmota_E588CD/RESULT = {"GPIO0":{"320":"Led_i1"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"192":"Switch_n1"},"GPIO5":{"2720":"BL0937 CF"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"0":"None"},"GPIO14":{"0":"None"},"GPIO15":{"224":"Relay1"},"GPIO16":{"0":"None"},"GPIO17":{"4736":"ADC Temp"}}
- [ ] 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:
- [ ] Set
weblog
to 4 and then, when you experience your issue, provide the output of the Console log:
Console output here:
TO REPRODUCE
Steps to reproduce the behavior:
EXPECTED BEHAVIOUR
Everything working out of the box.
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)
I just flashed my Shelly EM and I have the same problem.
Output status 0:
17:17:52.021 CMD: status 0 17:17:52.028 MQT: stat/tasmota_shellyEM/STATUS = {"Status":{"Module":0,"DeviceName":"Shelly EM","FriendlyName":["Shelly EM"],"Topic":"tasmota_shellyEM","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0}} 17:17:52.061 MQT: stat/tasmota_shellyEM/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:00:12","StartupUTC":"2022-09-09T16:17:40","Sleep":50,"CfgHolder":4617,"BootCount":9,"BCResetTime":"2022-09-09T15:07:49","SaveCount":29,"SaveAddress":"F7000"}} 17:17:52.096 MQT: stat/tasmota_shellyEM/STATUS2 = {"StatusFWR":{"Version":"12.1.1(tasmota)","BuildDateTime":"2022-08-25T11:33:55","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"350/699"}} 17:17:52.117 MQT: stat/tasmota_shellyEM/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["WIFEO",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}} 17:17:52.151 MQT: stat/tasmota_shellyEM/STATUS4 = {"StatusMEM":{"ProgramSize":624,"Free":376,"Heap":24,"ProgramFlashSize":1024,"FlashSize":4096,"FlashChipId":"1620C2","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8F9AC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","54000020","00000000"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37,45,62","Sensors":"1,2,3,4,5,6"}} 17:17:52.186 MQT: stat/tasmota_shellyEM/STATUS5 = {"StatusNET":{"Hostname":"tasmota-shellyEM-7023","IPAddress":"192.168.0.8","Gateway":"192.168.0.1","Subnetmask":"255.255.255.0","DNSServer1":"8.8.8.8","DNSServer2":"0.0.0.0","Mac":"C4:5B:BE:77:7B:6F","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}} 17:17:52.212 MQT: stat/tasmota_shellyEM/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.0.6","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_777B6F","MqttUser":"DVES_USER","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}} 17:17:52.236 MQT: stat/tasmota_shellyEM/STATUS7 = {"StatusTIM":{"UTC":"2022-09-09T16:17:52","Local":"2022-09-09T17:17:52","StartDST":"2022-03-27T02:00:00","EndDST":"2022-10-30T03:00:00","Timezone":"+01:00","Sunrise":"06:18","Sunset":"19:16"}} 17:17:52.254 MQT: stat/tasmota_shellyEM/STATUS9 = {"StatusPTH":{"PowerDelta":[0,0,0],"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}} 17:17:52.276 MQT: stat/tasmota_shellyEM/STATUS10 = {"StatusSNS":{"Time":"2022-09-09T17:17:52","ENERGY":{"TotalStartTime":"2022-09-09T15:07:49","Total":0.000,"Yesterday":0.000,"Today":0.000,"Power":[ 0, 0],"ApparentPower":[ 0, 0],"ReactivePower":[ 0, 0],"Factor":[0.00,0.00],"Voltage": 0,"Current":[0.000,0.000]}}} 17:17:52.301 MQT: stat/tasmota_shellyEM/STATUS11 = {"StatusSTS":{"Time":"2022-09-09T17:17:52","Uptime":"0T00:00:12","UptimeSec":12,"Heap":24,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":28,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"WIFEO","BSSId":"D8:07:B6:5F:FB:AE","Channel":8,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}}
? Yours looks normal. You have Current and Voltage. That's what my 2.5 looks like also.
I just realized that if I activate the relay output, I start to see measurements, but the device responds very slowly when moving through the WebUI menus, it must be a GPIO configuration problem or something similar.
Not sure these two issues are related.
Probably not @isabido see https://tasmota.github.io/docs/Commands/#setoptions
@isabido no idea what is your issue yet. I would assume may be a wrong template as the Sh1PM is supposed to use serial to get power measurement but nothing in the template is about serial. May be someone who owns one will pass by
Thanks for the suggestion it worked! I have tried this option and it works correctly, even if I turn the relay on or off, I always have the measurement.
SetOption21 on
Another problem I see is that the independent energy counters do not appear for each of the two channels that ShellyEM has.
There's another setoption for that https://tasmota.github.io/docs/Commands/#setoption129
Read the doc section regarding Power Monitoring everything is listed there https://tasmota.github.io/docs/Commands/#power-monitoring
Perfect!!! Now it's working, thank you very much for your help!
If I activate the temperature, it marks a value that is not real and the RELAY is automatically deactivated when activated. It is not possible to calibrate the temperature more than 12º parameter TempOffset -12.0
@barbudor Already a more in-depth topic, the ADE7953 has an important register to calibrate the Phase in the address 0x203 (PHCALx register)
This is very important to correct the phaseshift introduced by the CT (CLAMP) with very low PF loads.
In my case I have two air conditioning machines that consume P=20W in standby with a CosPhi of 0.1. The Shelly is not able to measure this active power correctly, it indicates -5W (negative) and a PF= -0.2
Would it be possible to access this register?
I enclose some images where you can compare values between the reading of my company's digital meter and the shellyEM
https://www.analog.com/media/en/technical-documentation/application-notes/AN-1118.pdf
https://www.analog.com/media/en/technical-documentation/application-notes/AN-639.pdf
More information PHCAL
https://www.analog.com/media/en/technical-documentation/data-sheets/ADE7953.pdf
It would also be very interesting to have a reading of the ANGLES registers.
@isabido it would be better that you move to a discussion related to the EM or open your own as your questions are nor related to original poster. Search on Discussions as all these have already been addressed as well as with calibration procedure documentation
This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.
This issue was automatically closed because of being stale. Feel free to open a new one if you still experience this problem.