On the yeelight integration documentation page, there is a list of ‘known working devices’ and its missing yeelight filament bulb - which I have bought prior to checking the list. It does, however, support LAN control mode and thus there should be no problem in controlling the bulb - however adding it to my HA config file does not work (HA loads, but the entities are not present). Is there a way to “make it work” - since according to what i found it supports exactly the same syntax as other LAN controlled yeelight bulbs, i assumed there would- ?
Just to let you know, i just found a solution - https://flows.nodered.org/node/node-red-contrib-yeelight does work without any problem with my yeelight filament bulbs, thus now it is just a question of creating a virtual light in HA and connecting it to a nodered workflow. It is a bit of a jenky workaround, however I think if your light also follows the standards in https://www.yeelight.com/download/Yeelight_Inter-Operation_Spec.pdf, then you should be able to simply point the node to IP of the bulb and port 55443 to get it working.
Of course there are workarounds. Either through Node-RED or Apple Homekit Controller. I opened an issue for having the device supported directly through the Yeelight integration. Don’t hesitate voting if you find it useful.
I don’t know if anyone already did something about it, or black magic, but just today the lights appeared in home assistant - out of the blue after a restart they were present.
There is one minor issue, which is that they pretend as if temperature could be set, which is not true, so they probably register as a different model under HA.