Hello @frenck,
I have a question about the new netgear integration.
How is the security of the username/password in the netgear integration, because in the past you had to save that in the secrets.yaml file?
I fully support the HA team’s work to bring vendors closer to the great work they are doing and their efforts with the Tuya integration.
I for one however, having gone through the new integration and associated sign up have decided its time to pull the plug on the few devices I have left on this platform. I don’t see how Tuya expect this would work for a mass market (or indeed they don’t want it to) but things should be getting smarter and easier – I see this as acknowledgement by them that projects like Home Assistant could be a threat but not enough of a threat for them to fully come on board with the ethos and aims, rather keep them close enough to watch. I maybe wrong and happy to stand corrected in time but currently there are better solutions for my needs.
3 Likes
My RPi4 CPU usage went from 6-8% to 35-40% after upgrading to 2010.10.0. Is this a known issue and is there any way I could help debug it?
Turned out it was Zigbee2Mqtt addon going crazy for some reason. When I restarted it things went back to normal. I wonder why it reacted this way to updating Core.
Source: components/tuya/__init__.py:95
Integration: Tuya (documentation, issues)
First occurred: 4:13:52 AM (1 occurrences)
Last logged: 4:13:52 AM
Tuya login error response: {'code': 2007, 'msg': 'your ip(71.255.105.xx) cross-region access is not allowed', 'success': False, 't': 1633594432043}
Dang it! I thought I folllowed the directions (which were really nuts!)
1 Like
Go ask tuya.
I saw that too. A second restart solved it for me too (I’m also using Zigbee2MQTT).
I’m using home assistant core and Z2M with npm (no addon). My CPU load is very high, my only solution was a rollback to 2021.09.7
Did you try restarting Z2M?
I deleted all integrations and started from a clean db. I restarted every single service. I restarted the raspberry, no change unfortunately
Nanoleaf integration stop working after upgrade to new Tuya integration.
Updated my HA to 2021.10 and the Tuya integration stopped working, as expected. Everything else was good. Uninstalled the old Tuya, made reboot and installed the new Tuya integration, got through the setup and it workes perfectly.
After a second reboot, just to be sure my HA can reboot after the change, the Nanoleaf integration never starts. This have been working with no error since it was UI enabled some time ago. I get the error
Logger: homeassistant.bootstrap
Source: bootstrap.py:413
First occurred: 11:19:38 AM (9 occurrences)
Last logged: 11:27:39 AM
Waiting on integrations to complete setup: nanoleaf
Anybody else have seen anything like this. Any ideas?
I have not deleted/re-installed the nanoleaf integration yet, will try this evening unless some other solution.
EDIT: After deleting 1 of the Nanoleaf devices, the one mentioned in the logs, the rest of the nanoleaf devices now work. Also the Tuya works.
The error must be related to something else.
I dont have the tuya integration, but the Nanoleaf integration is working fine here after the upgrade
As its not tuya based not sure how tuya could affect it
After upgrading to 2021.10.0, some of my ESPHome based lights and sensors have duplicated entities with _2’s appended. I’m integrating them using the HA API and not MQTT.
Also, my GUI configured TP-Link HS220 now has a duplicated _2 entity.
I’ll try to dig further and share my logs. The _2’s happened upon installing the update.
Most of my automations have broken as a result.
I’m on Home Assistant OS 6.4, supervisor-2021.09.6 and core-2021.10.0.
@frenck I’m running HASS from a python env and i updated each time a new update came out however today i cannot update 2021.10.0.
i get this after running python3 -m pip install --upgrade homeassistant in the correct container:
error: can't find Rust compiler
If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.
To update pip, run:
pip install --upgrade pip
and then retry package installation.
If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.
This package requires Rust >=1.41.0.
----------------------------------------
ERROR: Failed building wheel for cryptography
Failed to build cryptography
ERROR: Could not build wheels for cryptography which use PEP 517 and cannot be installed directly
i cannot update pip because HASS requires an old one. full log here
1 Like
Had to switch to MQTT-server for Z-wave over IP. WS-server not supported.
After a few restored snapshots in this process I see the Energy history from my grid is gone (not z-wave related).
I assume “Energy” does not save it’s history in Snapshots/Backups?
Thanks to the team for this upgrade!
All seems to work like before, just (also after restarting) about 10% extra ram usage. But nothing I’m worrying about.
Also, the Tuya integration won’t make me buy any new Tuya stuff soon… let’s hope for some serious improvements in the (near) future. Especially on the local part.
1 Like
Please give the old version of tuya back as a second option of integration if possible (TUYA1 and TUYA2)
The new api is not Ok this means i need to stay on the old version of HA . If i update many things go wrong or don’t work anymore. This makes HA not useable anymore for a lager part in case.
I can solve by installing Homebrigde on top of HA and work around a few things.
First time i do not experience the new version of HA as an upgrade.
- i don’t want my devices in a cloud somewhere in the world
- I’m not sure what is going to happen after 1 year of subscription.
Want to be in control myself.
Thank you Sorry for being negative
you can grab the tuya folder from old release and load it as custom… was the old tuya local btw?
or instead you can use the localtuya integration
no you cannot
why not? why isnt it possible?