Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not connect to SSID #661

Open
bigboigahoy opened this issue May 5, 2024 · 4 comments
Open

Could not connect to SSID #661

bigboigahoy opened this issue May 5, 2024 · 4 comments

Comments

@bigboigahoy
Copy link

bigboigahoy commented May 5, 2024

I have several Merkury bulbs (MI-BWXXX) that seem to loop during the AP step. Below is from a Merkury MI-BW904 on v1.0.1

Wiping NetworkManager configs
Scanning for open Tuya SmartLife AP
......
Found access point name: "Merkury-5D5E", trying to connect...
Device 'wlan0' successfully activated with '9ad44e5a-7b66-40d6-8d4b-9a9af8b11a26'.
Wiping NetworkManager configs
..
Found access point name: "Merkury-5D5E", trying to connect...
Device 'wlan0' successfully activated with 'ce25e59a-da96-4a39-98b9-25914652566c'.
Wiping NetworkManager configs
..
Found access point name: "Merkury-5D5E", trying to connect...
Device 'wlan0' successfully activated with '43c8b23a-758e-43e8-9c8a-53bc16639e32'.
Wiping NetworkManager configs
...
Found access point name: "Merkury-5D5E", trying to connect...
Device 'wlan0' successfully activated with 'be5d9eda-88a4-4109-a7b2-a9b56c01679d'.
Wiping NetworkManager configs
..
Found access point name: "Merkury-5D5E", trying to connect...
Device 'wlan0' successfully activated with 'd33cb2de-8f40-4082-b7e4-12f20b270e52'.
Error, could not connect to SSID.
Failed to connect, please run this script again
@Cossid
Copy link
Member

Cossid commented May 5, 2024

  1. Make sure the devices are nearby enough to each other
  2. Try running with the -r parameter if you're not already

This is an issue with NetworkManager not able to fully connect it appears

@bigboigahoy
Copy link
Author

bigboigahoy commented May 5, 2024

  1. Make sure the devices are nearby enough to each other

    1. Try running with the -r parameter if you're not already

This is an issue with NetworkManager not able to fully connect it appears

I moved the devices closer and I still have the same issue. I was able to get some of the bulbs working correctly, it seems the MI-BW904 is giving me problems specifically. I was using the -r parameter as well.

Edit: I got quite a few of them to work. I am down to 4 bulbs that have this error. All the same model, the Merkury MI-BW904.

Edit 2: I put the device directly next to my Raspberry Pi 4 and I still get the same error.

Edit 3: All 4 of the devices left are the Merkury MI-BW904 (BK7231T). 3 of them are on v1.0.1, while 1 of them is on v1.2.3 . Strange these aren't working given there was another 904 in the mix that did work on a higher firmware.

Edit 4: I went into a VNC session and can see the Pi is connected to the bulbs AP after the script fails.

Edit 5: I had one more light with the same model Merkury MI-BW904 (BK7231T) on v 1.0.10 and that one worked. Anything on v1.0.1 goes through the AP loop and then this error.
Error: Connection activation failed: (0) No reason given.
Error, could not connect to SSID.
Failed to connect, please run this script again

@akintash
Copy link

akintash commented Jun 5, 2024

The same issue with Hombli_HBSS-0209-Smart-Socket-B2030248-Energy-Plug.
FW version 1.0.2.
Tried different WLAN adapters (Broadcom and Realtek), issue happens on both of them.

@bigboigahoy
Copy link
Author

bigboigahoy commented Jun 11, 2024

The same issue with Hombli_HBSS-0209-Smart-Socket-B2030248-Energy-Plug. FW version 1.0.2. Tried different WLAN adapters (Broadcom and Realtek), issue happens on both of them.

I wonder if there is a firmware bug that effects these. I have had success with numerous other devices as well as the same device, just not this specific firmware.

Edit: I did get a different error:
Found access point name: "Merkury-B789", trying to connect... Error: Connection activation failed: (11) 802.1X supplicant took too long to authenticate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants