gregy - sensESP token? expiryhave sensESP dev...
sensESP token? expiry
have sensESP device, been working fine, and just “stopped” communication with SK,
i can still access it as expected via webUI and noted its EXACTLY 12 months since i “programmed” it (& presumably first connected to sk)
i suspect? maybe its an authentication/token issue (eg “1 year”)
However cant work out how to force? it to re-authenticate.
sensESP fw is older 1.x (i think)
have deleted its entry/s in sk under security/devices.. no joy.
have “restarted” sensESp from webUI - no joy
in webUI under config/sk tab i can see its read/write token .. but cant? delete this?
Note i have not as yet tried a “factory reset’ …
Q: what will this reset?
how to force sensESP device to request a new token?
4 Replies
did the “factory reset” .
discovered this only? reset the authentication token… so all good
(i have server details and wifi hard coded into sensesp)
Factory reset nukes the WiFi settings, SK auth token, and the local disk that holds any other configuration information.
I believe current versions request a new token more reliably. It took a few iterations to get the SK authentication logic right. (Disclaimer: it still might not be 😉 )
ah yep, it did also reset a calibration value i had modified manually .. wifi i hard coded in sensesp.
interestingly i had a second unit also yesterday similar, however it actually generated a new token request.
obviously a slightly newer version of sensesp in it.
im now setting the token to “NEVER”.. so as to avoid this future issue.
.. but i do have one device that needs mods (esp32 analog IN is inaccurate near 3V as we know… so removing the project and adding ads1115 … so will probably try to update sensesp on it to latest version )
"NEVER" is the right answer!