You can do a factory reset on the device (which usually is done by holding the button on it for 25 seconds), or temporarily disable or change the ssid name of the current router it connects to. If it can't connect after a few minutes it should pop up with the built-in AP and allow you to reconfigure it.
1 Like
@ericm Do you think blacklisting it in the AP would do the same?
Yes, I think so. If it hasn't started re-broadcasting after 5-10 min, you might try to plug / unplug.
Yes, it works! Simple fix to changing wifi creds.
Now after all that, I'm thinking of trying to add the Tasmota firmware into the mix...
1 Like
Reviving an old thread... Anybody still using this app/driver combo? I am...
Subject to correction, I am using the ORIGINAL App
- Sonoff (Connect)
- Author: Eric Maycock (erocm123)
- Date: 2016-06-02
I also believe I am using the ORIGINAL Driver - Sonoff Wifi Switch
- Author: Eric Maycock (erocm123)
- Date: 2016-06-02
(If somebody want the source for both ping me)
The app/driver has been working flawlessly up to and including version 2.3.4.123
I recently upgraded to 2.3.4.128
I unfortunately noticed way too late I am now getting this in the logs; too late because I made many changes that I will lose were I to roll back.
Warning:
[sys:1](http://192.168.60.2/logs#)2023-01-04 09:03:42.623 AM[warn](http://192.168.60.2/logs#)Received data from 192.168.60.20, no matching device found for 192.168.60.20, C0A83C14:76D4, ECFABC06657E or C0A83C14.
This is happening for all 3 of my Sonoff devices.
Note: the devices still work just fine in Hubitat!!! Needless to day 192.168.60.20 is a valid, pingable, functioning Sonoff device. The Hub & all IOT devices are all on the same subnet.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
