- We used different temperatures to create a buffer so that we would not generate multiple triggers (and multiple emails) if the temperature hovered around a single temperature value.
- Using an intermediary meant we did not need to worry about a firewall, port forwarding, and other configurations necessary to expose your Raspberry Pi to the public internet.
- IFTTT is more consumer-focused, while Zapper is more business-focused in terms of the integrations it provides. Zapper will also allow you to create a more complex workflow, trigger, and action scenarios.
- No. ThingSpeak only consumes data to display on a dashboard. Some platforms, such as ThingBoard, will allow you to send data back to a device for the purposes of controlling that device.
- There is a maximum of three JSON properties available – Value1, Value2, and Value3.
- From ease and speed of development perspectives, IFTTT or Zapper would be a good choice, but you could certainly use AWS or one of the other...