Max Prokhorov

It is possible, ofc. Just means we would need to merge OneWire library with Dallas sensor code and name it something like ShellyTemperature.

@SiskoBen afaik, github allows file drag-n-drop everywhere, you can attach the file here / https://gist.github.com / drop in into a new branch (see fork) Do you use multiple ECH1560 class...

> Yeah... Those don't work with my version of WP2 (V1.1 2018) and the simple program I wrote to test the GPIOs. For one, there are four LEDs and not...

`INPUT_PULLUP`?

:oops: I did not type the rest. This was mentioned on gitter - https://gitter.im/tinkerman-cat/espurna?at=5df8a3a20dc628523e4de80c Since for some reason newer plugs don't have hw pullups anymore Tasmota tries to set pullup...

See https://templates.blakadder.com/blitzwolf_SHP7.html for the pinout We don't have any pre-defined hw yet, but see VANZAVANZU_SMART_WIFI_PLUG_MINI in [`hardware.h`](https://github.com/xoseperez/espurna/blob/dev/code/espurna/config/hardware.h) as an example.

For WP2, this should be: https://templates.blakadder.com/gosund_WP2.html Names for both templates can be referenced here: https://tasmota.github.io/docs/GPIO-Conversion/ https://github.com/xoseperez/espurna/wiki/Buttons-and-switches#tasmota-templates For OT, something like (obviously, untested) ```cpp #elif defined(BLITZWOLF_BWSHP7) // Info #define MANUFACTURER "BLITZWOLF"...

Note that we kind-of do output the bucket payloads via Portisch fw already, you just need to enable them via the serial command `AAB155` (I think? Wiki is kind of...

Also note of the https://github.com/NorthernMan54/rtl_433_ESP Which is currently in use in the OpenMqttGateway, but afaik it is only tested (?) with ESP32

RE: above, both MQTT (through a .../set topic) and HTTP API should already work with dev builds Scheduling part is something to add though