Feedback - the changes to pigpio Daemon PWM LED daemon 1.5 broke my home ventilation system. They were functioning via variable speed functionality of PWM extraction fans. I built a custom interface to do this. I reverted to 1.4 and rebooted. Now it is working again, I did not investigate root cause as GPIO is being deprecated in HA. I wont upgrade again until I am clearer about support for using GPIO on the same Pi as HA. Fully variable fans - controlled by a low voltage PWM signal, are easy enough to integrate via the GPIO interface and the PWM outputs from a Pi. I thought I could move to a Zwave PWM controller, but these look like they will not work (for various reasons). My options could be bringing up a second Pi for this purpose and integrating with MQTT, or moving to (3) speed fans and a Zwave switch.
Since nothing has changed the reason it’s not working for you right now is not the depreciation.
As the documentations say, 2022.06 is when it will be removed.
I’m also getting:
Configuration of the Version platform in YAML is deprecated and will be removed in Home Assistant 2022.4; Your existing configuration has been imported into the UI automatically and can be safely removed from your configuration.yaml file
I’m looking at the configuration.yaml file and I can’t figure out what needs to be removed. There is not string “version” (regardless of case). What needs to be removed?
I would like to know about this as well.
version: is part of default_config: so maybe the error is being generated from that. Either way as long as you don’t have version: in your config you should be fine (now found in the Integrations UI). I’m sure they will fix the error generation.
Actually version: is not in default_config
updater: was, but is deprecated and has been removed from default_config in 2022.3.0.
Yeah sorry. I was questioning myself as I typed it!
I had to look it up three times while posting my reply. I have so many tabs open it becomes even more confusing!
Scenes now have states. What would i put in my trigger for an automation to fire based on scene being activated? i have tried on, active, reloaded… not triggering… The logbook just shows the date when i look. Anyone using this?
The state is the time it was last activated, so when the state changes is all you need.
e.g.
trigger:
- platform: state
entity_id: scene.lounge_lights_on
Perfect, thank you
Out of curiosity, the ESPHome addon has been deprecated (No longer publish updates to Hassio Community Addons by jesserockz · Pull Request #51 · esphome/home-assistant-addon · GitHub) which was announced in February’s release (Mark ESPHome addon as deprecated by jesserockz · Pull Request #392 · hassio-addons/repository · GitHub)
I’m curious why it’s moved from being a community add-on to be a completely separate repository - if anything I would have thought it would be an official add-on now. I also cannot find where this was announced as per the pull request.
Thanks koying - tbh I didn’t even think of looking at the esphome release notes… That answers all my questions!