0.91: More streaming, better Zigbee, cameras with ESPHome

Hi all, I have some Annke cameras that work with VLC and some other programs with the following url format:

rtsp://IPaddress:554/user=username&password=mypassword&channel=1&stream=0.sdp?real_stream--rtp-caching=100

I tried this with stream_source and a generic camera with no luck. I had a play around using the username and password variables with no luck. Does anyone have a similar setup working?

Getting an error trying to update hassio from 0.90.2

19-04-04 12:28:11 ERROR (SyncWorker_2) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.91.0 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.91.0: No such image: homeassistant/qemux86-64-homeassistant:0.91.0").

Looks like the image is up on docker hub

Never had this issue in the past, any ideas?

androidtv is throwing an error after upgrade

2019-04-04 08:44:10 ERROR (SyncWorker_28) [homeassistant.util.package] Unable to install package androidtv==0.0.14: Failed building wheel for pycryptodome

python-jose-cryptodome 1.3.2 has requirement pycryptodome<3.4.0,>=3.3.1, but you'll have pycryptodome 3.8.1 which is incompatible.

pyrebase4 4.3.0 has requirement oauth2client==4.1.2, but you'll have oauth2client 4.0.0 which is incompatible.

broadlink 0.9 has requirement pycryptodome==3.4.11, but you'll have pycryptodome 3.8.1 which is incompatible.

Command "/usr/local/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-bi2pd0mu/pycryptodome/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-jb1wtcu7/install-record.txt --single-version-externally-managed --prefix --compile --user --prefix=" failed with error code 1 in /tmp/pip-install-bi2pd0mu/pycryptodome/

2019-04-04 08:44:10 ERROR (MainThread) [homeassistant.requirements] Not initializing androidtv.media_player because could not install requirement androidtv==0.0.14

Just saw a’HA can’t check for updates’ error in my log so there’s something amiss.

Any news if the problems with Totalconnect will be fixed? Its been down since 0.90.0. There was an updated on 0.90.1, but it didn’t seem to fix anything. I’ve been looking forward to all these updates, but I keep having to revert to 0.89.2.

have you logged the issue on github?

It looks like ZWave Node / entity renaming is lost in this release? And there is also no additional information anymore in the dev commands service section for zwave commands, like “zwave.rename_node”. Is there something lost with the zwave integration? It is quite important to still have the ability to change node/entity names. Thanks anyhow for the hard work! Looks just a little like a breaking change with the zwave integration.

Anmerkung%202019-04-04%20152057

The config/edit button has gone in the upper right corner?

This is usually a matter of having available space. The image is there at docker hub but your instance had a problem pulling it down, so “no such image” exists on your installation. Check your free space quickly using df -h from the console.

2 Likes

interesting I’ll check this out

Thanks!

unfortunately that breaking change started 15 versions ago.

It was originally removed from the z wave control panel in around version 76 or so. I’m surprised it lasted this long as a service, TBH.

I definitely don’t agree with it but my dissent has fallen on deaf ears so there is no way it’s ever getting changed back again.

Thanks @finity. However, I was able to do so with rel 90.2 just yesterday;-) Any idea what is now the way to change the zwave node/entity names?

That was it!

Thanks again

FWIW, there’s another person who mentioned it in the following thread and it may be more widespread than just zwave-related entities:

I can’t confirm because I haven’t installed 0.91 yet.

yes, you could still do it from the services page but not from the z wave control panel section in the configuration area. That was removed a long time ago.

And, yes, the service has likely been removed now with this release.

And, lastly, if that service has been removed then there is currently no way to rename a z wave node from within Home Assistant.

I’ve thought about using a standalone version of Open Zwave Control Panel but I haven’t had the need to do anything with my nodes (no new devices to configure) so I’m not sure how/if that will work in association with HA.

Yea I mentioned it as part of # 22229. It was closed. Would a new one have to be open if the fix never actually worked?

UPDATE: ZWave is working stable and entities can be renamed via the entity regiter section. I recall my original statement. However, every time a little heart attack after upgrading when some UI processes changed without notification for users which dont follow the community for years. And requires 45min of googling to check what really happend after an upgrade;-) Anyhow, thanks for all your hard work, support and progress. I love HA!

Original comment:
Ok. If this is the case. Sounds like zwave support is deprecated and HA is pulling the plug of zwave integration. If you cant rename entities, makes no sense to have this integration when working with more than +5 zwave devices from same manufacturer. Looks like moving to a 3rd party zwave solution instead of using the zwave HA integration…?

That’s a massive jump in logic. If that feature was removed on purpose (big if, no confirmation yet), it has nothing to do with larger z-wave support.

You can still rename all of the child entities created by the zwave device individually, one at a time…, thru the entity registry for the specific entity.

you just can’t rename the entire node and have all of the children entities carry the node name down to the entity_id. It’s still a problem as far as I’m concerned but that’s the way it’s going to be.

And yes, it was removed intentionally. At least the functionality in the zwave control panel was and there have been discussions that stated it would be removed from services in the near future, as well. I can only assume that “the near future” is now.

But I don’t believe that zwave support is going away.

All my Cogs are gone as well from 0.90.2 to 0.91 but I have found that going to the Entity Registry allows me to still change name. Agreed it’s annoying to have to go there but at least functionality isn’t lost.

I however still see “zwave.rename_node” chrome_ZSa5EllXYc

Running 0.91.0, zwave.rename_node service still an option in services.