I agree with this if someone wants to get into MQTT, which is tricky to figure out at first. If not, then Kasas are about as cheap and easy as it gets.
The only concern I have with manual plugs is that they get out of sync over time, since they can’t check a time server regularly and due both to imprecise mechanisms and power outages.
But if they’ve not got anything else smart in their environment, and therefore don’t need openHAB, then they won’t have to worry about MQTT - just use the Tasmota UI. (The point of the second paragraph is using smart devices without openHAB, which I realise now isn’t clear!)
Good point. @alda1 what are you actually switching?
At this moment I’m using openHAB for rs232 communication with radiator unit for zone temperature control, next I’m using a modbus for communication with photovoltaics system victron energy and for switching relay for wather heating. In development I have communication between openHAB and heat pump via eBUS (now I’m producing eBUS-USB adapter). Next I want control a blinds - I want use a shelly relay, but for this I don’t know how to measure luminiscence during a day to make a partial oscuraction (other post here).
This timer I want use in a exterior - for a pool energy control during summer times and led control during winter times (same plug, different times). Problem is bad wifi connection, so better is save time configuration into device to prevent that plug will not switch on or off. So idea is, that depends on the switch in UI or date (rule) a openHAB will send a time configuration into timer/plug (TAPO P100 looks good, but no chance send timer configuration from openHAB ?).
Regarding MQTT - if it’s possible, better not now (no experience, no brooker…).
This really sounds like a central heating ‘programmer’, with remote schedule setting. I’d be looking at one of those that you can wire into a wallbox, not self contained plug/socket units.
My idea is program a timer of external plug with timer function depends on the switch position or depends on the time rule.
Question is, if there is any device where I can change timer directly from the openHAB.
If you just want to ensure that plug goes off in any case (for example aka antiflooding protection), you can use pretty any relay with maximum ON time protection. As far as I remember Shellies have it. This means you can turn them on and off by openhab, but if for some reason the plug remains on for longer period than programmed in maximum on setting, it will switch off by itself.
Ok, it’s maybe a solution(I must check how critical is, if relay don’t switch on). Do you know which relay type Is it?
FYI any Tasmota flashed switch also has this feature via the PulseTime command.
ok, but for Tasmota I need to run a MQTT ?
No.
That’s the traditional way, but you can use the HTTP Binding instead if you want.
But considering the long list of protocols that you’re already dealing with, sounds like you’ll have no problem with MQTT.
But to be honest, I’m still not convinced that you need to hook this up to openHAB at all - just use the in built scheduler that Tasmota provides via the webpage of the device. If it’s only twice a year then you’ll spend more time integrating with openHAB than just changing a setting or two with Tasmota.
is it possible call Tasmota webpage directly from the openhab ? I mean like “special” window ?
Is there any device on the market where I can “flash” tasmota or it’s only for DIY projects ?
2600+ devices to date: https://templates.blakadder.com/
In the UK you can even buy pre-flashed devices: Tasmota Smart Plug | Power Monitoring | Local Bytes
ohh, very nice
ok, so I can take a shelly relay :
Shelly 1 Switch Module Configuration for Tasmota (blakadder.com)
and flash with Tasmota
One more question - for simplicity, is there any chance to open tasmota configuration webpage as special window directly in openhab UI?
Well, sure, but if you’re getting a Shelly then you may find that the Shelly UI is good enough - you might not need to flash with Tasmota. Have you researched the Shelly software?
Don’t know. I presume there is a widget which allows a hyperlink to whatever webpage you like, but I’ve never tried this so someone else will have to confirm.
I found this :
https://community.openhab.org/t/tasmohab-integrate-your-tasmota-devices-easily/124027/3
but not sure how to implement
You will gain an enormous flexibility by adding Tasmota controlled devices to your setup. The flexibility will be leveraged by the additional knowledge and techniques learned in the process of introducing Tasmota to ESP based devices. Regarding the MQTT broker, you are already running openHAB, perhaps by itself on some computer. Instead, run openHAB in Docker along with eclipse-mosquitto in Docker as your MQTT broker using volume mapping for persistent data. Run Portainer as a third Docker container to be able to manage your Docker setup via any web browser.
Tasmota is quite mature in regard to exactly what devices and control features you want in addition of course to the timer scheduling. You may find much of your automatic control will be occurring at the Tasmota device level instead of at the openHAB level. OpenHAB may wind up being used primarily for an integration monitor.
It used to be that just about all retail smartplugs used an ESP8266 mcu module, which is easily re-flashed with Tasmota. Nowadays the same brand smartplugs use a different mcu module that cannot be re-flashed with Tasmota, but often that different module can be removed and a suitable ESP8266 mcu module transplanted in its place. This is the extreme end of the previously mentioned “additional knowledge and techniques learned”. The Shelly devices are a way around this. When using ESP8266 or the ESP32 development type boards, especially the ones with a USB data connection, you have the foundation for any wi-fi based Tasmota sensor and control device less a power supply and the sensor and controlled devices. As already mentioned, Tasmota is quite mature. I doubt there is anything you would like to do, even the most obscure need, that has not been already addressed in some way with Tasmota.
I’m running a openHAB on the odroid n2+ and DietPi. I’m not so experienced, so I’m happy that’s working 
and not sure which steps to do to get MQTT working (and also not sure that I need it). For me it looks too complicated and I have one important request : Be able run openHAB only with local network.
As an MQTT broker is usually installed within the same network (often the same device) as openHAB, it will be local.
Fair enough. What other option will you go ahead with?
At this moment I have only shelly relay and shelly motion - for this Mqtt isn’t necessary. Other my devices uses a modbus and serial port, so also not mqtt. But yes, maybe in the future I will need. And yes, a lot of devices works only with mqtt so I will need in the future. In general I have nothing against mqtt.
ok, on the end I decided to try install a mqqt
I used this guide
Mqqt is online. Now I must search for device for tests. Maybe I will flash some arduino board with Tasmota or Shelly 1.