[Bug]: Unconfigured user button has a reading

[gendebeat]

Category

Other

Hardware

Rak4631

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.7.15.567b8ea

Description

Hi, I've been noticing for days that my RAK19003 boards with RAK4630 are restarting randomly. At first, I thought it might be due to Bluetooth disconnecting, but after checking the logs, I can see that everything disconnects (BT, USB) and then it reboots.

Could there be an issue with the USER BUTTON? Is that why it's restarting? I don't have any physical button. The button pin is at 0. thanks

Relevant log output

INFO  | 20:39:56 209 [EnvironmentTelemetry] Send: voltage=0.000000, IAQ=0, distance=0.000000, lux=0.000000
INFO  | 20:39:56 209 [EnvironmentTelemetry] Send: wind speed=0.000000m/s, direction=0 degrees, weight=0.000000kg
INFO  | 20:39:57 209 [EnvironmentTelemetry] Send: radiation=0.000000##R/h
INFO  | 20:39:57 209 [EnvironmentTelemetry] Send: soil_temperature=0.000000, soil_moisture=0
DEBUG | 20:39:57 209 [EnvironmentTelemetry] Partially randomized packet id 1121328581
INFO  | 20:39:57 209 [EnvironmentTelemetry] Send packet to phone
INFO  | 20:39:57 209 Tell client we have new packets 34
INFO  | 20:39:57 209 BLE notify fromNum
INFO  | 20:39:57 209 [UserButton] LONG PRESS RELEASE AFTER 60029 MILLIS
INFO  | 20:39:57 209 [UserButton] Input event 155! kb 0
DEBUG | 20:39:57 209 Save to disk 31
DEBUG | 20:39:57 209 Opening /prefs/config.proto, fullAtomic=1
DEBUG | 20:39:57 209 FromRadio=STATE_SEND_PACKETS
DEBUG | 20:39:57 209 phone downloaded packet (id=0x42d61dc5 fr=0xb3dabd3a to=0xffffffff, transport = 0, WantAck=0, HopLim=4 Ch=0x0 Portnum=67 rxtime=1769200797 priority=10)
INFO  | 20:39:57 209 Save /prefs/config.proto
DEBUG | 20:39:57 210 Opening /prefs/module.proto, fullAtomic=1
INFO  | 20:39:58 211 Save /prefs/module.proto
DEBUG | 20:39:59 211 Opening /prefs/channels.proto, fullAtomic=1
INFO  | 20:39:59 211 Save /prefs/channels.proto
DEBUG | 20:39:59 212 Opening /prefs/device.proto, fullAtomic=1
INFO  | 20:40:00 212 Save /prefs/device.proto
DEBUG | 20:40:00 213 Opening /prefs/nodes.proto, fullAtomic=0
INFO  | 20:40:01 213 Save /prefs/nodes.proto
INFO  | 20:40:01 213 toRadioWriteCb data 0x20025a22, len 49
DEBUG | 20:40:01 213 New ToRadio packet
DEBUG | 20:40:01 213 PACKET FROM PHONE (id=0xcde8ad24 fr=0x00000000 to=0xb3dabd3a, transport = 0, WantAck=0, HopLim=4 Ch=0x0 Portnum=3 priority=10)
DEBUG | 20:40:01 213 Enqueued local (id=0xcde8ad24 fr=0x00000000 to=0xb3dabd3a, transport = 0, WantAck=0, HopLim=4 Ch=0x0 Portnum=3 rxtime=1769200801 priority=10)
DEBUG | 20:40:01 213 FromRadio=STATE_SEND_PACKETS
INFO  | 20:40:01 214 Enter deep sleep forever
INFO  | 20:40:01 214 Disable NRF52 bluetooth
INFO  | 20:40:01 214 BLE Disconnected, reason = 0x16
DEBUG | 20:40:01 214 PhoneAPI::close()
DEBUG | 20:40:01 214 BluetoothStatus DISCONNECTED
INFO  | 20:40:01 214 Ended BLE connection
WARNING file:stream_interface.py __reader line:216 Meshtastic serial port disconnected, disconnecting... ClearCommError failed (PermissionError(13, 'El dispositivo no reconoce el comando.', None, 22))

[github-actions]

@gendebeat, Welcome to Meshtastic! 👋

Thanks for opening your first issue. If it's helpful, an easy way
to get logs is the "Open Serial Monitor" button on the Web Flasher.

If you have ideas for features, note that we often debate big ideas
in the discussions tab
first. This tracker tends to be for ideas that have community
consensus and a clear implementation.

We're very active on discord,
especially the #firmware and #alphanauts-testing channels. If you'll
be around for a while, we'd love to see you there!

Welcome to the community! ❤️

[thebentern]

Do you happen to have a GPS module installed?

[gendebeat]

Do you happen to have a GPS module installed?

no, i dont. I have a switch on the battery. I'm seeing that if I make it vibrate, the LEDs are affected. Maybe it's introducing noise into the GPIO. Perhaps it's more of a hardware issue. I'm going to remove the switch to rule it out.

[BrandtWoolf]

I am seeing reboots on my RAK19007 with RAK4631 about every 15 minutes with a similar "error" mentioned above. I do have a GPS module RAK12500 and I see warned related to GPS. I am running 2.7.15. Could these be related?

INFO  | 00:42:51 905 Tell client we have new packets 86
INFO  | 00:42:51 905 BLE notify fromNum
DEBUG | 00:42:51 905 FromRadio=STATE_SEND_PACKETS
DEBUG | 00:42:51 905 phone downloaded packet (id=0x192321c8 fr=0xa8923b66 to=0xffffffff, transport = 1, WantAck=0, HopLim=1 Ch=0x0 Portnum=67 rxtime=1769233371 rxSNR=6 rxRSSI=-45
WARN  | 00:42:51 905 [GPS] Couldn't publish a valid location: didn't get a GPS lock in time
DEBUG | 00:42:51 905 [GPS] Took 900s to get lock
DEBUG | 00:42:51 905 [GPS] Predict 0s to get next lock
DEBUG | 00:42:51 905 [GPS] 119s until next search
DEBUG | 00:42:51 905 [GPS] gps_update_interval >= 0s needed to justify hardsleep
INFO  | 00:42:51 905 [GPS] GPS power state move from ACTIVE to HARDSLEEP
INFO  | 00:42:51 905 [DeviceTelemetry] Send: air_util_tx=0.984556, channel_utilization=5.293333, battery_level=101, voltage=4.282000, uptime=905
DEBUG | 00:42:51 905 [DeviceTelemetry] Partially randomized packet id 4003693405
DEBUG | 00:42:51 905 [DeviceTelemetry] updateTelemetry LOCAL
DEBUG | 00:42:51 905 [DeviceTelemetry] Node status update: 32 online, 80 total
INFO  | 00:42:51 905 [DeviceTelemetry] Send packet to phone
INFO  | 00:42:51 905 Tell client we have new packets 87
INFO  | 00:42:51 905 BLE notify fromNum
DEBUG | 00:42:52 905 [Power] Battery: usbPower=1, isCharging=1, batMv=4282, batPct=100
DEBUG | 00:42:52 905 FromRadio=STATE_SEND_PACKETS
DEBUG | 00:42:52 905 phone downloaded packet ()
INFO  | 00:42:52 905 [UserButton] LONG PRESS RELEASE AFTER 899838 MILLIS
INFO  | 00:42:52 905 [UserButton] Input event 155! kb 0
DEBUG | 00:42:52 905 Save to disk 31
DEBUG | 00:42:52 905 Opening /prefs/config.proto, fullAtomic=1
INFO  | 00:42:52 906 Save /prefs/config.proto
DEBUG | 00:42:53 906 Opening /prefs/module.proto, fullAtomic=1
INFO  | 00:42:53 907 Save /prefs/module.proto
DEBUG | 00:42:54 907 Opening /prefs/channels.proto, fullAtomic=1
INFO  | 00:42:54 908 Save /prefs/channels.proto
DEBUG | 00:42:55 908 Opening /prefs/device.proto, fullAtomic=1
INFO  | 00:42:55 909 Save /prefs/device.proto
DEBUG | 00:42:56 909 Opening /prefs/nodes.proto, fullAtomic=0
INFO  | 00:42:56 910 Save /prefs/nodes.proto
INFO  | 00:42:57 911 Enter deep sleep forever
INFO  | 00:42:57 911 Disable NRF52 bluetooth
INFO  | 00:42:57 911 BLE Disconnected, reason = 0x16
DEBUG | 00:42:57 911 PhoneAPI::close()
DEBUG | 00:42:57 911 BluetoothStatus DISCONNECTED
INFO  | 00:42:57 911 Ended BLE connection
DEBUG | 00:42:57 911 SX126x entering sleep mode
DEBUG | 00:42:57 911 Started Tx (id=0x4ddda723 fr=0x1388bbf3 to=0xffffffff, transport = 1, WantAck=0, HopLim=0 Ch=0x8 encrypted len=107 rxtime=1769233368 rxSNR=5.5 rxRSSI=-43 via
DEBUG | 00:42:57 911 1 packets remain in the TX queue
DEBUG | 00:42:57 911 Packet TX: 1050ms
DEBUG | 00:42:57 911 Completed sending (id=0x4ddda723 fr=0x1388bbf3 to=0xffffffff, transport = 1, WantAck=0, HopLim=0 Ch=0x8 encrypted len=107 rxtime=1769233368 rxSNR=5.5 rxRSSI=-
INFO  | 00:42:57 911 GPS deep sleep!
INFO  | 00:42:57 911 GPS power state move from HARDSLEEP to OFF
WARNING file:stream_interface.py __reader line:216 Meshtastic serial port disconnected, disconnecting... read failed: [Errno 6] Device not configured

[gendebeat]

i dont know. but i havent GPS, and y put configuation to NOT_PRESENT

[gendebeat]

The physical switch definitely has nothing to do with this. I deactivated it and I'm still getting the same reset at night. I just got up and the node had only been running continuously for 2 hours (of course I sleep more than 2 hours, even though this problem is robbing me of sleep, because it's maddening). For what it's worth, just now I had the USB connected for the log and Bluetooth connected, and it reset twice in less than 5 minutes with the same "USER_BUTTON" error.

Do you think you have more resets with BT connected? Without a doubt, that's the way I notice it the most, as it's maddening to see it randomly disconnect from the phone.

Here's another point that might be helpful.
I have another node that is exactly the same. It was the one I was testing to carry with me always. It was on this hardware that I first noticed this problem. A few days ago, truth be told, and desperate, I reset it, flashed it again several times doing tests, and curiously it doesn't reset anymore. It's been running for 11 hours now.

I'll check if I can compare the configurations. But I'd swear they are identical.

Thanks.

[BrandtWoolf]

@gendebeat what happens if you set your Button GPIO to 31? (like you were actually connecting a button to the rak19007)

I was able to get past an uptime of 15 minutes once I set this. I could reproduce the reboot at 15 minutes with my GPS module attached and the Button GPIO set Unset in the iOS app. If the GPS module was disconnected, I have no reboot issues with either Button GPIO setting.

This also appears to have addressed my random screen updates like I was pressing a button.

Again to be clear, I have no button connected at all.

I think there is an actual bug around the Button GPIO as Unset. I am continuing to test and will update if I have any more findings.

[gendebeat]

Indeed, I didn’t try your solution because I looked for another alternative! But knowing this, I’m sure everything is related.
I didn’t mention (sorry) that I have a barometric sensor in slot D. When I disabled environment telemetry, it started working correctly. Then I remembered your GPS! My log shows a button read error right after the barometric sensor reading.

I can avoid the reboot:
1-Either by disabling environment telemetry, or
2-By moving the barometric sensor to slot C.

I also have a base board 19007, and if I put the sensor in slot D, the same error occurs.

So I deduce that the problem comes from GPIOs IO5 or IO6.
By not initializing a button as you mentioned, these GPIOs might remain assigned or something similar. I’m not familiar with firmware programming. Thanks.