emoncms VS Guzzle

I think I have seen others do this with some smaller dedicated timer thermocouple controllers.. but I wanted to be able to write software to do more.. like email me start/stop emails.. and the openenergy monitor emonpi gives access to emoncms.org which lets me see the kiln temps 24 hours a day from anywhere in the world.. and they have an iphone app that you can use to see the data.. so all I had to do was figure out how to publish the data to their service.. and then write a if then loop python script to check for the kiln temp at a time.. if low..turn kiln on.. if high.. turn it off.... I have dreams of a cleaner simpler script.. but no time to get it done.

Take a look at CircuitSetup.us for their EmonESP whole-house energy monitor. I got their single phase with two current transformers several months ago and it has worked perfectly. It has a web page, sends out MQTT messages and can simultaneously send out emoncms data (see emoncms.org ).

Guzzle is a PHP HTTP client library. It’s a simple and effective solution for sending HTTP requests and managing HTTP/1.1 and HTTP/2.0 responses. This versatile tool excels in several areas, allowing developers to build query strings quickly, send POST requests, upload JSON data, and handle other HTTP-related tasks. Moreover, Guzzle facilitates both synchronous and asynchronous request handling, providing flexibility for different scenarios.

Symfony HTTP Client or Guzzle. If new build then Symfony, but have a lot of existing implementations with Guzzle. Both have worked very well. Worst case fallback to cURL.

but if you'd rather make raw requests, guzzle is a good option (though I'd opt for the sdk): https://github.com/guzzle/guzzle

PHP has built-in cURL support, but I never use it. I like using Guzzle or Symfony's http-client.

I just ran into multiple errors regarding the pre-packaged cURL: It does not feature accepting compressed responses (which I suppose is due to absense of `libz` being compiled/linked in).

I am busy building a small application that monitors websites using guzzle. My idea is to run through the list of websites alphabetically and make a guzzle request to each and update my table with the http response codes of each site.

Like Node.js, the PHP ecosystem has quite a number of good HTTP request libraries. Guzzle is perhaps one of the most well known, but there are many other popular libraries out there. Luckily, PHP also has some interface standards around HTTP clients and messages, particularly PSR-7, PSR-17, and PSR-18,