API variables changing

[71]

I have a custom program, which declares a boolean variable named strict.

Using the API, I can change the variable without a problem. But it looks like it sometimes resets.

curl https://us.wio.seeed.io/v1/node/variable/strict -> "0" curl -X POST https://us.wio.seeed.io/v1/node/variable/strict/1 curl https://us.wio.seeed.io/v1/node/variable/strict -> "1"

I'll check it again a few hours later: curl https://us.wio.seeed.io/v1/node/variable/strict -> "0"

The variable can only be change throu the Internet, and this behavior appeared hours after pushing the update, so I'm 100% sure that nobody's playing with my API tokens.

I guess the Wio Link restarts every few minutes / hours, since "0" is the default value of my variable. If so, where is it documented?

[KillingJacky]

Hi, thanks for reporting this issue. We will test it using your scenario, and to see if the issue is recurrent. For now, there're 2 possible reasons I can imagine that the variable resets.

• exception happen, and caused the wio to restart
• network connection broken or slow, heartbeat lost for a long time (1min), wio actively reboots itself.

Anyway, we will look into this and if you have any progress please let us know too.

[KillingJacky]

BTW, from the URL, I guess you've uploaded your custom program to the newest global server, is that true? Or which firmware version are u using if you deployed a private server?

[71]

@KillingJacky Hi, thanks for your answer!

Nope, I'm using the new global server. The project can be found here.

I didn't think about the possibility of an exception, although the resets seem "random", so I don't really know what would cause it.

[KillingJacky]

@6A Nice project and docs. I already cloned your project with my wio link. Instead my wio link connects to my localhost private server. Let's see how is it going for my copy :)

[71]

@KillingJacky Thanks! Lemme know how it goes! I didn't include a picture of where to plug what though, so I hope it wasn't too hard to find it out!

[KillingJacky]

It's not hard for me to figure out which grove connects to which port. But for others I'm afraid it will take a while. Well here's the result at my side. It does reboot for no reason. I enabled the debug printing, and here's what I get:

Node name: Wio Link 22
FW version: 1.2
Chip id: 0x0015ec67
Free heap size: 24200
Private key: 7e5188c22b63fa67acde18f13b3969bf
Node SN: f6bca7d7ef9bb00eb48264b15b55d051
Data server: 192.168.31.12
OTA server: 192.168.31.12
OTA result flag: 0
start to establish network connection.
connect to ssid Xiaomi_Youth with passwd xxx
Waiting ip, state: CONNECTING
err: wakeup failed!
Waiting ip, state: CONNECTING
wakeuped
paj7620 initialization done.
Waiting ip, state: CONNECTING
Done. IP: 192.168.31.236
Resolving 192.168.31.12...
Resolved IP: 192.168.31.12
Resolving 192.168.31.12...
Resolved IP: 192.168.31.12
data connection init.
ota connection init.
data conn connected
ota conn connected
data conn confirm hello: 1 
data conn handshake done, keep-alive
ota conn confirm hello: 1 
ota conn handshake done, keep-alive
ota conn: ##PING##
ota conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
data conn: GET /variable/strict

data conn: GET /variable/strict

ota conn: ##PING##
data conn: POST /variable/strict/1

data conn: GET /variable/strict

ota conn: ##PING##
data conn: ##PING##
data conn: GET /function/toggle

ota conn: ##PING##
data conn: POST /function/toggle/bm9uZQ==

data conn: POST /function/toggle/bm9uZQ==

data conn: GET /variable/strict

data conn: GET /variable/strict

data conn: GET /variable/strict

data conn: GET /variable/strict

data conn: GET /variable/strict

ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: GET /variable/strict

ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: GET /variable/strict

data conn: GET /variable/strict

data conn: GET /variable/strict

data conn: GET /variable/strict

data conn: GET /variable/strict

data conn: GET /variable/strict

ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
data conn: GET /variable/strict

ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: GET /variable/strict

ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ü

Boot reason: DEFAULT
Node name: Wio Link 22
FW version: 1.2
Chip id: 0x0015ec67
Free heap size: 24200
Private key: 7e5188c22b63fa67acde18f13b3969bf
Node SN: f6bca7d7ef9bb00eb48264b15b55d051
Data server: 192.168.31.12
OTA server: 192.168.31.12
OTA result flag: 0
start to establish network connection.
connect to ssid Xiaomi_Youth with passwd xxx
Waiting ip, state: CONNECTING
err: wakeup failed!
Waiting ip, state: CONNECTING
wakeuped
paj7620 initialization done.
Waiting ip, state: CONNECTING
Done. IP: 192.168.31.236
Resolving 192.168.31.12...
Resolved IP: 192.168.31.12
Resolving 192.168.31.12...
Resolved IP: 192.168.31.12
data connection init.
ota connection init.
data conn connected
ota conn connected
data conn confirm hello: 1 
data conn handshake done, keep-alive
ota conn confirm hello: 1 
ota conn handshake done, keep-alive
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##

 ets Jan  8 2013,rst cause:1, boot mode:(3,6)

load 0x40100000, len 1396, room 16 
tail 4
chksum 0x89
load 0x3ffe8000, len 776, room 4 
tail 4
chksum 0xe8
load 0x3ffe8308, len 540, room 4 
tail 8
chksum 0xc0
csum 0xc0

2nd boot version : 1.4(b1)
  SPI Speed      : 40MHz
  SPI Mode       : QIO
  SPI Flash Size & Map: 32Mbit(1024KB+1024KB)
jump to run user1 @ 1000

ø

Boot reason: DEFAULT
Node name: Wio Link 22
FW version: 1.2
Chip id: 0x0015ec67
Free heap size: 24200
Private key: 7e5188c22b63fa67acde18f13b3969bf
Node SN: f6bca7d7ef9bb00eb48264b15b55d051
Data server: 192.168.31.12
OTA server: 192.168.31.12
OTA result flag: 0
start to establish network connection.
connect to ssid Xiaomi_Youth with passwd xxx
Waiting ip, state: CONNECTING
err: wakeup failed!
Waiting ip, state: CONNECTING
wakeuped
paj7620 initialization done.
Done. IP: 192.168.31.236
Resolving 192.168.31.12...
Resolved IP: 192.168.31.12
Resolving 192.168.31.12...
Resolved IP: 192.168.31.12
data connection init.
ota connection init.
data conn connected
ota conn connected
data conn confirm hello: 1 
data conn handshake done, keep-alive
ota conn confirm hello: 1 
ota conn handshake done, keep-alive
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
dota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
ota conn: ##PING##
data conn: ##PING##
.....

From the boot reason (DEFAULT) I can see the boot is just like a power-on startup. It's not caused by exception either watchdog. And the time point it reboots is totally random too. For the last try, it keeps running good for 2 hours, but the worst one is 10 minutes (even when I did not issue any internet request).

It's just accidental and not regularly recurrent. I have to say it's a tough issue. What's in my brain now is that maybe the LED-Strip causes the power unstable, so the ESP8266 is just like going into a power down and up. I'm going to do more experiments - remove the LED-Strip, power with battery...etc.

[71]

@KillingJacky Wow, thanks for the very thoughtful reply! Btw, I know this is a private server, but do watch out since you included a password / token in your logs!

Now the issue... Well it does look weird, thanks for investigating!

[KillingJacky]

After twice reboot, it never happen again. The Wio can stand very very long time without reboot. I even didn't change anything of the environment. It's really odd.

[KillingJacky]

How many LEDs are in your strip? 60? I still think the power drain of the LED strip caused the unstable state.

[71]

It says there are 60 of 'em, but as you see in the code I only turn on 30 LEDs, and that lights up the whole strip. I'll try, thanks! Btw, I turn off the strip by setting everything to black (000000), is this the correct way to go?

[KillingJacky]

I think you just pull the strip off and test if it still reboots. Or you try to pick the red wire out of the strip's grove socket and connect it ( vcc of led strip ) to a 5V power.

[71]

Damn, I'll do that some other time, right now everything is already set up and doing this'll take hours. Wanna close this? I'll try it out when I get the opportunity, and reopen this issue if needed?

[KillingJacky]

Sorry man, I really can't get it recurrent afterwards. Thank you for your understanding and your possible future efforts.

[KillingJacky]

Will close this, feel free to reopen it if any further question.