search

KaufHA / kauf-rgbww-bulbs

Files for the KAUF RGBWW Smart Bulbs
39 stars 18 forks source link

V1.875 wont connect to wifi. Keeps reverting to captive portal AP. #30

Open ThrashinVictim opened 1 year ago

ThrashinVictim commented 1 year ago

I also tried to go to 192.168.4.1/reset and get invalid file error.

I also tried to reset the bulbs manually.

bkaufx commented 1 year ago

Yea /reset won't work on the captive portal. I've thought about adding it. You can connect to the bulb's AP and enter credentials but they don't get saved? Is there a table at the bottom with information? What does it say?

bkaufx commented 1 year ago

I should mention I updated some of my bulbs with esphome 2023.2.0 and our 1.875 yaml and they reconnected back to the same wifi network fine.

ThrashinVictim commented 1 year ago

Yea /reset won't work on the captive portal. I've thought about adding it. You can connect to the bulb's AP and enter credentials but they don't get saved? Is there a table at the bottom with information? What does it say?

Correct, I add the SSID and password. But they never reboot and try to connect just sit there then the bulb resets and connects back to AP portal

ThrashinVictim commented 1 year ago

Is there a way to totally factory reset the bulbs?

ThrashinVictim commented 1 year ago

I also tried to upload a bin file using the ap, but as soon as I try it goes to a webpage stating invalid request

applehomekit1 commented 1 year ago

I am also having the issue with all my bulbs, I stopped updating them, and the ones i did update I had to put tasmota on them to work. I have updated my unifi APs and they still cannot see my network, they can see others. This only happened after this update. Any ideas?

applehomekit1 commented 1 year ago

For testing, I created a new wifi network with nothing but letters and numbers and no spaces, upon reconnecting to bulb, it did see the wifi, and was able to connect and control. The settings are identical to the previous network except no special characters.

bisrael8191 commented 9 months ago

I'm having the same issue with 1 out of the 3 bulbs I got to test. They're all running 1.851(f) and were all successfully connected to my SSID and home assistant. One of them no longer connects and starts it's own SSID again, when I connect and go to the web UI, reentering the correct SSID and password doesn't seem to do anything and uploading new firmware fails. I also tried to create the 'initial_ap' SSID but it won't connect to that either. The table at the bottom of the UI looks like the two working ones:

image

I tried to reset it by turning it on/off 5+ times but nothing seems to work. How do you factory reset a bulb if it won't connect to any network and I can only get to the captive portal? Was planning on getting more of these because they work great when working, but now am not so sure.

bkaufx commented 8 months ago

Can you try creating your own firmware file with your credentials built in? You would do this from the ESPHome dashboard and do manual install. Then gzip the bin file. Then upload through the captive portal. If the web interface for the captive portal isn't working to upload the firmware some people have had better luck with using the curl command.

curl -v -X POST -H "Content-Type: multipart/form-data" -F update=@firmware_filename.bin.gz "http://192.168.4.1/update"

If that doesn't work send me an email and I can send a replacement to see if it works better.

bisrael8191 commented 8 months ago

Was able to build a new firmware in esphome but uploading it still fails via curl and the webUI. Also tried the 1.87 build again (from releases: https://github.com/KaufHA/kauf-rgbww-bulbs/releases) but didn't work either. Curl log below, will also send you an email. Thanks for trying to help resolve.

curl -v -X POST -H "Content-Type: multipart/form-data" -F update=@kauf-bulb-test.bin.gz "http://192.168.4.1/update"
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying 192.168.4.1:80...
* Connected to 192.168.4.1 (192.168.4.1) port 80 (#0)
> POST /update HTTP/1.1
> Host: 192.168.4.1
> User-Agent: curl/8.1.2
> Accept: */*
> Content-Length: 359026
> Content-Type: multipart/form-data; boundary=------------------------d5fabe1a234bc9e8
>
* We are completely uploaded and fine
* Empty reply from server
* Closing connection 0
curl: (52) Empty reply from server
ThrashinVictim commented 8 months ago

Can you try creating your own firmware file with your credentials built in? You would do this from the ESPHome dashboard and do manual install. Then gzip the bin file. Then upload through the captive portal. If the web interface for the captive portal isn't working to upload the firmware some people have had better luck with using the curl command.

curl -v -X POST -H "Content-Type: multipart/form-data" -F update=@firmware_filename.bin.gz "http://192.168.4.1/update"

If that doesn't work send me an email and I can send a replacement to see if it works better.

I think I have a bad bulb. I finally got it to take the firmware, but if I leave it on for 15-30 minutes it starts flashing again. But it doesn't lose wifi because I can ping it.