search

KaufHA / kauf-rgbww-bulbs

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

Bulbs getting Adopted after already adopting #5

Closed Exit2Studios closed 1 year ago

Exit2Studios commented 2 years ago

I've gone through and updated the firmware on some bulbs that shipped pre 1.72. I adopted them into esphome and changed the config, renamed the yaml file, etc. However, I'm getting the following duplicate entries for each of those bulbs (and unable to adopt if I try). How do I get this to go away? image

KaufHA commented 2 years ago

Did you compile the firmware and flash to the bulb? If not, then the old firmware is still running and being found in addition to the yaml file.

Here's what I have when I adopt but don't install:

image image

The green one is shown due to the firmware running on the network broadcasting its dashboard import capability. The red one is due to a yaml file in the config directory. It's red because there is no corresponding device found on the network. Only once I "update" the adopted bulb then ESPHome doesn't see the old firmware available to adopt.

If you did already flash new firmware to the bulb then I'd try deleting the ".esphome" folder within the esphome config directory. Maybe something is cached funny.

KaufHA commented 2 years ago

Actually, even without updating the firmware I got the green discovered card to go away just by compiling the firmware. Maybe viewing logs would work as well.

Exit2Studios commented 2 years ago

Yes, I compiled and wirelessly uploaded to the bulb. Everything is working fine (the new esphome entry is working and is integrated into HA). However, the green discovered is still there. I'll try deleting .esphome.

KaufHA commented 2 years ago

Maybe restart the esphome addon or dashboard as well when you delete .esphome