-
Notifications
You must be signed in to change notification settings - Fork 75
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
Comments
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. |
The same issue with Hombli_HBSS-0209-Smart-Socket-B2030248-Energy-Plug. |
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: |
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
The text was updated successfully, but these errors were encountered: