KAUF bulb not seen in HA.

[bert269]

Updated:

See below.

[bkaufx]

I don't see anything below. Where are you at on this? Once you get the bulb connected to the network, and able to access the bulb's web interface through typing its IP address in a web browser, then HA should find it. If not, I would try adding it manually as described here: https://github.com/KaufHA/common#device-not-being-detected-by-home-assistant

[bert269]

Oooops sorry.

Second device is back. I can access it via it's IP address, but still does not appear in HA.
Followed those instructions and also renamed the device.

Not in HA or even in ESPHome as a device.

First device is useless - does not even power back on after I tried the flash firmware 1.879 to it.

[bkaufx]

• Is the bulb up at 192.168.1.92?
• What do you mean by "Not in HA or even in ESPHome as a device."
• What is the IP address of the Home Assistant server?
• What do you see on the web interface for the bulb at 192.168.1.92 in a web browser? Do you see the logs and can you turn the bulb on and off?
• Are you sure the bulb is not already in Home Assistant? If you watch the logs for the bulb in the web browser and reboot Home Assistant does it say it disconnects and reconnects?
• Anything weird with your network that would not allow the two devices to see each other?

[bert269]

Yes, the bulb is: 192.168.1.92 and I can access it's web interface.
After the bulb has been configured it does not "appear in Home Assistant" as a device.
It does not show with the other ESPHOME devices as an entity on the integrations panel.

• even after I set it up manually in ESPHOME using the following configuration:
  

On the bulb's web interface I see the controls and the log, with updates when I turn it on or off.

I am certain that this bulb is NOT in HA, it is not under the list of devices and not as a device in ESPHOME like my other four ESPHOME devices..

No - looking at the log on the bulb while rebooting Home Assistant - it does not mention anything about Home Asistant. It is not in home assistant. This is all I see after logging onto the device and rebooted Home Assistant:

[bert269]

For somereason, the bulb finally showed up in HA. All that was different and changed, was the ESPHOME got updated today to the latest version.
Trying to configure the bulb, created an 'invalid flow specified' error.

is that because I ALREADY renamed the .yaml file to the correct name - "kitchen-lamp.yaml" before this integration was established?

[bkaufx]

The yaml filename really has nothing to do with anything.

I have never seen that invalid flow specified error from ESPHome and can't find any information about it.

• Maybe try adding manually now that its seen by Home Assistant.
• try reflashing now that ESPHome has updated.
• Try reflashing without API encryption and change IP address too.

[bert269]

This is truly very, very strange that the bulb is acting like this. This morning, I received a notification that 'a new device was found' - but when i click on the 'more details' = nothing shows up. It did this about three or four times - then it showed up. I managed to configure it in HA - and YES, it works. What the hell is going on - it looks like HA is sleeping or there is a huge delay setting this up for this device. OK - but let's move on - it is working and I hope it stays that way. Thanks for your help. <https://mssociety.donordrive.com/index.cfm?fuseaction=donorDrive.participant&participantID=52149&referrer=BF_emailbadge> Keep in TOUCH, with the American(-Dutch) *Live free or die hard trying...* *We may not be racing, but that doesn't mean I am not trying to beat you ;-)* Bert

…

On Wed, May 17, 2023 at 4:20 PM Brian Kaufman ***@***.***> wrote: The yaml filename really has nothing to do with anything. I have never seen that invalid flow specified error from ESPHome and can't find any information about it. - Maybe try adding manually now that its seen by Home Assistant. - try reflashing now that ESPHome has updated. - Try reflashing without API encryption and change IP address too. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEN5KABMI7XR6GCINY76EALXGVFL7ANCNFSM6AAAAAAYCX433E> . You are receiving this because you authored the thread.Message ID: ***@***.***>