Added PowerSaving for all ESP32-based repeaters by IoTThinks · Pull Request #1687 · meshcore-dev/MeshCore

IoTThinks · 2026-02-13T16:22:35Z

Hi friends,
This is the cleanup PR for this old PR #1353
The changes are below:

(New) Let ESP32-based repeaters to sleep immediately receiving and process a LoRa packet
(New) Added detailed response for powersaving CLI
Supported sleep for all ESP32-based repeaters
(New) Reduced time drift ESP32-based repeaters in power saving
Added getIRQGpio to return DIO1 (SX1262) and DIO0 (SX127x)
Fixed DIO0, DIO1 and RESET for Heltec v2. This is to allow Heltec v2 to do power saving. Well, I have a lot of requests to support Heltec v2.
Added getIRQGpio to return DIO0 for Lilygo T3S3 SX1276
Added getIRQGpio to return DIO0 for Lilygo TLoRa SX1276

I have tested with RAK4631, Heltec v3, Heltec v4 and Heltec V4 with ESPNOW.
I will set this as Draft to see if I miss anything and let all of my repeaters to run for a while.

Thanks a lot and have a nice day.

IoTThinks · 2026-02-13T16:40:42Z

Still need to fix for those TBeam boards.
Will do it tomorrow.

meshcore-dev/MeshCore#1687

IoTThinks · 2026-02-14T15:33:00Z

@towerviewcams Here you go.
These files are for UPGRADE from existing repeater firmware.
https://github.com/IoTThinks/EasySkyMesh/tree/main/firmware/Testing/PR-1687

This PR should be for ESP32-based repeaters only.
I have tested RAK4631 to ensure the PR does not break PowerSaving in NRF52.

powersaving on => It should tell you to have effect immediately.

Testing steps for ESP32-based repeaters

powersaving on => It should tell you to to wait 2 minutes to see the power reduction. Around 14mA for Heltec v4. Around 10mA for Heltec v3.
When receiving a LoRa packet, it will process and sleep again immediately.
For heltecv4 with bridge, it will say "Bridge not supported" and will not go to sleep.
powersaving off => Returns Off
powersaving => To see status On or Off
start ota => It will skip sleep and stay at 120mA. You can do OTA as normal. After automatically reboot, the powersaving will automatically run after 2 minutes from boot.
clock => for time drift, around 1 minute/24 hours.

Please help to test.
Thanks a lot.

IoTThinks · 2026-02-14T16:21:43Z

For Heltec v4, when doing "start ota", the current may jump to ...750mA then down to 124mA.
So if the power supply is not stable for spike or set at low voltage (3.6-3.8v) the "start ota" may fail to start.
I see this happen even if "powersaving off".

It should be ok for battery.

cra0 · 2026-02-15T11:18:30Z

+1 testing atm

towerviewcams · 2026-02-15T13:30:45Z

V4 testing on two boards results:

*fresh flash 1.13 firmware, powersaving delay is 22 seconds, then drops to 11.6mA sleep.
**testing/PR-1687 flashed over the 1.13 firmware and sleep is FAST! after packet process, sleep is immediate. 11.6mA
(version shows 1.12 29-Jan-2026) on the test bin for PR1687) FYI. I know this file is new because powersaving now reply with "On - After 2 minutes".

I have also verified that the receiver sensitivity remains normal with my lab test companion set to -9 power and the V4 has rssi of my test signals at -117 setup in a RF cage (normal RX level for V4 in my test cage). Also checked to make sure GC1109 has power on VCC pin full time-yes. So the LNA is always on.

Now running live on the mesh here in Oregon USA. repeating packets normally working good.

Next for Rak!

**Update
Testing 2, 4631 rak boards with new stock 1.13 works great and sleep is immediate at 4mA

beachmiles · 2026-02-17T19:37:50Z

There is a chance that rtc_gpio_hold_dis will release this pin P_LORA_PA_EN to its default state which is off. May want to put the rtc_gpio_hold_dis function after setting the pin. There could be an extremely short blip on waking up after deep sleep that may not really show too much during testing but is not ideal.

pinMode(P_LORA_PA_EN, OUTPUT);
digitalWrite(P_LORA_PA_EN,HIGH);
rtc_gpio_hold_dis((gpio_num_t)P_LORA_PA_EN);

The esp32 docs are not super clear on this rtc_gpio_hold_dis function and may be missing some detail that the gpio_hold_dis function had Discussion about it here.
#1600 (comment)

IoTThinks · 2026-02-18T00:07:49Z

@beachmiles This is required in deepsleep as I understand.

rtc_gpio_hold_dis

This PowerSaving uses light sleep.
So during lightsleep, GPIO states and RAM are intact / unchanged.

beachmiles · 2026-02-19T04:12:56Z

Initial testing on this firmware is very good with VERY low power usage during sleep (6.7mA at 5.095V / 34.2 mW) and its extremely quick in going back to sleep after handling traffic.
Nice job!!

The bright white LED is still flashing during communication which it ideally wouldn't be doing while in powersave.
I believe this is the P_LORA_TX_LED pin?
Ideally a check for powersaving_enabled flag could be done before running this function,
_board->onBeforeTransmit();

Otherwise you'd have to put the check in each of the onBeforeTransmit functions in all of the variants cpp files. Save a little bit of juice and reducing this small current spike during TX could help keep the PA voltage a bit more steady giving slightly better TX performance?

mikecarper · 2026-02-19T09:01:11Z

@beachmiles can you remove the led on code and measure the power difference? If it's small then chasing this down might not be worth it; if it's significant then this is important

towerviewcams · 2026-02-19T14:30:24Z

@beachmiles can you remove the led on code and measure the power difference? If it's small then chasing this down might not be worth it; if it's significant then this is important

I remove the current limit resister on all my boards. Might be a small amount but why have a light show in a sealed box that no one can see. Buy areas like Oregon is now the benefit is a bit more then slow areas.

beachmiles · 2026-02-19T22:53:06Z

@beachmiles can you remove the led on code and measure the power difference? If it's small then chasing this down might not be worth it; if it's significant then this is important

Will try to see if I can compile it with it off and do some testing. I am not only concerned about saving a tiny bit of power but also ensuring there is no VCC / 3.3V voltage drop with the bright LED on why transmitting as that same rail is used by the PA chip which could degrade its TX signal strength.

IoTThinks · 2026-02-20T01:46:24Z

@towerviewcams @beachmiles Likely very minimum power saved if turn off led after TX.

but also ensuring there is no VCC / 3.3V voltage drop with the bright LED on why transmitting as that same rail is used by the PA chip which could degrade its TX signal strength.

It makes sense.
I actually love to see the led on during TX for ...debugging :D
Generally, the LED seems to be ON for Heltec boards only.

Ideally a check for powersaving_enabled flag could be done before running this function,
_board->onBeforeTransmit();

Let me see if the code can access powersaving_flag.

Theo-Marshall · 2026-02-20T03:03:33Z

This works great for my ESP32C6 board. Current from 38 mA down to 6.5 mA, basically just spending energy on keeping the sx1262 in RX!

beachmiles · 2026-02-20T03:21:38Z

Excuse my continued editing of this post. My original findings were bad as I was disabling the PA as well as the LED so was seeing way better power savings with the PA off.

I couldn't easily access the powersaving_flag inside RadioLibWrappers.cpp so I just commented out the LED turning on in HeltecV4Board.cpp and built and flashed to my v4.

With the LED on during TX I am seeing ~3.5W spikes that drops the voltage from my 5V usb power supply from 5.09V all the way down to 4.78V.

Edit 3. @mikecarper Having the LED turned off lowers this TX peak to 3.35W and the 5.09V voltage dropping to 4.83V.
So the powersavings with the LED off only saves~150mW during TX blasts which is still not insignificant.

Im guessing the onboard 3.3V regulator is handling this voltage drop without its 3.3V output dropping too far, but Im fairly sure its 3.3V output is not going to be steady during these short blasts of the LED which could slightly decrease the PA signal strength.

Maybe this powersaving flag could be a uint8 instead of a bool so you could set different levels of powersaving for folks that want LEDs flashing and still have decent powersaving. I def love LEDs when I am debugging/troubleshooting but not when its sealed inside a box powered by a battery.

This is the build I finally got working with only 1 line commented out that turns on the LED on the heltec v4 variant.
meshcore_Heltec_v4_Repeater_PR1687_wLED_Off_v3.zip

mikecarper · 2026-02-20T03:39:29Z

The savings here are significant. Great find @beachmiles. With powersaving on, led off makes a lot of sense; I don't think we need to make a setting here. If you want blinking lights just turn powersaving off.

IoTThinks · 2026-02-20T07:05:31Z

I am willing to off the led in powersaving on.
Still finding a way to reach the powersaving_enabled flag in Heltec v3 and v4.
Do you have any suggested simple fix for this?

BTW, if this is bad not because of power consumption but because of the voltage drop during TX.
Then the LED should not be on during TX at all regardless powersaving is on or off.

IoTThinks · 2026-02-20T07:07:49Z

@Theo-Marshall Thanks a lot for your testing.
Glad it works as my Xiao C6 has not reached me yet.

IoTThinks · 2026-02-20T10:37:05Z

@mikecarper @beachmiles Confirmed having lower voltage drop via USB cable when LED is on. Measured by realtime usb monitor.
However, this issue happens even in main power and may affect TX.
Actually, the main power will be less stable to current spike like LED compared to battery.

So I suggest we or any friends here propose a way to turn off LED for all boards in all modes instead of just in powersaving mode.

Many boards have this features. RAK4631 does not have it.

basiccode12 · 2026-02-21T13:31:17Z

@IoTThinks Hi, my apologies on a little confused.

Some places say seeed esp32s3 + WIO works, some say it works with a pin hack. Some say its not working. Any chance I can get an update or eta (no hack).

IoTThinks · 2026-02-21T14:09:17Z

@basiccode12 This new PR requires no pin hack / change for Xiao Wio S3 combo.
This combo has a 30-pin connector link.

You may try the bin here.

https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving13

Please note Xiao S3 (non Wio) + Wio Sx1262 is different.
This combo uses basic GPIOs only.
It is supported too in the link.
I will create a PR for this combo too.

basiccode12 · 2026-02-21T23:40:07Z

@basiccode12 This new PR requires no pin hack / change for Xiao Wio S3 combo. This combo has a 30-pin connector link.

You may try the bin here.

https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving13

Please note Xiao S3 (non Wio) + Wio Sx1262 is different. This combo uses basic GPIOs only. It is supported too in the link. I will create a PR for this combo too.

Thanks!, 66mA for 2 mins then to 9mA on a 30 pin connector type. Went straight back to sleep after repeat.
----> The only thing i noticed is there were no adverts in sleep. Is it supposed to wake for adverts? Has anyone else noticed this?

IoTThinks · 2026-02-22T02:05:53Z

@basiccode12 All esp32 repeaters will wakeup every 30 minutes to check if to send adverts.

Last version, periodically adverts were sent correctly.

This version sleep after a few cycles after wakeup.

Let me monitor the adverts.

IoTThinks · 2026-02-22T02:07:08Z

@basiccode12 So your board is Xiao Wio S3.

Does it show battery percentage?

towerviewcams · 2026-04-01T16:24:33Z

@IoTThinks I have 4 repeaters running on PS14.1......Two are 4.2 boards and two are 4.3 boards. I can confirm that all of these had reset issues prior and now, DO NOT have any reset issues. running for days. Very nice

terminalvelocity23 · 2026-04-01T18:38:35Z

Mine is running for over a day now, and no restarts so far. V4.2.

upd: two days in, all good despite being deep-frozen - I'm simulating winter for an outside setup. Had to reset it due to temp sensor getting stuck at 0° С.

IoTThinks · 2026-04-02T02:53:22Z

@towerviewcams @terminalvelocity23 I haven't changed anything for PowerSaving code. :)
Let's monitor the reset issue for a while.

I guess some "reset" bug in MC 1.14 has been fixed or there is some "reset" bug in dev branch.
Good to have the "powerlog" CLI, just in case.

AI7NC · 2026-04-02T03:02:45Z

I just upgrade my tree node today to a V4.2 and firmware 14.1. I'll let you know if I see a reboot on it or not (only 2h in so far).

…

On Wed, Apr 1, 2026 at 7:53 PM IoTThinks ***@***.***> wrote: *IoTThinks* left a comment (meshcore-dev/MeshCore#1687) <#1687?email_source=notifications&email_token=ASMB24KVCWGYV6PHHNL6H334TXI3VA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJXGQZDQNRSGM2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4174286234> @towerviewcams <https://github.com/towerviewcams> @terminalvelocity23 <https://github.com/terminalvelocity23> I haven't changed anything for PowerSaving code. :) Let's monitor the reset issue for a while. I guess some "reset" bug in MC 1.14 has been fixed or there is some "reset" bug in dev branch. Good to have the "powerlog" CLI, just in case. — Reply to this email directly, view it on GitHub <#1687?email_source=notifications&email_token=ASMB24KVCWGYV6PHHNL6H334TXI3VA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJXGQZDQNRSGM2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4174286234>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASMB24NZFZU2BN4RS3UMCBL4TXI3VAVCNFSM6AAAAACVBSMOL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNZUGI4DMMRTGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

terminalvelocity23 · 2026-04-02T09:54:10Z

@IoTThinks I'll try to build it off main with your patches and mine, too.

IoTThinks · 2026-04-02T10:08:55Z

@terminalvelocity23 Go ahead.

fizzyfuzzle · 2026-04-03T08:50:06Z

@IoTThinks I was running the main branch + your diff and after a little more then 24 hours it was reset. Fortunately I now got the Powerlog 😅

Last reset reason: Interrupt watchdog reset

Hope this can help ;)

IoTThinks · 2026-04-03T10:44:22Z

@fizzyfuzzle Great.
The powerlog helps.
I may guess the issue for this rare case.

Please help to try this firmware to see if there is any reset in the same position.
The version for this firmware is "PowerSaving14.1-FixedWDT" so you can know if you flash the correct one.
Thanks a lot for your effort.
https://github.com/IoTThinks/EasySkyMesh/tree/main/firmware/Testing/2026-04-03-PowerSaving14.1-TEST

fizzyfuzzle · 2026-04-03T12:00:13Z

@IoTThinks I flashed your new firmware let's see if it works 👌

fizzyfuzzle · 2026-04-04T06:44:56Z

@IoTThinks It just restarted again but now with a different powerlog:

Last reset reason: Panic / exception reset

terminalvelocity23 · 2026-04-04T06:58:52Z

Mine restarted too, with a "Panic / exception reset".

Built it from main with that diff above applied + PR #1954 and some run-once additions by myself.

IoTThinks · 2026-04-04T07:58:37Z

@fizzyfuzzle @terminalvelocity23 It is actually a progress for the rare case.
Let me bring up my MeshCore spammer to replicate the issue.

towerviewcams · 2026-04-04T12:48:19Z

@IoTThinks Sounds like boards are still restarting so I wont flash this.

IoTThinks · 2026-04-05T04:53:43Z

Heltec v4 + PS 14.1 has not crashed yet with 3 nodes (spam group text, fllood advert + sleep 0s and sleep 1s).
Duty cycle 100% with set af 1.0.

The buffer table for Heltec v4 is full after a while.
We spam alot but the Heltec v4 repeater will send one by one.
I will add a few more spammer nodes

I guess you use agc.reset.interval 4. So I set it also.
What custom commands do you use?

Well, I believe 1 node will automated generated spammer may bring down the entire network.
The only "protection" the buffer table of the TX packets.

beachmiles · 2026-04-05T07:11:27Z

@IoTThinks Just in case you haven't seen this.
https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/fatal-errors.html

I've never tried using the onboard jtag on the esp32-s3 but it evidently is decent and works with platform io.
https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/jtag-debugging/index.html

IoTThinks · 2026-04-05T07:46:16Z

@beachmiles Yes, I know about these fatal errors.
Just now, I can manage to hit the "Interrupt WDT Reset" after 2-hour hard spamming.

Sometimes it is harder to replicate than fix the rare to happen errors.
I'm testing the fix now.
Thanks for the links.

BTW, I'm quite interested in how MeshCore network can survive against spammers.

AI7NC · 2026-04-05T07:52:36Z

I have a V4.2 repeater running powersaving 14.1 Mar-29 build and it has reset twice in 3 days. So the behavior does seem to still be present.

IoTThinks · 2026-04-05T07:57:04Z

@AI7NC I'm doing the spam test against the fix now for Heltec v4.2.
Meanwhile, the time is still correct and advert is still continue to run.

AI7NC · 2026-04-05T08:00:58Z

Yes I can confirm that despite the resets, the auto-adverts are still working and the time is still correct.

…

On Sun, Apr 5, 2026 at 12:57 AM IoTThinks ***@***.***> wrote: *IoTThinks* left a comment (meshcore-dev/MeshCore#1687) <#1687 (comment)> @AI7NC <https://github.com/AI7NC> I'm doing the spam test against the fix now for Heltec v4.2. Meanwhile, the time is still correct and advert is still continue to run. — Reply to this email directly, view it on GitHub <#1687 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASMB24PGBBIW5LMXN4CKRBL4UIGWPAVCNFSM6AAAAACVBSMOL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOBYGQ4TAMRQGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

terminalvelocity23 · 2026-04-05T10:39:34Z

What custom commands do you use?

Here's my config.

set prv.key 'key'
set radio 868.7313232,62.5,7,7
set name 'name'
set repeat on
set lat 'lat'
set lon 'lon'
set tx 22
set direct.txdelay 0.5
set txdelay 1.5
set rxdelay 2
set af 2
set agc.reset.interval 8
password 'password'
set multi.acks 1
set radio.rxgain off
powersaving on

IoTThinks · 2026-04-05T16:47:46Z

@terminalvelocity23 My new fix servived 60 K MeshCore requests.
The fix is to use friendlier lock to the FreeTOS than the current Arduino lock.

I will test another 60K requests tomorrow.

Your CLI commands look "harmless" (no impact).

terminalvelocity23 · 2026-04-05T18:04:15Z

@IoTThinks good, because my repeater has crashed again. Panic / exception reset.

Theo-Marshall · 2026-04-05T18:05:36Z

I have a esp32c6 repeater that's been rock solid with an uptime of 38 days currently.

IoTThinks · 2026-04-06T09:38:00Z

@terminalvelocity23 @fizzyfuzzle @AI7NC Please help to test this.
The fix is to use friendlier lock to the FreeRTOS than the current Arduino lock.
The version is "PowerSaving14.1-FixedWDTMux".

I have tested it with 3 spammers (MeshCore companion usb).
You may use CLI "powerlog" to see the last reset log if any.
Thanks a lot.
https://github.com/IoTThinks/EasySkyMesh/tree/main/firmware/Testing/2026-04-03-PowerSaving14.1-TEST

terminalvelocity23 · 2026-04-06T10:01:22Z

@IoTThinks flashing now.

AI7NC · 2026-04-06T18:35:54Z

https://github.com/IoTThinks/EasySkyMesh/tree/main/firmware/Testing/2026-04-03-PowerSaving14.1-TEST

Is this for Heltec hardware V4.2 or hardware V4.3?

towerviewcams · 2026-04-06T23:18:44Z

https://github.com/IoTThinks/EasySkyMesh/tree/main/firmware/Testing/2026-04-03-PowerSaving14.1-TEST

Is this for Heltec hardware V4.2 or hardware V4.3?

14.1 has always covered both boards. I'm testing both at the house. so far so good at about 9 hours

AI7NC · 2026-04-06T23:29:32Z

Ok, my home repeater is running 14.1 4/6 build

IoTThinks · 2026-04-07T00:37:21Z

@AI7NC The bin file PS14.1 is for both Heltec 4.2 and 4.3.
It automatically detects Heltec 4.2 or 4.3 based on FEM control pin.

On Heltec 4.2, set radio.fem.rxgain on/off will return not supported
On Heltec 4.3, you can set it on/off.

IoTThinks marked this pull request as ready for review February 14, 2026 13:54

IoTThinks marked this pull request as draft February 14, 2026 14:11

IoTThinks added a commit to IoTThinks/EasySkyMesh that referenced this pull request Feb 14, 2026

Add files via upload

57133a1

meshcore-dev/MeshCore#1687

IoTThinks mentioned this pull request Feb 15, 2026

Heltec v4 remote management issue IoTThinks/EasySkyMesh#30

Closed

IoTThinks marked this pull request as ready for review February 15, 2026 03:20

IoTThinks mentioned this pull request Feb 16, 2026

To support PowerSaving for all ESP32-based repeaters and NRF52-based repeaters. #1353

Closed

IoTThinks mentioned this pull request Feb 18, 2026

Implement Powersaving for esp32 devices (Heltec v3/v4) #950

Open

etienn01 mentioned this pull request Apr 6, 2026

Add CLI control to LoRa's fem LNA. #2140

Open

Conversation

IoTThinks commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IoTThinks commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IoTThinks commented Feb 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IoTThinks commented Feb 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cra0 commented Feb 15, 2026

Uh oh!

towerviewcams commented Feb 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

beachmiles commented Feb 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IoTThinks commented Feb 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

beachmiles commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mikecarper commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

towerviewcams commented Feb 19, 2026

Uh oh!

beachmiles commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IoTThinks commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Theo-Marshall commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

beachmiles commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mikecarper commented Feb 20, 2026

Uh oh!

IoTThinks commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IoTThinks commented Feb 20, 2026

Uh oh!

IoTThinks commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

basiccode12 commented Feb 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IoTThinks commented Feb 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

basiccode12 commented Feb 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IoTThinks commented Feb 22, 2026

Uh oh!

IoTThinks commented Feb 22, 2026

Uh oh!

towerviewcams commented Apr 1, 2026

Uh oh!

terminalvelocity23 commented Apr 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IoTThinks commented Apr 2, 2026

Uh oh!

AI7NC commented Apr 2, 2026 via email

Uh oh!

terminalvelocity23 commented Apr 2, 2026

Uh oh!

IoTThinks commented Apr 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

IoTThinks commented Feb 13, 2026 •

edited

Loading

IoTThinks commented Feb 13, 2026 •

edited

Loading

IoTThinks commented Feb 14, 2026 •

edited

Loading

IoTThinks commented Feb 14, 2026 •

edited

Loading

towerviewcams commented Feb 15, 2026 •

edited

Loading

beachmiles commented Feb 17, 2026 •

edited

Loading

IoTThinks commented Feb 18, 2026 •

edited

Loading

beachmiles commented Feb 19, 2026 •

edited

Loading

mikecarper commented Feb 19, 2026 •

edited

Loading

beachmiles commented Feb 19, 2026 •

edited

Loading

IoTThinks commented Feb 20, 2026 •

edited

Loading

Theo-Marshall commented Feb 20, 2026 •

edited

Loading

beachmiles commented Feb 20, 2026 •

edited

Loading

IoTThinks commented Feb 20, 2026 •

edited

Loading

IoTThinks commented Feb 20, 2026 •

edited

Loading

basiccode12 commented Feb 21, 2026 •

edited

Loading

IoTThinks commented Feb 21, 2026 •

edited

Loading

basiccode12 commented Feb 21, 2026 •

edited

Loading

terminalvelocity23 commented Apr 1, 2026 •

edited

Loading

IoTThinks commented Apr 2, 2026 •

edited

Loading

fizzyfuzzle commented Apr 3, 2026 •

edited

Loading

terminalvelocity23 commented Apr 4, 2026 •

edited

Loading

towerviewcams commented Apr 4, 2026 •

edited

Loading

IoTThinks commented Apr 5, 2026 •

edited

Loading

IoTThinks commented Apr 5, 2026 •

edited

Loading

IoTThinks commented Apr 5, 2026 •

edited

Loading

IoTThinks commented Apr 6, 2026 •

edited

Loading