Skip to main content

TwoToneDetect Suddenly Stops - Troubleshooting

Steve
  • Updated

 

When TwoToneDetect (TTD) goes "offline," it usually refers to one of two things: the program has stopped running, or it has lost its connection to IamResponding.

Because TTD is often a "set it and forget it" tool, sudden outages are usually triggered by environmental changes or automatic updates.

1. Check Service Connectivity (The "Cloud" Link)

If TTD looks like it’s running but alerts aren't reaching your IaR Website Dashboard, the issue is likely the handshake between TTD and IamResponding.

  • IamResponding (IaR) Users: TTD uses an API key to talk to IaR. If you see "Error 401" or "Unauthorized" in the log, your API key may have expired or was reset in the IaR portal.

  • Internet Stability:  

    • On Raspberry Pi: Use ping google.com in the terminal. If it fails, your Pi may have dropped its Wi-Fi/Ethernet lease.

    • On Windows: Ensure a Windows Update didn't trigger a "Public" network profile, which can sometimes block outgoing TTD traffic via the firewall.

2. Check for Software Crashes

TTD is a Python-based application. If the underlying environment shifts, the program will close.

  • The Log File (log.txt): This is your best friend. Look at the very bottom of the file in your TTD folder.

    • "PortAudio Error": This means TTD lost its connection to the sound card.

    • "Memory Error": On a Raspberry Pi, if you aren't clearing out old .wav recordings, the SD card might be full, causing TTD to crash when it tries to write a new file.

  • Automatic Updates: 

    • Windows: Windows Update often restarts the computer. If TTD isn't in your "Startup" folder, it won't restart automatically.

3. Check Hardware "Vanishing"

Computers occasionally "drop" USB devices to save power or due to driver glitches.

  • USB Sleep Settings (Windows): Windows may "suspend" USB ports to save power. Disable "USB Selective Suspend" in your Power Options.

  • Ghost Sound Cards: If you unplugged the USB sound card and plugged it into a different port, Windows or Linux might assign it a new ID (e.g., changing from "Device 1" to "Device 2"). TTD will still be looking for "Device 1" and will show an error.

  • Power Supply (Raspberry Pi): A sudden "offline" status on a Pi is often caused by a weak power supply. When the USB sound card and Wi-Fi chip both draw peak power during a transmission, the Pi may suffer a "brownout" and reboot or freeze.

4. Troubleshooting Steps (Action Plan)

  1. Restart the Hardware: It’s a cliché for a reason. Power cycling the Pi or PC may erase existing log files, so be sure to capture them (if needed) before restarting.

  2. Verify the Audio Input: Open the TTD GUI. Is the "Audio Input Device" still showing your sound card by name? If it says "Default" or is blank, TTD can't connect to the hardware.

  3. Check the "Heartbeat": If you are a pro user, check the heartbeat.txt file. If the timestamp hasn't updated in the last 60 seconds, the program is frozen.

  4. Clear Space: Delete old recording folders. A full disk is a common silent killer for TTD on Raspberry Pis.

Pro Tip: If you are running on a Raspberry Pi, use the command journalctl --user -u ttd -f to see a real-time feed of what is breaking. It will tell you exactly why the "listener" is failing.

 

 

 

Related articles