I see there seem to be a lot of automation developments over the past months and I imagine more are to come in the future. I’ve used node red for my automations (only because I wanted to teach myself node red) but I’m wondering whether I should continue with it or move over to HA’s native automation mechanism. Would any of the key developers offer any advice on this? Thanks
Thanks for the update.
I’m not sure if it’s a wrong configuration from or a bug.
I have multiple modbus configurations in different files / packages. Everything configured as mentioned in the docs. Before the update it worked afterwards it seems like they overwrite each other. The one that was included last counts the other ones are not recognized.
Same situation for knx works like expected.
1 Like
So these errors does have an impact none of my Smart Plugs reports current Power back.
Device:
lumi.plug.maeu01
Gateway:
Conbee II
No changes has been made on Device or Gateway.
Any help would be appreciated.
I am seeing the same issue with my ZHA integration. My post with screen shot is above… if anyone has any ideas that would be great.
also having problems with ZHA after upgrade to 2021.7.1. I hope that this PR will be included in next release and fixes the issue.
For the moment I downgraded to 2021.6.6 again
should be fixed in 2021.7.2 when released. Bump deCONZ dependency to properly handle current and voltage not being reported on some zhapower endpoints by Kane610 · Pull Request #52764 · home-assistant/core (github.com)
1 Like
Suggestion on best route to do that with a Pi set up?
Doing what? downgrading?
Correct. I’ve never had to do that before didn’t know if you had a good resource off the top of your head since you just did it. If not I’ll explore.
Thanks!
It’s really easy. Go to your supervisor then snapshots. Select a snapshot from previous 2021.6.x version and click on restore
This is because there is also difference in knowledge between devs. If a higher voted FR is not developed yet it could as well mean that there are fragments not developed because the developer with that skill has some more pressing manor to attend to. It could be number of things.
Thanks for the help. Rolled it back a version but it appears the error still persists. All of my automation appear to still be working and I can create new ones… So not sure what exactly is broken or causing the error here.
Anybody have success with installing the Ambee integration. I have an APi key, but at a loss to know what I must fill in for a Name. Just keep getting invalid api key.
He doesn’t but I do like when I get a meaningful reply.
Which is not to imply I don’t get one often, I do, I just think it is nice to acknowledge it even if I don’t like the actual answer 
1 Like
I worked around this issue by pulling zwavejs2mqtt “master” instead of “latest” in my docker-compose file. Once there is a new formal release of zwavejs2mqtt, then the reco will be to switch back to “latest” to get a stable version as master could break anytime.
Thank you, this worked for me
SOLVED. For raspberry user ( core mode)
Disinstall FFMPEG
sudo apt remove ffmpeg
Compile FFMPEG from source
wget http://www.ffmpeg.org/releases/ffmpeg-4.4.tar.xz
tar xf ffmpeg-4.4.tar.xz
cd ffm*
./configure --enable-shared --enable-pic --extra-ldflags="-latomic"
make -j4
sudo make install
In venv install av
pip3 install av
modify configuration.yaml
ffmpeg:
ffmpeg_bin: /usr/local/bin/ffmpeg
bye
This update broke my duckdns - NGNIX https access. Had to revert. Anyone else? Local works.
There is a breaking change to do with trusted proxies when using a reverse proxy. This example worked for me.
Did you enter that code via the Nginx Proxy Manager gui, or in a yaml file. Thanks.