Search results for:

Merry Christmas!

btw, I had problems with simple proxy, but the Squid proxy works very well

My REST API example:

var options = {
  protocol: "http:",
  method: 'POST',
  host: 'XXXX.XXXX.XXXX.XXXX',  // Proxy IP
  path: 'https://endpoint.com/', // Landing URL
  port: 8888,
  pathname: "restpath",
  search: null,
  query: null,
  headers: { "Content-Type": "application/json", "Content-Length": content.length }
};

var req = require("http").request(options, function (res) {
  var d = "";
  res.on('data', function (data) { if (d.length < 8) d += data; });
  res.on('close', function (data) { callback(); });
});
req.on('error', function (e) {
  callback();
});
req.end(content);
  } catch (f) {
}

Thank you very much MaBe!

Thanks MaBe,

Thank you for checking! Now I understand the reason. I think most sites no longer support TLS 1.0/1.1 and TLS 1.2 will be deprecated soon. Unfortunately, the ESP8266 cannot be used for this purpose. An ugly solution. but useful is the http_to_https proxy.

I have upgraded my Ai Thinker ESP-01s (1 Mb) to AT version:1.7.1.0(Jul 15 2019 16:58:04).
The problem is the same.

Dear MaBe, maybe you can try this url with your new AT?
https://djdjeleeisvpd3y-elink.adb.eu-fra­nkfurt-1.oraclecloudapps.com/ords/demo/t­eszt/test/

Thank you, Gordon, for the quick solution! I can't upgrade my firmware, probably my usb-ttl converter is wrong, so i ordered a new one. Your example works with the AT version:1.2.0.0(Jul 1 2016 20:04:45) firmware, but:
it doesn't work with this url:

https://djdjeleeisvpd3y-elink.adb.eu-fra­nkfurt-1.oraclecloudapps.com/ords/demo/t­eszt/test/

This is interesting because the Certificate Signature Algorithm is the same:
PKCS #1 SHA-256 With RSA Encryption

I hope the new firmware will fix this problem.

I couldn't find any reference to it in this document, maybe it was made for the older firmware.
The AT versions are also old in the document: such as, v1.2.0.0, v1.1.3.0, v1.1.2.0.
The good news is that there is a reference to TLS 1.3 on the Adafruit site:
https://blog.adafruit.com/2022/12/13/esp­32-esp8266-https-and-ssl-tls-encryption-­basic-concepts-esp32/

Thanks Gordon, that would be a good solution. Do you think the ESP8266 can handle TLS 1.3?

Thanks!

Hi Gordon,

Do you have any recent information about the new wifi+ble (+https) hardware?
Btw the good old combo the mdbt42+esp8266 is incredibly stable, but i can't use the https.

Dear MaBe,

I would like to know if the psram is "automatically" used by e.g. wrover or if something has to be set when uploading the firmware?

if you type this into the google search engine: "nrf52840 smartwatch" the third search result (for me) is this watch. When I searched for a picture, it was the second one. I think other people look for it in the same way, there is nothing surprising about it. For me, the question was basically what type/style the new watch should be. The retro line (e.g. Casio) is also interesting, but for corporate use it is not serious enough for me, I vote for such a form, that's why I shared it. If anyone, then I definitely support Gordon's developments, I have already bought a lot of factory Espruino devices.

I don't really understand why you wrote that it was a "coincidence". I was deliberately looking for a watch that looks good and uses an NRF52 chip. I don't think - although I could be wrong - that the Bangle JS 3 project has a budget for its own design. What I like about Gordon's projects is that they are rationally planned. Besides all that, really thanks for the info!

Thanks for the info, I didn't know that. I shared it mainly because of the design.

First of all: i like the Bangle js concept.
Size and design: I prefer the V1 to the V2
Screen: V2
I miss the loud speaker.

https://www.nordicsemi.com/News/2021/03/­Mo-Young-Ltd-uses-nRF52840-in-Leadoys-C1­6-Smart-Watch

Hello @Gordon, this Puck.js Lite is a good idea! It was tiring to solder the beacon :) When can I order these?

Great, thank you very much!

Great, thanks!

can it be inadequate power-some power glitch/brownout? if you use esp8266 with it an connect it to same power source the total system power draw may change a lot e.g due to wifi traffic and may cause random power issues if it draws too much.

I thought about it too but i use very good voltage regulators.

@Gordon thank you for your suggestions and efforts! I tested a lot too. And I have come to the conclusion that sometimes reading and writing to storage is very slow. This is not a problem anyway, but if there is a delayed reboot after that, the memory will be cleared. But it also happens very rarely and I think it has to do with running out of memory.

This strange code sometimes produced this error:

function log(f){  
     if (require("Storage").read(f) == "undefined") {
      require("Storage").write(f,'1');
    }else{
      var n=parseInt(require("Storage").read(f))+1­;
      n=n.toString();
      require("Storage").write(f,n);
    }
}

for (var g=0; g<10; g++) {
	clearInterval();
	clearWatch();
	console.log(require("Storage").getFree()­+'-'+parseInt(require("Storage").read('g­s4.pc'))+1);
	log('gs4.pc');
	setTimeout(E.reboot,2000);
}

Thank you very much!

I use the MDBT42Q with the 2v09 firmware.
I connected the ESP8266 to it.
After 2 months of operation, the flash became empty!

>require("Storage").list()
=[  ]
>require("Storage").getFree();
=40960

The code and the logs are disappeared.
The device has been self-initialized, working, and can be connected.
I tried another MDBT42Q yesterday and the same thing happened!
Is it possible that the storage write could cause a problem?
I do a simple log, I write very little data (basically i am writing a counter):

function log(f){
     if (require("Storage").read(f) == "undefined") {
      require("Storage").write(f,'1');
    }else{
      var n=parseInt(require("Storage").read(f))+1­;
      n=n.toString();
      require("Storage").write(f,n);
    }
}

This log runs very rarely.

I couldn't manually reproduce this thing maybe someone has a similar experience?
This is very scary for me.

Same here..MDBT42Q, 2v09

>require("Storage").list()
=[  ]
>require("Storage").getFree();
=40960
>process.memory();
={ free: 2458, usage: 42, total: 2500, history: 17,
  gc: 0, gctime: 3.47900390625, blocksize: 16, stackEndAddress: 536928976, flash_start: 0,
  flash_binary_end: 432868, flash_code_start: 442368, flash_length: 524288 }
> 

I can connect to the device, but I don’t want to do anything else with it until there’s a suggestion.
The power supply was continuous and i use a good quality adapter, voltage regulator and battery. I was able to connect to the device, I didn’t have to reboot, but the flash was completely empty. I used the flash to log in, but that couldn't be much data.

I guess maybe there was some logging to Storage inside your setScan handler?

I store the result of setScan in an array, but inside the http handler write the log. I log not only the errors but also the exceptions. I'm trying the fix, which is interesting! I attach the memory usage graph.