Please see screenshot of the Tasmota Edge Driver. Note the Gateway IP Address (169.254.x.x). The ST Hub is actually at 192.168.x.x. Rebooting the ST Hub will result in the correct Hub IP address (192.168.x.x) appearing in the Driver and the ability of ST to communicate with the Sonoff Plug.
The 169.168.x.x address is apparently reserved for “Automatic Private IP Addressing” which made me think about how my ST Hub is connected to the router. The Hub is connected to the router via a network switch. As a test, I connected the Hub directly to an Ethernet port on the router and rebooted everything. The Tasmota driver loaded with the correct Gateway IP address and everything worked correctly. Repeated 3 times, same result. I then connected the Hub through the network switch, rebooted everything and again the incorrect 169.254.x.x address was loaded into the Tasmota driver and I was unable to control the Sonoff Plug. So, somehow the use of a network switch is impacting the IP address of the Hub in the Tasmota driver.
As most ISP provided routers have a limited number of ports, necessitating the use of a switch, it would be ideal to resolve this issue.
Thank you.
This appears to be a network issue/configuration, where the switch or router is unable to assign a correct IP address (192.168.x.x) to the ST hub when the ST hub is connected via the switch.
The IP address you get is what the ST hub gets from the network.
I have multiple network switches and my ST hub is connected through a network switch too. All devices are assigned the correct IP addresses (192.168.x.x) under the router.
I’m afraid I’m unable to assist you, because this is not an Edge driver issue.
This only happens when the router, network switch and ST hub are booting at the same time. It sounds like a timing issue around when you are getting the IP address from the ST hub when everything is booting up at the same time. After everything has fully booted, the ST hub has a valid IP address. And if I reboot the ST hub only or remove and reinstall the Tasmota driver, the driver has the correct IP address of the hub. So the switch and router are assigning the correct IP address as long as they have fully booted up. I am not having this issue with other network connected devices and drivers.
Which LAN edge driver is able to get the correct IP address of the ST hub? I’d expect it not able to, as I believe we use the same method from ST documentation.
I am having some issues trying to add a 2-gang metered switch. After adding, when I turn on and off, it doesnt turn switch on/off, even though the status changes in the app and in the event log.
Shows switch is on, shows voltage, energy consumption. The switch though, connected to a socket next to me is not on.
This one shows the history.
Shows the IP address - 192.168.1.243
From browser I can connect to the IP address and can actually turn on each socket using the toggle switches. So, the IP address is correct in my Smartthings configuration.
What am I doing wrong or missing ? Any help would be greatly appreciated.
I have a second dual switch still running old Tas
Do you happen to have the Tasmota username & password enabled on the Tasmota device?
If so, you’d have to remove it because it’s not yet supported in Tasmota Edge.
When you turn on/off from the app, it will appear in the Tasmota console ( http:// IP /cs? ).
Which LAN edge driver is able to get the correct IP address of the ST hub?
The DSC Security System/Envisalink Driver (2021) by TAustin
Local Bond Bridge Edge Driver by blueyetisoftware
So to be sure I was giving you accurate information, I retested. Connected the ST Hub to the switch instead of the router and rebooted everything:
- The Tasmota driver again had the wrong IP address for the ST Hub and didn’t work.
- The DSC Envisalink Driver does not show the ST Hub address but it functioned perfectly.
- The Bond Bridge Driver did not work and was showing offline and I waited for a few minutes to see if it would reconnect on its own, which it did not. Note that this driver does not require a static IP address.
Connected the ST Hub directly to the router, rebooted everything and all three LAN drivers worked.
After removing the password this is what I see.
- When I turn on and off from console, the switch turns on and off, and the status is reflected in ST. I console also shows the on and off status. Below example is turning off switch 1 from the console.
19:49:31 RSL: stat/sonoff/RESULT = {“POWER1”:“OFF”}
19:49:31 RSL: stat/sonoff/POWER1 = OFF
19:49:31 RUL: POWER1#STATE performs “WebQuery POST {“Mac”:“XXXXXXXXXXXX”,“STS”:{“POW1”:“0”}}”
19:49:31 RSL: stat/sonoff/RESULT = {“Command”:“Unknown”}
When I try to turn on the same switch 1 from ST, all I see in console is:
19:53:26 RSL: stat/sonoff/RESULT = {“Command”:“Unknown”}
The status in the ST App turns to on, and then once refreshed from console, goes back to off.
Success report: Teckin SS30 (ESP8266) 5 port switch.
It worked, but I had to edit the IP address myself. My network is 192.168.4.XX.
It sees the 5 switches but not the LEDs or the button, although Tasmota can see both.
Teckin SS30
Teckin SS30-1
Program Version 12.1.1(tasmota)
Build Date & Time 2022-08-25T11:33:55
Core/SDK Version 2_7_4_9/2.2.2-dev(38a443e)
Uptime 0T00:18:37
Flash write Count 356 at 0xFA000
Boot Count 131
Restart Reason Software/System restart
Friendly Name 1 Teckin SS30-1
Friendly Name 2 Tasmota2
Friendly Name 3 Tasmota3
Friendly Name 4 Tasmota4
Friendly Name 5 Tasmota5
AP1 SSId (RSSI) BadgerNetBase (98%, -51 dBm) 11n
Hostname TeckinSS30-1
MAC Address 68:C6:3A:C2:76:8A
IP Address (wifi) 192.168.4.XX
Gateway 192.168.4.1
Subnet Mask 255.255.255.0
DNS Server1 192.168.4.1
DNS Server2 0.0.0.0
HTTP API Enabled
MQTT Host
MQTT Port 1883
MQTT User DVES_USER
MQTT Client DVES_C2768A
MQTT Topic tasmota
MQTT Group Topic 1 cmnd/tasmotas/
MQTT Full Topic cmnd/tasmota/
MQTT Fallback Topic cmnd/DVES_C2768A_fb/
MQTT No Retain Disabled
Emulation None
ESP Chip Id 12744330 (ESP8266EX)
Flash Chip Id 0x1440C8
Flash Size 1024 KB
Program Flash Size 1024 KB
Program Size 624 KB
Free Program Space 376 KB
Free Memory 24.8 KB
It appears that you are using an old/modded Tasmota firmware, please flash with the latest Official Tasmota firmware, reset configuration, and delete/add device again.
When it had the wrong IP, were you able to access with the < “right IP” >:< port > on your browser?
Yes, but it was very slow to toggle and update (5 to 10 seconds). The console was full of error messages regarding that phantom IP address at 169.x.x.x If I then removed the ST Hub from the network, it responded instantly and the error messages stopped.
Thank you, that worked. Didn’t even have to reset configuration or delete/add device.
Are you using this template for Teckin SS30?
I don’t have the SS30. Can I have a screenshot of the Tasmota page and the result of http://ip/cm?cmnd=status 0 ?
Unfortunately, I’m unable to come up with a solution for the driver as the IP address is coming from the ST hub, which is assigned from your network. And this is necessary for Tasmota Edge and Tasmota devices to operate properly.
You may want to consider trying with another router and switch.
Okay, understood. I appreciate you looking into this. Perhaps if others report this issue, you can revisit. In the meantime, I will connect the ST hub directly to my router and I may try a different switch at some point.
I would like to know if there were any changes this week (especially on the weekend) in the driver, it would refer to the use of hub ir (virtual fan), the fan was working (turning on and off) and now it is not. And not only this problem, but a friend reported that (virtual fan) using radio frequency hub also stopped working. When entering the device, the option to enter the IR code does not even appear
The virtual fan (and some other devices) wasn’t intended to be released as they are under testing. A regression bug in the SmartThings app allows user to create them.
You’d have to delete them first but the good news is a new update is being pushed out which will include virtual fan and virtual switch. I’ll add the instruction for them soon.
Tasmota Edge Update!
- Added support for latest Tasmota v12.1.x
-
New - Virtual Switch and Virtual Fan devices
- Send IR or RF code via an IR or RF Bridge to control IR / RF device
- Use the Web Gateway to manage the IR / RF codes.
-
New - Web Gateway
- Local web access to view all your installed Tasmota devices and additional setting for virtual devices.
Update will automatically be pushed and installed to your hub. Version: 2022.9
Virtual Switch, Virtual Fan - Send IR or RF control code via an IR or RF Bridge to control an IR / RF device
Manage the IR / RF codes via the Web Gateway (see below for instruction on how to access.)
.
Web Gateway
Web Gateway lists all the Tasmota devices, and has additional configuration for virtual fan and virtual switch.
To access the Web Gateway, get the Gateway address from the Tasmota Edge device in SmartThings App.
Do note, the Gateway address changes frequently, make sure you get the latest Gateway address from Tasmota Edge device.
For example, it is http://192.168.1.208:44189 (screenshot below); access it on your browser.
Are you going to create also a Virtual Button as before? it was quite handy for inserting a Sonoff RM 433 controller.