Still says "default: 3" in the webui, fyi.3) MODIFIED: Upon a fresh installation, the default setting for the automatic ping test schedule is now set to every 5 minutes instead of every 3 minutes.
Still says "default: 3" in the webui, fyi.3) MODIFIED: Upon a fresh installation, the default setting for the automatic ping test schedule is now set to every 5 minutes instead of every 3 minutes.
Very good eye!! Thanks for catching it!!Still says "default: 3" in the webui, fyi.
Great catch!!!...
Token:
uW9AKwQwWosaIq_4EGyJFIDkBPVsUWgmIfSP_tP6n5RxeuDKhEExXj8vHDOLoCPtr60h1cMZWy9ehjv5vFaFog==
...
c7. Set InfluxDB API Token (v2.x only)
Currently: uW9AKwQwWosaIq_4EGyJFIDkBPVsUWgmIfSP_tP6n5RxeuDKhEExXj8vHDOLoCPtr60h1cMZWy9ehjv5vFaFog
cs. Send test data to InfluxDB
/jffs/scripts/connmon develop
No change.Great catch!!!
I just made a simple fix on the 'develop' branch. Please try the latest v3.0.10 development version:
Bash:/jffs/scripts/connmon develop
And just for my own sanity, cause full transparency I have not played with InfluxDB before last night.No change.
v3.0.10 on RT-BE88U
[Branch: develop]
From the router ui I enabled export ,pasted the correct token and saved but config file is still missing last two characters.
agagne@rt-be88u:/tmp/home/root# ls -ltr /opt/share/connmon.d/config
-rw-r--r-- 1 agagne root 1161 Dec 7 12:54 /opt/share/connmon.d/config
agagne@rt-be88u:/tmp/home/root# tail -1 /opt/share/connmon.d/config
NOTIFICATIONS_INFLUXDB_APITOKEN=uW9AKwQwWosaIq_4EGyJFIDkBPVsUWgmIfSP_tP6n5RxeuDKhEExXj8vHDOLoCPtr60h1cMZWy9ehjv5vFaFog
You must really mean from the router WebUI, because when I did a quick test using the CLI Main Menu UI options, the token remains intact:No change.
v3.0.10 on RT-BE88U
[Branch: develop]
From the router ui I enabled export ,pasted the correct token and saved but config file is still missing last two characters.
agagne@rt-be88u:/tmp/home/root# ls -ltr /opt/share/connmon.d/config
-rw-r--r-- 1 agagne root 1161 Dec 7 12:54 /opt/share/connmon.d/config
agagne@rt-be88u:/tmp/home/root# tail -1 /opt/share/connmon.d/config
NOTIFICATIONS_INFLUXDB_APITOKEN=uW9AKwQwWosaIq_4EGyJFIDkBPVsUWgmIfSP_tP6n5RxeuDKhEExXj8vHDOLoCPtr60h1cMZWy9ehjv5vFaFog
Please try the latest 'develop' branch v3.0.10_25120718 version of connmon.No change.
v3.0.10 on RT-BE88U
[Branch: develop]
Thanks the issue of saving the token using the router webui has been solved.Please try the latest 'develop' branch v3.0.10_25120718 version of connmon.
Once you verify that the issues you reported have been fixed, I can release the production version within 24 hours.
BTW, the same bug was affecting the setup of the Pushover notification.
View attachment 69425
HTH
Any way to see response code returned from attempting in write to the influxdb.Thanks the issue of saving the token using the router webui has been solved.
HELP [v3.0.10_25120718]
In the router webui I removed the token and hit save.
agagne@rt-be88u:/tmp/home/root# tail -1 /opt/share/connmon.d/config
NOTIFICATIONS_INFLUXDB_APITOKEN=
Then add token and hit save.
agagne@rt-be88u:/tmp/home/root# tail -1 /opt/share/connmon.d/config
NOTIFICATIONS_INFLUXDB_APITOKEN=uxifWDhieter42ZIZDInCPsHijF2p9E-3KHqFdTQEEm94VjSa41sVEIr7U9fX5HengK05Pe9FKdf10BvZz1gtg==
Good news. Thank you for verifying the fix.Thanks the issue of saving the token using the router webui has been solved.
HELP [v3.0.10_25120718]
Try the latest 'develop' branch v3.0.10_25120808 version.Any way to see response code returned from attempting in write to the influxdb.
All I get from running a test in either the webui or using connmon ui from command line is a failed message.
2025-12-08T06:16:36.000000-05:00 rt-be88u connmon_[24535]: Data failed to send to InfluxDB
curl command sent when testing/sending notifications using InfluxDB. This applies only to the CLI menu. Hopefully, this will be more helpful to figure out the source of the issues you're having when testing your InfluxDB setup.Good news. Thank you for verifying the fix.
Try the latest 'develop' branch v3.0.10_25120808 version.
I've made changes to capture and display errors from thecurlcommand sent when testing/sending notifications using InfluxDB. This applies only to the CLI menu. Hopefully, this will be more helpful to figure out the source of the issues you're having when testing your InfluxDB setup.
View attachment 69436
Like Spock would say: Fascinating!!v3.0.10 on RT-BE88U
[Branch: develop]
HELP [v3.0.10_25120808]
Something is not quite right with the InfluxDB export test now.
When I run it using connmon ui commandline it reports success. I have not seen any data show up in the database
so I deleted the bucket (pingtest) and I still get a success message. Since it is trying to write to a non-existent bucket I should
see errors in the InfluxDB logs but do not.
curl command and it returns a success code, I normally delete the temporary file that gets created. Now, for testing purposes, I simply commented out the line that deletes the file./tmp/var/tmp/temp_connmon.LOG
v3.0.10 on RT-BE88ULike Spock would say: Fascinating!!
When I input "bad" config settings, I get a failure along with some verbose output:
View attachment 69446
Try the latest 'develop' branch v3.0.10_25120811 version.
When executing thecurlcommand and it returns a success code, I normally delete the temporary file that gets created. Now, for testing purposes, I simply commented out the line that deletes the file.
So, after you run your test again, check the contents of the temporary file:
Code:/tmp/var/tmp/temp_connmon.LOG
agagne@rt-be88u:/tmp/mnt/rt-be88u/entware/home# cat /tmp/var/tmp/temp_connmon.LOG
2025-Dec-08 Mon 03:12:12 PM EST
Note: Unnecessary use of -X or --request, POST is already inferred.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 10.215.101.33:8086...
* Connected to 10.215.101.33 (10.215.101.33) port 8086
> POST /api/v2/write?bucket=pingtest&precision=s HTTP/1.1
> Host: 10.215.101.33:8086
> User-Agent: curl/8.4.0
> Accept: */*
> Authorization: Token uxifWDhieter42ZIZDInCPsHijF2p9E-3KHqFdTQEEm94VjSa41sVEIr7U9fX5HengK05Pe9FKdf10BvZz1gtg==
> Accept-Encoding: gzip
> Content-Length: 83
> Content-Type: application/x-www-form-urlencoded
>
} [83 bytes data]
< HTTP/1.1 400 Bad Request
< Content-Type: application/json; charset=utf-8
< X-Influxdb-Build: OSS
< X-Influxdb-Version: v2.7.12
< X-Platform-Error-Code: invalid
< Date: Mon, 08 Dec 2025 20:12:12 GMT
< Content-Length: 65
<
{ [65 bytes data]
100 148 100 65 100 83 24109 30786 --:--:-- --:--:-- --:--:-- 74000
* Connection #0 to host 10.215.101.33 left intact
agagne@rt-be88u:/tmp/mnt/rt-be88u/entware/home# cat /tmp/var/tmp/temp_connmon.LOG
2025-Dec-08 Mon 03:16:53 PM EST
Note: Unnecessary use of -X or --request, POST is already inferred.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 10.215.101.33:8086...
* Connected to 10.215.101.33 (10.215.101.33) port 8086
> POST /api/v2/write?bucket=pingtest&precision=s HTTP/1.1
> Host: 10.215.101.33:8086
> User-Agent: curl/8.4.0
> Accept: */*
> Authorization: Token uxifWDhieter42ZIZDInCPsHijF2p9E-3KHqFdTQEEm94VjSa41sVEIr7U9fX5HengK05Pe9FKdf10BvZz1gtg==
> Accept-Encoding: gzip
> Content-Length: 83
> Content-Type: application/x-www-form-urlencoded
>
} [83 bytes data]
< HTTP/1.1 400 Bad Request
< Content-Type: application/json; charset=utf-8
< X-Influxdb-Build: OSS
< X-Influxdb-Version: v2.7.12
< X-Platform-Error-Code: invalid
< Date: Mon, 08 Dec 2025 20:16:53 GMT
< Content-Length: 65
<
{ [65 bytes data]
100 148 100 65 100 83 25038 31972 --:--:-- --:--:-- --:--:-- 74000
* Connection #0 to host 10.215.101.33 left intact
I managed to get something working but unfortunately not with the function in connmon script as it exists.v3.0.10 on RT-BE88U
[Branch: develop]
HELP [v3.0.10_25120811]
Run test:
Choose an option: cs
Data sent to InfluxDB successfully
Code:agagne@rt-be88u:/tmp/mnt/rt-be88u/entware/home# cat /tmp/var/tmp/temp_connmon.LOG 2025-Dec-08 Mon 03:12:12 PM EST Note: Unnecessary use of -X or --request, POST is already inferred. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 10.215.101.33:8086... * Connected to 10.215.101.33 (10.215.101.33) port 8086 > POST /api/v2/write?bucket=pingtest&precision=s HTTP/1.1 > Host: 10.215.101.33:8086 > User-Agent: curl/8.4.0 > Accept: */* > Authorization: Token uxifWDhieter42ZIZDInCPsHijF2p9E-3KHqFdTQEEm94VjSa41sVEIr7U9fX5HengK05Pe9FKdf10BvZz1gtg== > Accept-Encoding: gzip > Content-Length: 83 > Content-Type: application/x-www-form-urlencoded > } [83 bytes data] < HTTP/1.1 400 Bad Request < Content-Type: application/json; charset=utf-8 < X-Influxdb-Build: OSS < X-Influxdb-Version: v2.7.12 < X-Platform-Error-Code: invalid < Date: Mon, 08 Dec 2025 20:12:12 GMT < Content-Length: 65 < { [65 bytes data] 100 148 100 65 100 83 24109 30786 --:--:-- --:--:-- --:--:-- 74000 * Connection #0 to host 10.215.101.33 left intact
Odd even after re-creating the pingtest bucket, removing the /tmp/var/tmp/temp_connmon.LOG and
re-running the test I get the same message.
Code:agagne@rt-be88u:/tmp/mnt/rt-be88u/entware/home# cat /tmp/var/tmp/temp_connmon.LOG 2025-Dec-08 Mon 03:16:53 PM EST Note: Unnecessary use of -X or --request, POST is already inferred. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 10.215.101.33:8086... * Connected to 10.215.101.33 (10.215.101.33) port 8086 > POST /api/v2/write?bucket=pingtest&precision=s HTTP/1.1 > Host: 10.215.101.33:8086 > User-Agent: curl/8.4.0 > Accept: */* > Authorization: Token uxifWDhieter42ZIZDInCPsHijF2p9E-3KHqFdTQEEm94VjSa41sVEIr7U9fX5HengK05Pe9FKdf10BvZz1gtg== > Accept-Encoding: gzip > Content-Length: 83 > Content-Type: application/x-www-form-urlencoded > } [83 bytes data] < HTTP/1.1 400 Bad Request < Content-Type: application/json; charset=utf-8 < X-Influxdb-Build: OSS < X-Influxdb-Version: v2.7.12 < X-Platform-Error-Code: invalid < Date: Mon, 08 Dec 2025 20:16:53 GMT < Content-Length: 65 < { [65 bytes data] 100 148 100 65 100 83 25038 31972 --:--:-- --:--:-- --:--:-- 74000 * Connection #0 to host 10.215.101.33 left intact
I think you have found either a bug in the original implementation or the original API for InfluxDB may have changed since the initial implementation. Either way, that's a great find!!I managed to get something working but unfortunately not with the function in connmon script as it exists.
Attached is a script I made from your function to use as a test harness.
I had to add org to the InfluxDB api url and changed the payload to get things working.
/tmp/var/tmp/temp_connmon_curl_ERR.LOG
/tmp/var/tmp/temp_connmon_curl_OUT.LOG
I think you have found either a bug in the original implementation or the original API for InfluxDB may have changed since the initial implementation. Either way, that's a great find!!
Would you mind trying the latest 'develop' branch v3.0.10_25120908 version?
After you run your test again, please post the contents of the following files:
I'm also curious to see if this is a difference between the v1.8 and v2.0 InfluxDB API versions.Code:/tmp/var/tmp/temp_connmon_curl_ERR.LOG /tmp/var/tmp/temp_connmon_curl_OUT.LOG
agagne@rt-be88u:/tmp/mnt/rt-be88u/entware/home# ls -ltr /tmp/var/tmp/
-rw-rw-rw- 1 agagne root 151 Dec 9 12:45 temp_connmon_curl_OUT.LOG
-rw-rw-rw- 1 agagne root 1080 Dec 9 12:45 temp_connmon_curl_ERR.LOG
Apologies for my delayed reply; I got busy with my day job, so I waited until my lunch time to take a look at your feedback. Thank you for the helpful response and the test/debug results.v3.0.10 on RT-BE88U
[Branch: develop]
HELP [v3.0.10_25120908]
Run Test:
Choose an option: cs
Data failed to send to InfluxDB [Code: 999]
Code:agagne@rt-be88u:/tmp/mnt/rt-be88u/entware/home# ls -ltr /tmp/var/tmp/ -rw-rw-rw- 1 agagne root 151 Dec 9 12:45 temp_connmon_curl_OUT.LOG -rw-rw-rw- 1 agagne root 1080 Dec 9 12:45 temp_connmon_curl_ERR.LOG
I believe that the org requirement is a v2 change. Not sure of the payload.
https://docs.influxdata.com/influxdb/v2/write-data/developer-tools/api/
/tmp/var/tmp/temp_connmon_curl_ERR.LOG
/tmp/var/tmp/temp_connmon_curl_OUT.LOG
Apologies for my delayed reply; I got busy with my day job, so I waited until my lunch time to take a look at your feedback. Thank you for the helpful response and the test/debug results.
Would you mind testing the latest 'develop' branch v3.0.10_25120912 version?
I've now added the new "InfluxDB Organization" parameter to the WebUI and CLI menus which, as you found out, is now required for InfluxDB notifications.
View attachment 69455
View attachment 69457
After you run your test again, please post the contents of the following files:
Code:/tmp/var/tmp/temp_connmon_curl_ERR.LOG /tmp/var/tmp/temp_connmon_curl_OUT.LOG
Take your time. I'll be busy the rest of the afternoon, so I won't be checking my secondary emails until the evening after work hours.
Thanks.
agagne@rt-be88u:/tmp/mnt/rt-be88u/entware/home# ls -ltr /tmp/var/tmp
-rw-rw-rw- 1 agagne root 145 Dec 9 16:46 temp_connmon_curl_OUT.LOG
-rw-rw-rw- 1 agagne root 1080 Dec 9 16:46 temp_connmon_curl_ERR.LOG

Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!