I don’t think that there is a defined limit. I run it with 50-60 tone sets with no problem.
TwoToneDetect71 Released
- Thread starter aaknitt
- Start date
- Status
jhow64
Newbie
A couple of questions:
1. Is there a way to edit the new GUI? For example, can you edit the adminMessage.html page to have the email/SMS and pushover checkboxes checked automatically. I tried to update the html files but nothing updates.
2. When you click save on the any of the pages, the text boxes go grey. Is that normal? On the adminMessage page it does nothing
1. Is there a way to edit the new GUI? For example, can you edit the adminMessage.html page to have the email/SMS and pushover checkboxes checked automatically. I tried to update the html files but nothing updates.
2. When you click save on the any of the pages, the text boxes go grey. Is that normal? On the adminMessage page it does nothing
I'm having an issue with TTD v71c on Windows 10. I had it on my old Windows 10 PC and it worked fine. I just upgraded to a newer computer and moved the folder over from the old PC to the new and installed Chrome. Now, on this new computer, it won't stay running for more than a few hours. At some point, after 1-6 hours (varies), it will stop updating the log/stop detecting pages/the audio level bar freezes. I have to close the window and reopen it.
There doesn't seem to be any errors in the log file/debug window...it just stops (and stops reporting the hourly retrieval of tone file config, that's how I know how long it worked for each time). The window is still open, just "frozen". There is no response on port 8181 once it freezes.
If it detects the tones during the time it is still working, it sends the email and all like normal.
The only other programs this computer runs are BlueIris (a security DVR software) and MeinburgNTP (an ntpd). The same two on the old PC, just this one is an i7 vs i3.
I'm going to look at using one of the heartbeat solutions to restart it, but that is just a fix for some kind of other problem that is happening.
There doesn't seem to be any errors in the log file/debug window...it just stops (and stops reporting the hourly retrieval of tone file config, that's how I know how long it worked for each time). The window is still open, just "frozen". There is no response on port 8181 once it freezes.
If it detects the tones during the time it is still working, it sends the email and all like normal.
The only other programs this computer runs are BlueIris (a security DVR software) and MeinburgNTP (an ntpd). The same two on the old PC, just this one is an i7 vs i3.
I'm going to look at using one of the heartbeat solutions to restart it, but that is just a fix for some kind of other problem that is happening.
Just to follow-up on my post. I wasn't able to find the root issue, but I did setup Windows Task Scheduler to kill the TTD/Chrome process every hour and restart it.
Attachments
Yes, which is why I'd recommend running 'Headless' when unattended...only fire up the GUI when you need it.
Andy
Recently upgraded to version 71c on a Raspberry Pi from version 67, mainly because the old Raspberry had seen better days and I had no idea where the image file I made was.
Only problem in particular I'm having is with the FTP uploads. I've got two departments that utilize this feature. For one, it works great. For the other, I can't get it to upload for anything. I've tried different FTP accounts, using the same FTP account...pretty much everything I know to do concerning troubleshooting. Here's what I'm guessing is the relevant portion of the log file:
Other than that, all the departments I've set it up for have nothing but praise for it. This is the first real problem I've come across in over five years. I greatly appreciate all the hard work, Andy (and anyone else who has contributed)!
Other relevant info:
•Running on Stretch, because Buster and I just weren't getting along
•Currently running this on a R-Pi 2. I've tried it on the same R-Pi, different R-Pis.
•I've tried running on the same network side-by-side, and different networks.
•I've tried using the FTP login that I know works on the one that doesn't, with no success.
•Everything is based off the same image. I just update the config and tone files as needed.
Only problem in particular I'm having is with the FTP uploads. I've got two departments that utilize this feature. For one, it works great. For the other, I can't get it to upload for anything. I've tried different FTP accounts, using the same FTP account...pretty much everything I know to do concerning troubleshooting. Here's what I'm guessing is the relevant portion of the log file:
Code:
setting mail server up
set up mail server
starting TLS
done starting TLS
logging in
logged in
MP3 Individual Email sent to REDACTED via smtp.gmail.com o$
Adding Sample Tone back to detection list after 4 second delay
MP3 Individual Email sent to REDACTED via smtp.gmail.com o$
FTP UPLOAD STARTS HERE
RETURNING AND REMOVING STUFF HERE
[]
Traceback (most recent call last):
File "/home/pi/TTD/TwoToneDetect71c.py", line 1155, in uploadFTP
File "/usr/lib/python2.7/ftplib.py", line 120, in __init__
self.connect(host)
error: [Errno 101] Network is unreachableOther than that, all the departments I've set it up for have nothing but praise for it. This is the first real problem I've come across in over five years. I greatly appreciate all the hard work, Andy (and anyone else who has contributed)!
Other relevant info:
•Running on Stretch, because Buster and I just weren't getting along
•Currently running this on a R-Pi 2. I've tried it on the same R-Pi, different R-Pis.
•I've tried running on the same network side-by-side, and different networks.
•I've tried using the FTP login that I know works on the one that doesn't, with no success.
•Everything is based off the same image. I just update the config and tone files as needed.
I'm wondering if this may be a DNS issue with the Pi. I've had some hair-pulling experiences with that at times, for no apparent reason. If you can determine the IP address of the FTP server try entering that in the "Upload FTP Server" field and see if that helps. Also double check and make sure the FTP port is correct.
Andy
Wow, Andy Got his response in just as I was about to hit post on the below:
Are you running two instances of TTD? There is basically one FTP setup for ftp transfer in TTD so I am wondering why you are referencing two different setups for your ftp. If the two departments you are referencing operate on different radio frequencies I can understand two instances. V71c has a web interface that v67 did not. Are you accessing the cfg files through the web interface? I agree 100% that Stretch is the way to go. I am running TTD on Buster in a couple applications but my production units are headless Stretch Lite. They are bulletproof.
Are you running two instances of TTD? There is basically one FTP setup for ftp transfer in TTD so I am wondering why you are referencing two different setups for your ftp. If the two departments you are referencing operate on different radio frequencies I can understand two instances. V71c has a web interface that v67 did not. Are you accessing the cfg files through the web interface? I agree 100% that Stretch is the way to go. I am running TTD on Buster in a couple applications but my production units are headless Stretch Lite. They are bulletproof.
I haven't thought about just directly entering the IP address. I'm going to set up a dummy system at some point, and I'll try that. It's just annoying, since literally everything else is equal on the two systems. I want to say I've even used the same config file on the two systems, and still had this problem. I'll try some more troubleshooting. Computers are weird.
No...these are on totally different Raspberry Pis -- different departments/organizations, in different cities/locations, with different radio systems. They operate regionally as mutual aid, but that's about it. The only common thing is they're trying to upload to the same web server, and I'm the one setting up the systems. They're basically wanting an easier way to review/archive dispatches other than manually pulling the MP3s from emails, so I thought the FTP method would work well. And it does -- when it cooperates!
Long time TwoTone user. Love the software! Question? Just upgraded to windows 10 machine and TT ver 71c. It appears that the audio file attachment is being sent as a wav file as opposed to mp3. MMS is rejecting the file size based on recording duration. Is there somewhere to change the attachment file type?
I apologize! Rookie mistake. FFMpeg was in wrong directory. All is good!
I'm having a very strange issue that I think might be Windows, but I'm unable to find a solution online so I'm hoping someone may have experienced it here. I have a fresh install of Windows 10 (build 1909, fully patched and all drivers up to date), a USB audio card that's connected to my scanner speaker out, two instances of ProScan running, and a single instance of TwoToneDetect v71c running in headless mode. All performance settings are maxed and I have disabled the options to allow Windows to power down idle devices.
If I am logged into the computer through remote desktop, I can start up TTD with no issues. The second I lock my desktop or disconnect from the remote session, though, I see the activity on the web UI freeze. When I log back in, the error "Failed to execute script twotonedetect71c". As long as I have my desktop screen up, TTD works. The second I lock it, either Windows kills the process or TTD fails. Nothing shows up in the TTD logs and nothing really stands out on the Windows event logs.
Has anyone else experienced this? I can't be the only one running TTD on a hidden away computer that has a locked desktop. Thanks!
If I am logged into the computer through remote desktop, I can start up TTD with no issues. The second I lock my desktop or disconnect from the remote session, though, I see the activity on the web UI freeze. When I log back in, the error "Failed to execute script twotonedetect71c". As long as I have my desktop screen up, TTD works. The second I lock it, either Windows kills the process or TTD fails. Nothing shows up in the TTD logs and nothing really stands out on the Windows event logs.
Has anyone else experienced this? I can't be the only one running TTD on a hidden away computer that has a locked desktop. Thanks!
I've gotten some reports of similar behavior, still trying to sort out the commonality in the reports. If I understand correctly you're logging in remotely to start TTD but are viewing the GUI from the browser of another computer on the LAN, not via the remote desktop software?
For what it's worth I've been able to reproduce some of the symptoms of some of the reports (again, not a lot of commonality so far) by intentionally putting the computer to sleep and bringing it back up. I do think this is somehow related to certain settings in Windows user accounts but haven't been able to reproduce it enough to find the root cause yet.
Andy
Yep, that's exactly correct. I suspect you're right since this was working on the same computer before I reformatted it. Since I know it's not just me, I'll keep playing around. One thing I noticed but had dismissed as an errant log was in the Windows security log indicating a session logoff (event id 4634, "This event is generated when a logon session is destroyed") at roughly the same time as I lock the computer.
Thanks for the work you do on this!
Yeah my hypothesis has been that Windows is logging the user out when they disconnect remote desktop. I hadn't heard reports of this happening while locking the computer locally though, so that's interesting new info. Please let me know if you're able to figure anything out, others will be grateful.
Thanks,
Andy
So, I found a solution that at least works for me. In looking through the Device Manager, Windows was creating the USB PnP Sound Device (it's one of the cheap 7.1 channel USB devices recommended on the TTD page) under the Sound, Video, and Game Controllers section. It also created Microphone and Speaker items under the Audio Inputs and Outputs section. On a hunch, I disabled the Microphone and Speaker items and found that TTD was skill happily listening away according to the audio level bar. A lock and unlock still killed the process though. A reboot brought those Microphone and Speaker items back in the Device Manager.
Switching the Audio Input Device to "Microsoft Sound Mapper - Input" in TTD worked as far as audio was concerned, again according to the audio level bar. After changing to this setting, I could lock and unlock, reboot, and login at will without any issues.
So, long story short -
1. Set the audio device as the default in Windows
2. Change Audio Input Device to "Microsoft Sound Mapper - Input"
3. If you have multiple USB cards, make sure that you can manage power settings. The one I have doesn't give the option.
Not sure if this works for other folks, but thought I'd share in case it does.
Thanks again!
Switching the Audio Input Device to "Microsoft Sound Mapper - Input" in TTD worked as far as audio was concerned, again according to the audio level bar. After changing to this setting, I could lock and unlock, reboot, and login at will without any issues.
So, long story short -
1. Set the audio device as the default in Windows
2. Change Audio Input Device to "Microsoft Sound Mapper - Input"
3. If you have multiple USB cards, make sure that you can manage power settings. The one I have doesn't give the option.
Not sure if this works for other folks, but thought I'd share in case it does.
Thanks again!
Kingmobileaudio
Member
Using pushover is there any way to set priority ? I want to be able to over ride do not disturb on device.
No, priority is not user-configurable in TTD, all notifications are sent priority 0, the default. It also appears from the Pushover documentation that priority 1 and 2 notifications only override a user’s Pushover quiet hours, not the “do not disturb” setting on the device. If you change the priority for a tone set, you are changing it for every subscriber to that set.
There is a relatively simple work-around to this. Write a python script that goes in the alert_command option of the tone set to trigger a high priority PO when the tones are decoded.
Here is what I used to use for a priority 1 PO that also includes the url to the BCFY stream in the push:
import httplib, urllib
conn = httplib.HTTPSConnection("api.pushover.net:443")
conn.request("POST", "/1/messages.json",
urllib.urlencode({
"token": "aqhmftnxavtmqxxxxxxxxxxx",
"user": "u5ciiyr8bob5cvrxxxxxxxxxxxx",
"message": "First Alarm",
"priority": "1",
"url": "http://audio1.broadcastify.com/174121",
"sound": "alien",
}), { "Content-type": "application/x-www-form-urlencoded" })
conn.getresponse()
This is based on the Pushing Messages section in the PO API instructions, Pushover: API
The example code included here, Example code and Pushover libraries | Pushover Support is quite helpful.
There is a relatively simple work-around to this. Write a python script that goes in the alert_command option of the tone set to trigger a high priority PO when the tones are decoded.
Here is what I used to use for a priority 1 PO that also includes the url to the BCFY stream in the push:
import httplib, urllib
conn = httplib.HTTPSConnection("api.pushover.net:443")
conn.request("POST", "/1/messages.json",
urllib.urlencode({
"token": "aqhmftnxavtmqxxxxxxxxxxx",
"user": "u5ciiyr8bob5cvrxxxxxxxxxxxx",
"message": "First Alarm",
"priority": "1",
"url": "http://audio1.broadcastify.com/174121",
"sound": "alien",
}), { "Content-type": "application/x-www-form-urlencoded" })
conn.getresponse()
This is based on the Pushing Messages section in the PO API instructions, Pushover: API
The example code included here, Example code and Pushover libraries | Pushover Support is quite helpful.
- Status
Similar threads
