Decided to go back to basics and just try and send a write to Thing speak with "esp9266-dht-thingspeak-logger.ino also by squix from a link in his instruction pdf.
In this example the requests are totally different to squixs other code, he must have been experimenting to see what works. This example returns a bad URL request as below.
connecting to api.thingspeak.com
Requesting URL: /update?api_key=def4daadxxxxxx&field1=nan&field2=nan
HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=utf-8
Status: 400 Bad Request
Access-Control-Allow-Methods: GET, POST, PUT, OPTIONS, DELETE, PATCH
Access-Control-Allow-Headers: origin, content-type, X-Requested-With
X-Powered-By: Phusion Passenger 4.0.57
Date: Tue, 25 Jul 2017 12:18:40 GMT
Server: nginx/1.9.3 + Phusion Passenger 4.0.57
Again, i dont see anywhere that we have rights to submit a "write", or to which channel, although the bad URL is another issue. Maybe something has changed since it was written.
I have used thingspeak for a couple of years with domoticz but in that format requests are made with PHP at least in my case.
Also interesting in this case is that we are not calling another library i.e thingspeak.h where we can define the requests.
No panic, we will get there LOL, got food in our bellies it can wait.
Understand i am not trying to get a squix kit working here, just playing around trying to learn a little, at my age stuff goes in and out with little to no retention. AKA NULL VOID