kandi X-RAY | Tasmota Summary
kandi X-RAY | Tasmota Summary
Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Written for PlatformIO with limited support for Arduino IDE.
Top functions reviewed by kandi - BETA
Tasmota Key Features
Tasmota Examples and Code Snippets
Trending Discussions on Tasmota
I've been searching high and low for a simple explanation for this. What configuration settings do I use to connect my Sonoff RF bridge to the Mosquitto server on my computer? I'm sure it's a configuration issue but most of the tutorials out there are for rPi. My skill level in this is basic and I'm sure it may be obvious to someone what's wrong.
I'm running Mosquitto on Windows 10 and have verified that the Mosquitto server is running using netstat -a (I can see the broker is listening at 0.0.0.0:1883.
I've installed Tasmota Eclipse on my Sonoff RF Bridge and have verified it is receiving signal from my door sensor by opening the UI in my browser and viewing the console. I've tried multiple host addresses in the configuration menu; localhost, 0.0.0.0, 10.0.0.1, however Tasmota only seems to connect when I leave the host field blank.
I've tried to use MQTTlens to verify that the broker is receiving messages on port 1883 and nothing seems to be coming through.
ANSWERAnswered 2021-Jul-14 at 10:22
0.0.0.0 is a short hand to tell mosquitto to listen on all the available interfaces on the machine it is running on. It is meaningless to use it in the client configuration.
localhost always means the same machine that the code making the request is running on, so in this case it would be the Sonoff device it's self.
It looks like
10.0.0.1 is the address of your local router, unless mosquitto is actually running on the router (it is very unlikely your windows machine is your router) this again is not going to be useful.
You need to use the IP address of the Windows machine that mosquitto is running on, this is going to start with
ipconfig on the command line in windows is probably the quickest/simplest way to find that address.
My Rpi4 running my home automation recently upgraded itself from mosquitto version 1.6.12 to 2.0.8 and as a consequence it was starting in local only mode.
Done some digging about but still can't get it all working again, mainly used this previous helpful question Mosquitto: Starting in local only mode but my devices still can't connect.
From my mosquiito log I see...
ANSWERAnswered 2021-Feb-27 at 13:39
Your problem is not that Mosquitto is not listening, it's that your devices are trying to resolve a hostname of
I suspect you have entered the host:port combination into fields that should
- Only contain a hostname/IP address
- You probably should NOT be entering
127.0.0.1as this always points to the device it is entered on and you should be entering the IP address the broker is actually running on.
Which is the best way to discover all online devices in the LAN and their corresponding device name? I thought using the LWT message that every device sends, but I don't know how to subscribe to all LWT message from unknown devices.
The LWT "Online" messages are coming through with this path:
tele//LWT, but I don't want to subscribe to ALL "tele" messages, as they are too many.
ANSWERAnswered 2020-Dec-31 at 17:19
You can use single level wildcard topics.
I am currently working on the integration of IoT devices into a cloud. Many people know the Gosund smart plugs. Just for fun, I've been playing around with the original firmware and wondering how this coupling process is solved. The Gosund sockets are based on the ESP8266 and have no Bluetooth on the hardware side, only W-LAN. The Android app starts a search process when pairing, finds the socket, sends the settings and the setup is finished. But how exactly is this solved on the software side?
I'm interested in that, because I want to reproduce the same way it is solved for our app. My first theory was that the Gosunds, similar to Tasmota, open an access point with a webserver behind it and the app sends the settings via REST calls.
For testing purposes I implemented this in a small prototype, which also works so far. But you can see with my code that the phone is changing the wifi. Open connections are closed and so on... With the Gosund app this is not the case. My mobile phone stays in my W-LAN the whole time but manages to send the settings via Wifi to the gosund plug at the same time.
How is that solved?
Alternative theory: The app opens an access point and the gosund plug tries to connect. But can Android do that? Stay logged in to a wifi and open a hotspot at the same time?...
ANSWERAnswered 2020-Apr-01 at 20:34
OK, so now I know how it works. The trick is to encode the WiFi credentials into the unencrypted header of UDP packets. The ESP then searches for exactly these packets on all available access points. This allows the device to be configured from the mobile phone without having to change a WiFi connection. This technique is called SmartConfig.
Here is explained in detail how it works: https://www.eeweb.com/profile/steve6366/articles/smartconfig-how-to-turns-an-esp8266-into-a-smart-home-device
I'm trying to connect my Tasmota switch over mqtt. i have installed mosquitto on a virtual machine, heres the configuration:
ANSWERAnswered 2020-Jan-24 at 21:10
As thrashed out in the comments, your ACL file is missing any enabled topics either for the
anonymous user or the
If you enable ACLs you need to define all the topics you want users to be able to access.
I've done my googling on this and I have really tried to fix this before posting my question here.
System: Raspberry Pi B+ (Latest Raspbian), Wifi
Problem: When I try to run this: mosquitto_pub -h 192.168.1.121 -t cmnd/DVES_1A6953_fb/cmnd/Power1 -m off I get "Error: Connection refused"
What I know: Mosquitto is installed on 192.168.1.100 (RPi) Sonoff Basic Pow is located at 192.168.1.121 I've tried with mosquitto -d. And sudo systemctl enable mosquitto.service.
mosquitto -v gives me: 1579784576: mosquitto version 1.5.7 starting 1579784576: Using default config. 1579784576: Opening ipv4 listen socket on port 1883. 1579784576: Error: Address already in use
I really don't know what else to do now :)
Hope you can help me!
ANSWERAnswered 2020-Jan-23 at 13:36
You are trying to publish directly to device (192.168.1.121) not to the broker (192.168.1.100)
You need to send messages to the broker, which will forward them to the device (Assuming it's subscribed to the right topic)
No vulnerabilities reported
Reuse Trending Solutions
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page