[Solved] Unable to Log into Tuya Switch with OpenBeken 1.17.765 After Update

I have a strange problem. I have a light that is controlled from 3 switches. The switches are all KS-602S and one has an esp8266 flashed with Tasmota and the other two have a Tuya chip flashed with OpenBeken. I am using device groups on all three and it has been working for many months. Recently my wife attempted to turn the light on from one of the switches and the light began flashing on and off every second or two and there was nothing I could do with pressing any of the switches - it seemed like a relay race of some kind. I eventually logged into the switch with Tasmota and performed a restart and that cleared everything up and the switches began behaving normally. I probably could have logged into any of the three and done the same thing and that also would have worked.

Now comes the strange part. I noticed that the two Tuya switches had an older version of OpenBeken. I believe it was 1.17.268 and I decided to flash the latest which was 1.17.765. I flashed the first switch and after a minute I was able to log into it and it seemed fine. I flashed the second switch with the same file and the flash was successful but I was not able to log into it. The switches all worked fine, and still do. I use a program called Wireless Network Watcher from Nirsoft and all three switches show up on the network including the one that I can't log into.

Any idea why the switch would work fine but I could not log into it? I assume I could remove it from its location and re-flash it from scratch but really don't want to do that if I don't have to.

Thanks for any help or suggestions.

Bob

Try a different browser, delete the browser cache. For finding devices on the local network in my opinion AngryIP Scanner works best.

Thanks for the suggestions. I tried 3 different browsers as well as clearing the cache and I always got the message that the IP address took too long to respond.

I also appreciate the suggestion of Angry IP Scanner. When I installed and ran Angry IP Scanner, the IP address that I cannot log into definitely shows up as active. The thing I noticed that most of the ping responses were in the 30 to 40 ms range (although there were some in the 200 to 300 ms range); the IP address in question was in the 1700 to 1800 ms range. Not sure what, if anything, that tells me.

I may just have to remove the switch and flash from scratch.

Bob

You can also try safe mode. If device is restarted 5 times without fully starting up, it starts safe mode (with an open AP) and you can connect a WiFi client.

So just restart after one or two seconds and after 5 restarts you should see the device as an WiFi-AP...

Another good idea but I still have to remove it from the electrical box in the wall to do that. If I switch the breaker on and off it will put any other switch in that same circuit into AP mode as well. I will remove the switch from the box and try this method, and if that doesn't work, will just re-flash the chip.

Thanks for the ideas. I will report back when I have fixed this.

Bob

Just another hint, not sure if it can help:

You can access the logs of a device without the gui (in case this works) and maybe get some hints on why the gui isn't accessible.
The logs are available on port 9000, some ideas on how to access them in this thread

https://www.elektroda.com/rtvforum/topic4078451.html

I'm not sure I ever really solved this problem. The switch in question was in a box with three other switches that I could log into without any problems. I removed the switch in question and replaced it with a spare and the spare worked fine. I could log into it normally. When I took the questionable switch down to my bench and powered it up, I could now log into it normally as well. At some point in time I will install it in another location to see if it works there. But for now it is time to move on.

Thanks for the suggestions, especially for Angry IP Scanner.

Bob

I never really solved - just moved on as per my last post.