We've calibrated internal temperature sensor with @DeDaMrAz and it worked well for our devices, it's hard to say about yours. If you have thermal camera, you can double check whether shown temperature is correct. Usually I would also recommend to enable power saving, but for BL0937, it's a bad idea - it would reduce the precision of measurements
@p.kaczmarek2 Maybe this is another version of the Denver SHP-102, but the data in the list of devices currently points to a wrong or alternate version of this Device.
I just bought another two of these devices. The shop had them for sale now, 5 Euro/each. I could not resist .
Here's a more detailed recipe to unlock these devices with tuya cloudcutter:
I use an old 32 bit laptop with both WIFI and UTP wired Ethernet active. It has LINUX (ubuntu) installed.
Installed Docker earlier so I can not exactly point out how to do that.
Download the tuya cloudcutter: https://github.com/tuya-cloudcutter/tuya-cloudcutter
Go into a terminal and into the cloudcutter directory
I just followed the instructions as described in the cloudcutter github:
Run:
sudo ./tuya-cloudcutter.sh -s <SSID> <PASSWD>
by manufacturer/device name
--> Denver
--> SHP-102-plug
choose 1.1.8-BK7231N/oem-bk7231N-plug
upon questions to terminate certain services to free the WIFI answer yes to all
Get the device into slow blink mode. In my case I had to press the button 5secs to get it in fast blinking mode, then another 5 secs to get it in slow blinking mode.
After a while you have to do that again. Unplug and press button 5secs/again 5secs
You may have to try the unplugging and slow blinking mode several times to connect, be patient.
When the program ends normal without errors run it again but without extra commands:
you may have to say 'yes' to all the 'terminate this and that?' questions.
choose the 3rd party firmware, in my case it presented
openbeken-v1.17.697
Unplug your device and get it in slow blink mode...
Wait for it.....
You may have to unplug - slow mode it a few times to connect
Then at some point it will start flashing:
firmware update 10%
firmware update 20%
etc
and the program will terminate without errors.
Now use e.g your phone. Goto your wifi settings and choose the WIFI accespoint OPENBEKEN....(something)
When connected open a webbrowser on your phone and enter
192.168.4.1
If all went according to plan you're in!
Goto config and set your SSID and PASSWD that you use for your home
Check and double check that you entered the name and password correctly.
Unplug and replug your device. Now you can reach it from within your home environment. You can search for the IP address in your router.
Then in the openbeken application you need to change some settings. I personally set all my openbeken devices with a static IP address. Rename it to something that is clear
e.g. 'Kitchen Boiler'. You also need to set the pins:
BL0937 SEL Pin24
BL0937 VI (CF1) Pin 6
BL0937 ELE (CF) Pin 7
Button Pin 11 (Ch1)
LED_n Pin 10 (Ch1)
WifiLED Pin 8
Relay Pin 26 (Ch1).
Do not forget to hit the 'save' button everytime you change something.
I then calibrate the Energy meter:
I have a 1300W heater. It is purely resistic and that is what you want for an accurate setting. A incandescent lamp (the old one with the tungsten filament) will do as well.
Choose one with a high energy consumption 60W minimum.
In the openbeken app of your device goto 'lanch web application'. It will open a new page. Choose the tab 'Tools'
In the 3rd column the power metering is addressed.
Do some math: If you have a 100W light bulb it will draw 100W/230V = 0.435 Amps
a 60W light bulb will draw 0.26 Amps
My 1300W heater will draw 1300/230 = 5.65 Amps
You have to fill in all three values and hit 'apply', even if the values seem to be correctly filled in already, always hit apply!
So in my case:
Voltage 230 --> apply
Current 5.65 --> apply
Power 1300 --> apply
Check in the main page whether you succeeded.
I also create an autoexec.bat file (tab 'filesystem')
With contents:
startDriver ntp
ntp_timeZoneOfs 1:00
(hit save!)
I am in timezone +1 hour, you may have to change that into your timezone.
This will set the correct time for your device.