Matteo Agnoletto

Hi @cstrand89, thank you for your quick feedback. The YAML for your automation looks good to me. Did you notice any entries in the Home Assistant logs while trying to...

Hi @rschoultz, thank you for your patience and for your precious contribution. I'm sorry for my late response. I'll get ahead and review your PR. :) Huge thanks to @jstorgaard...

Hi @joneric25 , thank you so much for your suggestion! I'm happy to add support for this controller to our project. :) I'll let you know as soon as a...

⚠️ Important announcement about the project: #371 ⚠️ I'd like to kindly ask for your feedback about our work here. If you have time, please answer the poll in the...

Hi @Sab44, I'm reopening the issue and linking it to #314, so we can keep track of its status once we merge the PR in `main`. Thank you for your...

This issue seems related to `next` >= `14.0.1`. Tested that this example works with `next 14.0.0`.

@flostingapplesauce the issue with the bad port should be fixed as of commit 2524a61. You could try executing `python get_token.py --ip --port ` and see what results you get. I'm...

Hi @flostingapplesauce, you're welcome! I'm happy to help as I can. :) Did you clone this repo as of the latest commit? I think this could be the problem since...

Hi @flostingapplesauce @dariob84, thank you for performing these tests, but here's where I got stuck. Unfortunately I think we have the same issue. Just for testing purposes and be sure...

Hi @AKuHAK , > After reverting this commit: 2524a61 > Everything is ok now: > We must use port 8000 for sending websocket, not the user defined port. I'm happy...