-
• #2
Can you get a 200 response using a tool like Postman or Insomnia with the same endpoint? That's the first thing I'd check. That error suggests host is not found.
Also, but without knowing, I'd also check whether http is supported by Telegram. I would expect an API like that to use https (in which case you have a problem on ESP8266).
-
• #3
Hi.
Yes. I already made some requests with postman. http and https work in postman without any issues on the same endpoint.
Why there is a problem with http on esp8266?
Edit:
>var request = http.get( :encodeURIComponent("http://api.thecatapi.com/v1/images/search?size=full"), :(response) => { :console.log(response); :response.on('data', (data) => {console.log(data);}) :}); :request.on('error', (err) => {console.log(err)}); =undefined { "code": -6, "message": "not found" }
Now I'm sure that is isn't an issue with telegram bot.
Edit2:
var http = require("http"); http.get("http://www.espruino.com", function(res) { res.on('data', function(data) { console.log(data); }); });
This works fine. I got the whole html page...
-
• #4
I think ESP8226 build does not support
encodeURIComponent()
. See the docs - not available on devices with low flash memory. Try it without. -
• #5
>encodeURIComponent("https://www.google.de") ="https%3A%2F%2Fwww.google.de"
Seems to work fine.
Code compiles without any problems.Latest result:
>var options = url.parse("http://api.telegram.org/bot{MYTOKEN}/getUpdates") ={ protocol: "http:", method: "GET", host: "api.telegram.org", path: "/bot{MYTOKEN}" ... "{MYTOKEN}/getUpdates", pathname: "/bot{MYTOKEN}" ... "{MYTOKEN}/getUpdates", search: null, port: null, query: null } >var request = require("http").request(options, function(res) { : res.on('data', function(data) { : console.log("HTTP> "+data); : }); : res.on('close', function(data) { : console.log("Connection closed"); : }); :}); :request.on('error', (err) => {console.log(err);}); =undefined >request.end() =undefined HTTP> <html> <head> HTTP> <title>301 Moved Permanently</title></head> <body bgcolor="white"> <center><h1>301 Moved Permanently</h1></center> <hr><center>nginx/1.12.2</center> </body> </html> Connection closed
The "301 Moved Permanently" should be a real result of telegram. Why it didn't work in espruino. No issues on browser or on postman.
-
• #6
Request with curl results in the same.
No problem on espruino. Telegram didn't support http. Only https.
Thank you - My fault :)
Why espruino didn't support https on esp8266?
-
• #7
Ok, glad sorted. Re https, there's not enough memory on the device for the certificate management. You can use official Espruino Wifi board, and I think also supported on ESP32.
-
• #8
There's also this proxy which may work for you. http://httptohttps.mrtimcakes.com/ by espruino forum member @MrTimcakes
Hi guys,
i try to send a messages from the ESP8266-01 by using the espruino firmware.
The wifi connection is established successfully.
Response of the error case:
After that I try to send a message via GET or POST to the telegram bot.
Unfortunately I always get error messages. I am not sure if the requests arrive at telegram at all.
Can someone give me a hint?
I have already found a module in the internet. But that also do not work.
http://wiki.amperka.ru/js:telegram
Edit: If I just open the url in the browser the request will send and the telegram bot has the message.