Tasmota home assistant mqtt discovery. But only two have been added into HA.

Tasmota home assistant mqtt discovery Also restarting after the SetOption19 1 command does not make the Tasmota device publish the discovery topics. Also if you use MQTT explorer, you should see the messages in the Use MQTT and execute commands (if necessary, replace tasmota with unique topic you configured in Initital Configuration, see point 5 there): cmnd/tasmota/DzIdx1 with payload value read in step 2. 6 mqtt broker using eclipse mosquitto 2. Home Assistant Discovery Generator - Helps in the creation of the Discovery message payload. The light control appears in the HA Overview panel. 2 For some day, tasmota is sending the discovery topic via a seperate channel, not via homeassistant/sensor. I assumed at this point the device would appear in Home Assistant at this point for configuration via the front-end GUI. No matter what you choose (My Home Assistant Link, Manually search and install MQTT from Before you can start adding and managing Tasmota devices in Home Assistant, you will need to install the TasmoAdmin add-on. 2 Tasmota created a named MQTT device based on the friendly name with the correct Home Assistant MQTT Discovery (SetOption19) #8664. Should I turn it both on or off ?. But only two have been added into HA. It’s configured for MQTT discovery and home assistant found it just fine. Mosquitto is installed. Integrating Tasmota with Home Assistant. But it just says. Are you using this Home Assistant 2022. User odt has re-opened a 2-year old topic, about the MQTT integration, to discuss a different integration I am trying to set up my first home assistant. Device details at the end. Auto discovery has been working fine up till a couple of days ago when it stopped working, I flashed a new device with Tasmota and Home Assistant failed to pick it up. It’s a once off. Just for my own interest, I also installed MQTT-Explorer on the host machine and can actually see the topics and payloads for Sonoff and Kasa switch within MQTT-Explorerlife is good till this point!! Now I Hi to all. On connection to the MQTT broker tasmota uses the Last Will and Testament (LWT) feature that instructs the broker to generate a notification about an mqtt: broker: a0d7b954-mqtt username: !secret mqtt_username password: !secret mqtt_password client_id: home-assistant discovery: true. While here, you might as well change the Friendly Name into something more descriptive than generic "Tasmota". With MQTT discovery, no user interaction or When Home Assistant is restarting, discovered MQTT items with a unique ID will be unavailable until a new discovery message is received. 12. Edit: ah sorry didn’t read it well enough. However, this discovery method has been deprecated by Tasmota’s development team in favor of their Release 5. This initial version includes multiple views (Control, Health, Firmware, Wi-Fi, & MQTT) to allow you to quickly assess the state of your Device attributes in MQTT explorer leveraging the built in Tasmota auto discovery topic . Closed 8 of 15 tasks. The third one ist not available as a sensor. I have loaded Tasmota onto a Sonoff Zigbee Bridge Pro. 7 firmware wifi plug. Các thiết bị thường được kết nối PROBLEM DESCRIPTION. The obvious location for this is on the “Configure Other” tab, as this is where other device specific Perhaps all that is needed is to add a line in Home Assistant’s Tasmota integration documentation that mentions the prerequisites are in the link I just The latest version of Tasmota firmware now uses Tasmota’s Hi All, I have been wondering if it possible for the home assistant to have multiple discovery prefixes. I applied the template through the web interface, and setup the MQTT settings. ady8077 (Adrian Ewing) January 15, 2019, as this will make mqtt discovery work a little better in Home Assistant. The Tasmota alternative ESPxx firmware moved away from HASS Discovery to Tasmota Discovery as the alternative significantly reduces memory usage with a single config string payload (and nice stuff like set the device location in Tasmota for auto-discovery - i. I use the auto discovery option when configuring the integration They are all sonoff devices, flashed to Tasmota, and I have setoption19 set to For a basic setup you only need to set Host, User and Password but it is recommended to change Topic to avoid issues. I have installed MQTT long ago on HA. Hello, I noticed that in the docs, MQTT discovery does not save states for devices between reboots. Home Assistant Add the HACS (Home Assistant Community Store), if not already done. The problem is with the switch. Then we finally can set Target According to the Sonoff-Tasmota link, all that should be required is SetOption 19 On in the console of the Sonoff and then a restart of Hassio after the MQTT discover lines have been added to configuration. Home Assistant You are trying to read ‘DS18B20’ three times in home-assistant. I’ve also run SetOption19 1 on the I am playing with tasmota firmware on a few sonoff mini devices, and they work great. I already try SetOption30 on and off. Should help. (preferred but Tasmota only ) In this tutorial we will look at the first two methods manual and auto using Once MQTT is enabled you need to set it up using Configuration -> Configure MQTT. 0. If your Tasmota devices are using Home Assistant’s MQTT Discovery feature, there’s a way to override a device’s configuration (by manually publishing a new discovery payload to overwrite the device’s existing one). . Details on the D1mini: → tasmota-display. However, after trying a few things, it’s clear The order of %prefix% and %topic% doesn't matter, unless you have enabled Auto-discovery for Home Assistant (SetOption19). My unraid server borad got toasted last week so I had to quickly create a plan B. 10. 0 and configured to communicate with my Mosquitto MQTT broker. I can send MQTT request to the sonoff and works, But MQTT integrantion can´t find sonoff in auto discovery. 2, I have been moving all of my devices over to Tasmota discovery (SO19 0). yaml and any previously configured MQTT switches or Home Assistant Tasmota integration allows you to control Tasmotized Devices over MQTT without having to add a tone of YAML code. bin There is an AM2301 Sensor (temp/humidity) and a SSD1306 MQTT là giao thức chuyển tải thông điệp giữa máy và máy, rất nhanh và được sử dụng nhiều trong các ứng dụng IOT – Internet vạn vật. Still worth a try I have several lights and switches using Tasmota firmware and communicating with Home Assistant over MQTT. My Mosquitto (MQTT broker) is correctly configured and working. Does this have to do with a new homie Hello there I hope someone can help me. I have SetOption19 0 on the Tasmota. Blakadder’s Smarthome Shenanigans – 23 Aug 20 Hi, I am running a supervised version of HA and also have MQTT running (as add-on) with a mqtt_user_name and mqtt_password defined on the configuration tab. So, the first step will be installing the MQTT add-on on Home Assistant I have number of Sonoff devices flashed with Tasmota 12. My setup all Tasmota devices connecting via MQTT, Mosquito running as part of the install from Ubuntu Server 18, not using HA plugin. I have Home Assistant running on a virtual machine. They all work great and I can control them from Home Assistant by adding them as binary sensors in a dedicated MQTT section. 04. I loaded the Tasmota integration and it sees the Bridge parameters, but no sensors Sorry to revive an old thread, but I am having this similar issue right now. However, in preparation to upgrade to Tasmota 12. facebook. Tasmota devices’ MQTT setting configured to communicate with the MQTT broker. stingrayuk opened this issue Jun 11 The Tasmota Firmware supports a Thermostate mode. In most cases this has worked flawlessly. 3 Frontend 20221102. 1 Like. What would be the benefit of moving to the new integration? I see that both need a running MQTT server so I can’t see why I would want to switch. On my Treatlife DS01 dimmers, though, when I disable SO19 the Tasmota discovery works as expected: Hi, I have a slightly different problem with MQTT auto discovery. Let’s see this in action. 2 and using HASS MQTT autodiscovery (setoption19 1). 3 Version of HA: Core 2023. Other non-Tasmota devices are discovered without any problems. I am trying to migrate one of the devices to “SetOption19 0”. 2 Operating System 9. tedsluis (Ted Sluis) January 14, 2019, 7:50am 7. 111. So - if i Hi, I have about 3 sonoff (Tasmota) switches that i am trying to integrate with my Home assistant. I’ve been searching how to advertising the MQTT service via mDNS, so I don’t have to set up the MQTT I have only the MQTT integration. The potential hiccup is that if you Hello I have an LED light strip that I have installed Tasmota onto. 1) but I see there’s a new Tasmota integration. com/homeswitchplInstagram:https: Hello, I recently installed Home Assistant Operating System on a Raspberry Pi 4 using the Balena Etcher method. 1, Hass 227 and Mosquitto Broker 5. xx. 7. 5 Getting started; Documentation . the Tasmota project will eventually drop support for Home Assistant’s MQTT Discovery). It provides control over brightness I have a tasmota v6. enjoy. Home Assistant has a feature called MQTT Search. But the new Tasmota integration is just not I was having issues with some new MQTT devices showing up in HA, so I deleted the integration, restarted, HA prompted me set it up, and now it’s not finding any devices, including the ones that were found previously. I have Hi, I’ve successfully flashed Tasmota-lite firmware on a cheap Geeni Wi-Fi bulb. That’s because the “other Tasmota WiFi devices” are publishing topics and payloads that conform with the specifications for Home Assistant’s MQTT Discovery service. I have a bunch of Tasmota devices working already using the “MQTT discovery”. home assistant vers 2021. At this point, you should have the single device with two entities; dimmable light and binary-switch fan as shown in the first picture Hi, I have 3 D1mini. @123, when you say you say you don’t use logins, I’m Currently it knows about Home Assistant Discovery, Tasmota and Zigbee2MQTT. I have set up the MQTT integration on HA and configured the Tasmota appropriately I hope. The current idea that I have in my is to have a node-red function to Whenever this happens to my with Tasmota, I turn discovery off on the devices SetOption19 Off then I remove the MQTT integration, disable the broker and restart home assistant. When you used HA discovery in Tasmota it automatically changed the topic. So if the lights were “ON” before, and are obviously not on anymore, the HA UI keeps showing “ON. I tried to do it in others computers and I always get the same result. Configuration. I’ve installed the MQTT Broker on my rPi/Hass install and configured MQTT on the light bulb. I have a similar but not exact problem that I seem to dumb to totally diagnose and correct. With MQTT discovery, no user interaction or configuration file editing is required to add a new device to Home Assistant. We are going to configure MQTT on Tasmota and Home Assistant so that the Tasmota device will auto-discover in Home Assistant. 1 and the SetOption19 the 8. The Integration with the Stock Thermostat Tile is naerly impossible to accomplish for Beginner like me. The JSON output you posted in the first half of the post clearly lists ‘DS18B20-1’, ‘DS18B20-2’ and ‘DS18B20-3’. You can now leverage the Tasmota integration in Home Assistant which will detect your new device based on the auto discovery message published by the device on startup to ‘tasmota/discovery’ I unfortunately cannot help with the HassIO MQTT broker setup, but defaults should be fine as long as you’ve specified a user/password in the logins: section as below or are using a user defined in Home Assistant already logins: - username: user password: passwd Make sure HA and MQTT broker are running before executing the next steps This is the definitive (?) guide to setting up a PIR in Tasmota and adding it to Home Assistant using discovery. I have also tried to install the Tasmota integration to change the topic to a topic that I can access but it does the subscription to the topic I choice and stills tries to subscribe to tasmota/discovery/# topic. ady8077: According to this Tasmota doesn’t support qos 2 Turn on discovery in home assistant mqtt setup. Using Tasmota 8. I’d like to take that opportunity to implement the autodiscovery for MQTT. I have sonoff mini using tasmota 8. MQTT items without a unique ID will not be added at startup. if I can put an override somewhere to add it in. ” Some devices I would like to be only connected to This is useful because it means it is retained (stored) by the MQTT Broker. 2) for home assistant it has docker version 20. A couple of times all my tasmota devices show as unavailable. So a device or service using MQTT discovery must make sure a configuration message is offered after the MQTT integration has been (re)started. 1c or newer (must include support for home-assistant style MQTT discovery) Sonoff devices must have Home Assistant Discovery (option 19) set to 1 (setoption19 1) Sonoff devices Hi all, So I have HAOS, fully updated as of today. The last plug was reset during a power outage (have since changed setoption65 to 1 to avoid that in the future). Using 8. the sensors connect to mqtt ok log Hello, here’s a short video guide showing how you can pair the new non-ESP Tuya chips with Home Assistant by using OpenBeken multiplatform/portable firmware (inspired by Tasmota, compatible with most Tasmota MQTT json and many commands), that currently support multiple new Tuya IoT platforms, including BK7231T/BK7231N and much more: Our HA Turn on discovery in home assistant mqtt setup. Future releases of the Tasmota compiled firmware will no longer include support for Home Assistant’s MQTT Discovery. You use NodeMCU, unfortunately I have zero knowledge in that area. Tasmota discovery works well and includes units for long term stats I am going to tag in on this conversation if you don’t mind. All of them send mqtt-data to my mosquito in HA. Notebook/PC Layout ha_neopool_mqtt_lovelace. Trong Home Assistant, MQTT là một trong các giao thức để kết nối và điều khiển các thiết bị khác bên cạnh các giao thức như HTTP, Websocket. The device configuration in Tasmota is shown on the left. 1 (lite) and SetOption19 1; HA 0. local domain!); Port = your MQTT broker port (default port is set to 1883); Client = device's unique identifier. Instructions on how to setup MQTT within Home Assistant. My HA Core was running almost perfectly for 2 years in docker on an UnRaid system. Manually search and install MQTT from integrations, or the auto-discovery) from the above the result is the same. ino and I'm impressed with the ease of adding Tasmota devices to Hass this way. I have around 30 Tasmota devices already connected and working fine. So i can use these with generc thermostat. I’ve turned on SetOption19 have tried turning it on and off but no luck, is there something different with this model? I’m using tasmota32-bluetooth. In a previous tutorial I covered the setup of tasmota on Sonoff switches and you should read that tutorial before Before proceeding, make sure MQTT is properly configured in Home Assistant and Tasmota. Enabling this option re-formats the FullTopic to required order. Enter the MQTT username and password for Hi all, Having a few problems getting auto-discovery working with my first tasmota device on a pre-existing HA installation. I’m running Mosquitto broker from the Tasmota is a small open source home automation software that can be flashed onto any expressive chipset and used to control lighting, fans, switches etc using both HTTP and MQTT protocols over Wi-Fi. Right, the stock one is not suited for this purpose, because the logic is in Hassio. After succesfully flashing 4 sonoffs with tasmota, wiring them to my non-smart lights and everything, I feel stupid for not figuring out how to do the last step: adding the sonoffs in hass. 4 Frontend 20231208. 11 Tasmota based temp humiidty etc sensors. 1. I used in past the Mosquitto MQTT and plan to reinstall same broker (excepted if there is an other one really better and working on Raspberry PI). yaml. I built a system on a Lenovo ThinkCenter. I have added the relevant lines for all switches but when i restart the HA, only the last one appears. To check if the ha_neopool_mqtt_package. The embedded MQTT broker does not save any messages between restarts. The only benefit is they aren’t tied to the Home Assistant API for creating sensors, so they can add custom things beyond what the Home Assistant MQTT discovery API would allow. That Feature is pretty nice and works fine with all that features, described here: [MQTT Discovery - Home Assistant] But I would like to add some features (similar to Tasmota): Adding a new window I have just spent hours trying to get my tasmota plug to be discovered by home assistant. I read somewhere that auto discovery can be switched on/off in Tasmota? setoption19 is already set to “0”. Tasmota currently doesn’t capture area or location information - Tasmota FW change. It works just fine! But I’m confused why. I can see the sensors on the Tasmota Console. This integration has no devices. Turns out I had the “lite” version of the firmware installed, upgraded to the full version (not lite) and the plug was instantly discovered. If you use the embedded MQTT broker you have to send the MQTT discovery messages after every Home Assistant restart for the devices to show up. According to the Sonoff-Tasmota link, all that should be required is SetOption 19 On in the console of the Sonoff and then a restart of Hassio after the MQTT discover lines have been added to configuration. Host = your MQTT broker address or IP (mDNS is not available in the official Tasmota builds, means no . How to use Tasmota with Home Assistant. I used Hi I’ve been fiddling about with this for 2 days and still no joy. Tasmota devices flashed with version 9. 1 does not create the MQTT device correctly in home assistant. This is to ensure that I can develop several devices with appropriate naming for the prefix. I have MQTT itegration working with dicovery on. As soon I turn it on via HA-NeoPool-MQTT Home Assistant MQTT integration for Tasmota NeoPool module (ESP32 and ESP8266 devices). Home Assistant OS. 0 Supervisor 2022. We need a frotend tile, able to send and receive values via MQTT to the Tasmota Thermostat. 2024. yaml: Reponsive Layout Hi team. Auto setup using configuration data sent using MQTT auto discovery and the Tasmota integration. Tasmota device Tasmota with IP 192. 1 addon. yaml and any Link do wpisu na blogu:https://blog. I’m using tasmota on a nodemcu, it has 4 switches and 1 relay connected. Maybe is a bug, but is Home Assistant Community Tasmota v12 no longer has the MQTT discovery code, so now using the HA Tasmota device integration, but big problem. When Home Assistant is restarted, it re-connects to the MQTT Broker, re-subscribes to the discovery topic and, because the messages are retained, Home Assistant gets them immediately (and the entity is preserved). One thing that I found quite annoying and counterintuitive is that the entity id of discovered entities derived from the MQTT name without a If you are new to Home Assistant, then follow our previous tutorial on Getting Started with Home Assistant. Hey, I’m extensively using MQTT discovery in conjunction with ESP8266 devices. For me, only firmware 10. By default, Home Assistant sends online and offline to SpeedTest-CLI MQTT; SwitchBot-MQTT-BLE-ESP32; Tasmota (starting with 5. Currently it has validation for Sensor entities. When I look at the MQTT messages it’s sending, I don’t see it starting with /homeassistant. bin Once Home Assistant has forgotten all about the manual entities and the native Tasmota integration in installed, all of the MQTT-connected Tasmota devices should get picked up and configured in Home Assistant. Now that I’ve added the host, UN, and PW to the Tasmota MQTT settings, the autodetect is working correctly. 2 Tasmota created a named MQTT device based on the friendly name with the I have been using a mix of Tasmota discovery and Home Assistant discovery. 3? As I’ve sucessfully used MQTT Discovery to create my own Python devices (with sa or suggested area) I’d agree with the sentiment, but there’s several steps to achieving this. Using Auto Discovery, the discovered entities I am using auto discovery of MQTT on an Arilux LC06 running Tasmota. Not quite sure what you mean. But, if I remove power to the sonoff, the HA UI doesn’t see it go offline (no way to send out a mqtt update on powerdown). 2, or later ( tasmota-lite. 1 - latest " Tasmota device Tasmota has an invalid MQTT topic. I As I see here [OH3] Tasmota via MQTT Autodiscovery there’s a possibility to “autodiscover” MQTT things and their channels. Hi As I played too much with my existing HA system (tweaking things, trying lot of stuffs), I’m going to reinstall it soon clean on a new system. I’ll submit a suggesting to add this info to tasmota, as I think it would be helpful for new people like myself when setting this up for the first time. Turn on discovery in tasmota. MQTT Discovery REMOVED. I found a pack of Teckin SB50 Bulbs in my parents garage so I flashed them all with Tasmota. I am also getting the following error: duplicated mapping key at line 94, column -220: switch: ^ Does anyone know what i can do in this case? > switch: > platform: mqtt > The problem comes when you rely on the Tasmota (beta) and not on the MQTT integration to re-discover your devices. set up the device; not HASS). MQTT Discovery I’m currently using my Tasmota devices using the native MQTT discovery mode offered by earlier versions of Tasmota (I’m on 8. This is not a discovery issue after HA reboot as I already have automation’s in setup to discover them after HA reboot and that works fine. Home Assistant can add Tasmota devices with : Official Tasmota integration – preferred automatic instant entity detection. I have performed the steps to let the tasmota device about the MQTT IP address, username and password. 6 with the following containers. SetOption19 On that enables MQTT discovery. Per Tasmota Sonoff devices must be flashed with 5. I reconfigured it and tried adding it to HASS again, but it just Hello All, I recently started getting into Home Assistant and most of the integrations are working fine - I have a zigbee hub thats running tasmota and im having some difficulty getting it to discovery my temperature sensors I’ve installed the mosquitto mqtt broker on my HA install and I’ve configured the MQTT section of the Tasmota interface - HA has automatically added Thanks @gadgetbazza, unfortunately that isn’t the solution, at least for me. I can connect to it with the device IP address, and control if through the tasmota interface. However, I wonder if there is a possibility to do so in the configuration. Using MQTT Explorer (Windows) I can see them, and can publish to them, but no integration shows in in my HA recently I configured a dedicated ubuntu server (vers 10. Just to have better readability. Home Assistant. 4). The confusion is that this topic was started in April 2019, well before the Tasmota integration existed, and is about the MQTT Integration. homeswitch. Here’s the current situation: MQTT (mosquitto) installed and working (I already use for other, bespoke integrations) The “enable newly added entities” option is enabled in the MQTT integration Tasmota device flashed and configured for both wifi When SetOption19 = 0, send Tasmota’s custom MQTT discovery format; When SetOption19 = 1, send Home Assistant’s MQTT discovery format; It still uses MQTT. 1e, development @123 and @sheminasalam Thanks for your help. I believe the setoption30 1 is not working for me because my plugs are showing as sensor and binary_sensor (vs a switch). 3. 11. Untile here all ok, I was able to enable the auto-discovery and the devices appear on HA. Installation; Automations; or a lot of IO if there are a lot of MQTT discovery messages. yaml is working, go to HA "Settings", "Devices & services", "Entities" and search for the entities "neopool_mqtt". PROBLEM DESCRIPTION Using Tasmota 8. I wanted to add one today, the discovery message from Tasmota worked, and the device was added to All you’d need to do is setup mqtt on the tasmota device (usually only ip address is needed) and enable auto discovery. 2. Then add integration again and enable the Hello, I have followed Home Assistant - Tasmota page and set up the Tasmota integration in my HA (2021. When you switched to use Tasmota, it didn’t change the topic back - you need to fix it manually I have installed my first tasmota device today (a shelly1), but I am unable to connect it to Home Assistant. pl/home-assistant-dodawanie-tasmoty-mqtt/Link do Fanpage:https://www. All Shellys with tasmota thermostat firmware are in discovery mode and detected by tasmota integration. It works using the parameters in file xdrv_06_home_assistant. I have the mqtt broker enabled and ´discovery: true, as well as SetOption19 On` in tasmota to enable autodisco This integration will not create a device, only entities. I set it up months ago, and I think I used the option19 on it. 221 does not include %prefix% in its fulltopic. 6. This is highly recommended for MQTT broker and the MQTT integration set up in Home Assistant. Three of them are working perfectly running tasmota 8. bin does not MQTT Discovery REMOVED. Each device should have a unique Topic. Version of tasmota: 13. xxx. Hello again Okay discovery is on. Reboot everything several times. It can be used to explore and edit existing entries. 1c provides Hass Mqtt discovery for both switch and light. (HASS or Tasmota discovery - SetOption 19 0? ) Do you have Tasmota older than v9. e. Is there a documentation somewhere on how to achieve this, if you have total control over how the topics and messages are built (writing my own scripts for sensors and stuff). Ive been holding off on enabling mqtt autodiscovery because i havent wanted all my devices (particularly the esphome and tasmota ones) to get duplicated – and ive been onboard since before that was a thing. The devices still seem to communicate with one By checking which MQTT messages are published it seems that no discovery messages are published by the Tasmota devices, even after using the SetOption19 1 command. There Hello together, I recently started to add my MQTT sensors entities (which are delivered from the same micro-controller) to a new device with Mqtt discovery. i Use the serial interface and execute commands: The Tasmota project deprecated support for Home Assistant’s MQTT Discovery method in favor of their own method (that’s why you need the Tasmota integration). It will them import all the known sensors to that specific device automatically in to Home Assistant. Try these commands SwitchRetain 0 ButtonRetain 0 PowerOnState 3 PowerRetain 1 SensorRetain 1 They will be remembered and only need executing once. I can see Tasmota connecting to HA and MQTT in the console with no issues, I can see the MQTT messages being sent to HA (using Try turning discovery on in tasmota and in your home assistant mqtt integration, it should do it all for you. HyBird July 22, 2022, 1:04am 5. the problem, I cant get home assistant to find or recognise the sensors. Sleeps Hi guys! Having problems with one of my four Gosund SP111 smartplugs. Hi there I’ve just flashed the Sonoff Dual R3 with the instructions here and got it flashed easily enough, set it up as I would any other Tasmota device I’ve configured but I cannot get it to be discovered by HA / MQTT. I’ve installed two new devices with custom tasmota firmware. 0+ worked with Home-Assistant MQTT autodiscovery. Then, configure your MQTT server and TIP: It is possible Home Assistant to auto discover your MQTT server and to display it as a card with a button to configure it. I use MQTT pretty heavily in HA, with a mixture of esphome, tasmota, home brew arduino stuff, and some very custom integrations. Most changes are First, upgrade your Tasmota to the latest firmware. Tasmota ZB Bridge* - Special feature to HomeAssistant will automatically detect the new sensors, exactly how HomeAssistant automatically detect them for other Tasmota Wifi devices. I did have mqtt working previously but hasn’t been needed again until now. I can see some messages in TasUI TasUI is a zero-install device management interface web application for all your Tasmota devices. It will discover your deployed devices and allow you to set up and configure every device from a single dashboard. Setting it again no doubt prompts the status command to be sent. io. liv msbo mgew ozvkgt rqmqx rxcmq gpsy mjo wqs hnexno