I am running two different devices on .io, one is a ESP32-S3 Rev TFT, the other a QT Py. I have had both woring on WiFi and interfaced to .io, reporting data, and graphing it. When I power down either of them, the Feeds do not see to start again, even though the devices seem (by LED flashes) to be sending data. What am I doing wrong?
#Powered-Down Devices Won't Re-Connect
1 messages Β· Page 1 of 1 (latest)
Can you update to latest version, we have recently (last week) fixed such an issue...
Should be, hmmm
When I reload the Feeds page, I get two messages that they are connected.
Maybe worth doing a full flash erase (the factory reset / nuke uf2 image) and then applying the latest update.
Can you see the serial monitor, does it mention a number of bytes and i2c decode error?
Sure, what operating system / computer type are you using (mac/windows/linux), and which code editor
Ah got you. In that case, let's avoid that for a second, which sensors are connected to the qtpy, and which sensors are setup as components on wippersnapper (do you have all the sensors configured already)
I am using SHT45, and they are both configured. Were working fine before the power cycle.
The RevTFT is connected to USB, and is right in front of me.
This site shows the serial monitor after you use the connect button and select the device.
You might need to reset the device, then once you hear the usb/disc connected noise you can try connecting the serial monitor website. https://webserial.io/
Switching to Edge for that.
OK... seems to be connected to WebSerial.
I am connected, and getting PING!'s
Cool, so before that ping bit it does the connecting to wifi, then mqtt (adafruit IO) then does pin config, then does i2c config (the liekly bit with error message) then does Pings inbetween sensor reads.
Try resetting the board and connecting as quick as possible, if you see something about connecting or pin definitions then you did it quick enough. if all you see is pings then try again but connect more quickly.
No, curious, try refreshing the IO page, are the components (SHT45) still there?
If so then you'll have to try removing them and re-adding them. That should sync up the i2c configuration message
Those numbers have not changed.
use the cog next to one of the sht45 data rows, then remove the component, and re-add an sht45. You can see the serial monitor at the same time get those messages to update i2c stuff.
I will try that.
I removed the device. Then added the device.
Then did a I2C scan, and saw it.
I've got a qtpys2 with an sht41, I've deleted it, and created it again as sht45 (same driver). I'm on 30seconds polling, and seen 4 feed values published, I'll now reboot.
I brought up the Devices page in Firefox and Edge, no difference.
So after a reboot my secrets.json needed filling in (I've seen that before where the device is showing an old copy after being flashed until power cycled).
Then it loaded as expected
My Secrets is fine, because I show ONLINE at io.adafruit.com. Both wifi and account login thus good.
So do you see the i2c section of the configuration in the serial monitor now, after removing and re-adding the sensor to the device's wippersnapper page. (Reboot device and watch serial monitor again)
Okay that looks good. Then the last issue is the Send Every (interval time) for each sensor feed / metric. If you have it set for 15minutes for example (the default) then you wont see a new data value for the first 15minutes of being online after rebooting. This is not the same as if you add a new component (it does an initial reading). There is an open github issue related to this "initial reading"
Try adjusting the send-every time to 30seconds and then wait for a minute watching the serial monitor
OK... you are right... it had reverted to 15 minutes. I changed it to 30 seconds, and it started working.
π frustrating but success is better when well earned.
Fortunately it's on the todo list π
I powered down the QT Py... this was on the Rev TFT..... let me go grab it.
powered up
π€
connection made, but it says my I2C connection is bad. That could be on me.
using the stemma QT port on QTPY?
no... wired on breadboard.
Q: is Vin a battery input on the sensor?
I think I found my error.
the i2c port is only the one on the stemmaQT port. Otherwise you need to build wippersnapper yourself (not too hard). Easiest is to make an adapter cable or buy one https://www.adafruit.com/product/4209 [out of stock use digikey or local seller]
Vin should be whatever the StemmaQT cable is providing, or you can supply Vin up to the maximum rating of the breakout, and then 3V is the regulated supply from the Vin.
Thanks... I think this answered my question. I did something wrong.... trying again.
Just to reiterate, the I2C on the QTPY has 2 ports, the pins labelled SDA/SCL, and the StemmaQT port. Only the latter works with wippersnapper.
It came up!
Wunderbar!
OK... I think I grok what you said... Sigh....
I need to steal the cable from the other one.... my cables are not here yet.
Ah yeah, lots of plug and playing π
You can also get to grips with code + git and then make it work with the pins instead of StemmaQT port (Arduino i2c port is Wire1 instead of Wire).
Yay.... QT Py, connected ....
... and delivering data. As usual, I had two problems at once. Engineering... sheesh.
Glad to hear both work "as expected", but not "as desired" or really expected π Well done for persevering! (Also I love the reverse tft + qtpy s2/s3's, both lovely things!)
Wow batteries! Fair play
π
C-cells?
I only look like a noob. Those are a pair of Type 123 batts. 6V total.
Thanks for teaching me about WebSerial.
oh fair play π know more than I, I wondered if some camera thing or something π
That one is very handy, usually works best in Chrome related browsers.
Yes. Edge worked.
I have a project in mind and need to see how the QTPy and SHT45 use power, for battery life.
Kill the LEDs (break the jumper on back of sensor board), also I think the feathers may be more designed for switching off Peripherals, like the display / i2c may have a separate power pin / control.
Any way to do that while using Wipper?
You can also slow the cpu speed, and deep sleep on the esp32, but not yet on wippersnapper without getting your hands dirty.
Heh.... that's my ultimate goal, serious low power consumption.
My cable should be in tomorrow or the day after, and I'll get both units up and running. If I have two different units up and running delivering data, and they both can survive power downs I will be very happy.
Some temp/humidity sensors have an interrupt pin, which can be used to wake the esp32 when a threshold is reached. Maybe the BME range, but lots of them do, and you could save a lot of power by sleeping the esp32 until the interrupt pin is triggered. The SHT31 has an alert/interrupt pin for example https://learn.adafruit.com/adafruit-sht31-d-temperature-and-humidity-sensor-breakout/pinouts#other-pins-1536805
< Long term goal for you.
Neato. Yes, Wipper now, code later.
Thank you so much!