This shows you the differences between two versions of the page.
iothings:proiecte:2025sric:discordbot-notification [2025/04/23 15:11] gelu_codrin.lupascu Added intro and challenges |
iothings:proiecte:2025sric:discordbot-notification [2025/04/23 16:17] (current) gelu_codrin.lupascu Added challenges text |
||
---|---|---|---|
Line 15: | Line 15: | ||
- | {{ :iothings:proiecte:2025sric:codrinlupascu-iot_project_schema_bloc.drawio.png?direct&900 |}} | + | {{ :iothings:proiecte:2025sric:codrinlupascu-iot_project_schema_bloc.drawio.png?direct&550 |}} |
Line 51: | Line 51: | ||
The first step in any workflow is the trigger condition. The free account has a daily limit on requests: 10. The triggers need to be spaced out evenly across the day, or design the system to send the median temperature once per day. InfluxDB has a way to send notifications by itself but they are not available for the free account. | The first step in any workflow is the trigger condition. The free account has a daily limit on requests: 10. The triggers need to be spaced out evenly across the day, or design the system to send the median temperature once per day. InfluxDB has a way to send notifications by itself but they are not available for the free account. | ||
- | The next challenge was | + | The next challenge related to accessing the information in the database. Pipeline offers a couple of solutions for this, but at the end I decided to use HTTP Requests. First I tested in the CMD window using curl. The first requests were targeting "INFLUX_URL/api/v2/buckets" which apparently only retrieves buckets metadata. The tutorial [1] didn't really specify in detail that I should've used another url (/api/v2/query). One more error I was getting at some point, |
====== References ====== | ====== References ====== |