Rafal Pietrzak

Hi! Just found a solution (after checking whole documentation - I have found nothing). Documentation provides endpoint `/users/activate/` for "User Activate". I have walked through the djoser package files from...

it happens to me on Ubuntu 22.04, psycopg2-binary and newest stable Django + newest stable celery. Trying to find the reason, it seem to be running while handling massive amount...

Seem that changing the type to simple instead of forking and disabling multi solves it (source: https://sam.hooke.me/note/2023/01/celery-and-systemd/)

Same issue here unfortunately (with exact same errors); using docker-based image of newest HA on my Synology NAS. Did you manage to fix this? I'm trying to reverse engineer it...

I've just tried again. 1. Added Lines to my configuration.yaml 2. Updated the zte_tool.py #300 to my credentials 3. Uploaded the sensors, python_scripts, command_line and switch folders to my main...

I did it inside of my docker terminal of the home assistant and got this. Maybe I did it wrong? homeassistant-home-assistant1:/config# python python_scripts/zte_tool.py Traceback (most recent call last): File "/config/python_scripts/zte_tool.py",...

I've manually changed the ha_select to 3 (zteInfo) ha_select = 3 instead of ha_select = int(sys.argv[1]) Now the output is actual data from the router. `{ "wa_inner_version":"BD_PLKPLMC889V1.0.0B13", "cr_version":"", "network_type":"ENDC", "rssi":"",...

Ah, right. Actually I get the response as above, so it seem to be working. Although all sensors have unavailable / unknown data. My HomeAssistant log says this:

Still doesn't work unfortunately