ShellyForHASS: [BUG] Can't control Shelly Bulb RGBW from Home Assistant
Environment
- ShellyForHASS release with the issue: 0.2.1
- Last working ShellyForHASS release (if known): Not sure, but a Shelly Bulb appears to work in the screenshots in README.md
- Home Assistant Core release with the issue: 2020.12.1
- Operating environment (Home Assistant/Supervised/Docker/venv): venv
Describe the bug
I just bought a Shelly Bulb RGBW (SHCB-1), and after plugging it in I can only see a “firmware update” entity in Home Assistant. I can’t find a way to actually control the lights from Home Assistant.
I don’t remember what the firmware version was when I got the device, but it seems the device wants to update between 1.9.0 and the latest 1.9.3 beta release. I have also tried 1.9.2, but it has the same behaviour.
Steps to Reproduce
Have a Shelly Bulb RGBW on the network.
Expected behavior
I would expect a light.shelly_shcb_* entity show up in Home Assistant.
Screenshots
Traceback/Error logs
Additional context
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 23
@sjoerdos92 I don’t know for sure, maybe 5 days ago, for what I can suppose from the firmware version: 20210107-122133/1.9_GU10_RGBW@07531e29
@magicbenny sorry for the misunderstanding, but I was referring to the problem of frequent disconnection of the lights when changing the setting, not the automatic light detection via ShellyForHASS.
I can also confirm that RGB bulb is missing light component part. But I hardly believe I was able to use it when first connected. Although I’m not sure what version I was using. I also had some MQTT setup but I doubt this had any affect.