Jorge Schrauwen

> There is, of course, another option: roll local PKI, and while it is probably "the correct" solution for many, marrying it with Apple TV etc. will definitely be even...

I tried with: ```python client.authenticate({"Servers": [{"AccessToken": api, "address": url, "DateLastAccessed": 0}]}, discover=False) ``` But that just results in different errors: ``` Traceback (most recent call last): File "/home/sjorge/anilist-jf-sync/venv/lib/python3.10/site-packages/jellyfin_apiclient_python/connection_manager.py", line 176,...

I gave up and ended up just doing it manually with the requests library. Although jellyfin server doesn't really seem to like just plain API token access as it shows...

TuYa implements their data layer and are essentially using zigbee as a transport layer. That's why it's not supported.

Their IoT Core docs do mention device groups, but I have no access to their wire level docs/sdk nor do I have any devices to look into this. I assume...

Hmm interesting, I notice a improvement in overall responsive ness with log set to info instead of debug when my adaptive lighting automation triggers, it causes a a bunch of...

I wonder if moving that one from info -> debug would help.

Perhaps we could introduce a 'subsystem' to the logging we can tune ? e.g. herdman, converter, homeassistent, mqtt, ... so we could then have these on different lives, samba does...

Also seeing this with a J7+, I tried the cipher change mentioned but that didn't help. Neither can I say curl the endpoint dorita980 is trying to access. I also...

@Koenkk could this be the race again were the customClusters are not yet added ? The D1 should have it, as it has the correct extend: https://github.com/Koenkk/zigbee-herdsman-converters/blob/f5ed0bfb5508a28efe507fff8d2578f39c0db4f1/src/devices/ubisys.ts#L832