Lucas Held

I have developed an Ansible collection of modules to configure Uptime Kuma with Ansible. Currently monitors, notifications, proxies, tags, monitor tags and status pages are supported. https://github.com/lucasheld/ansible-uptime-kuma Under the hood,...

Here is a full example. First you need to add the monitors themselves. Then add a status page and save it with the `publicGroupList` parameter. It consists of a `name`...

I also have the same problem. I am using WS2801 LED strips with an ESP32 dev board and a LAN8720 module. The GPIO pins were connected as on a WT32-EHT01,...

As far as I know, the LAN8720 module does not use SPI at all, but RMII. Accordingly SPI should be available for the LEDs right?

@d3473r The datasheet is also available in english. [WT32-ETH01_datasheet_V1.1- en.pdf](https://github.com/Aircoookie/WLED/files/9017709/WT32-ETH01_datasheet_V1.1-.en.pdf)

Sorry :D However, I had to introduce custom errors for timeouts because I also use them apart from socketio. I forgot it here, thank you.

Thank you for the research. Retries on timeouts would be useful, also for other temporary network errors. Also logging should help to debug these problems. I think I should refactor...

What do you mean by configuration after the installation? Which steps should be performed there? Is this a common practice to distribute such roles in a collection?

Timeouts should not occur. Rate limiting by uptime kuma is possible and can be seen in the uptime kuma logs. As far as I know, it is not the number...

I cannot reproduce this problem. With a local uptime kuma instance I made 1000 `get_monitor_beats` requests with different monitor ids and time periods. All of them took less than 0.02...