Connection Refused about remoteid-mqtt-subscriber HOT 6 CLOSED

Thanks! I was able to get connected and am receiving the status message every minute. Is this result in the DRONESCOUT screen a concern?

......
threshold_WLAN_USB: -200 dBm
threshold_BT_UART: -200 dBm
threshold_BT_USB: -200 dBm
mqtt localhost 1883 60
sh: 1: ubus: not found
Create monitor thread
Create license thread
Create wlan1 thread
Create wlan2 thread
create wlan hopping thread
channel index 0 | 1
........
ls: cannot access '/proc/net/rtl8*/wlx30eb1f4d9d32/monitor': No such file or directory
INFO: device license activated!
ls: cannot access '/proc/net/rtl8*/wlx30eb1f4d9c65/monitor': No such file or directory
..........

It also seems to crash the application when I connect to the DRONESCOUT screen.

No it does not crash, it is more debug information that normal users would not see. I included it in my answer to show you where the application was started already. Background, depending on the installed WLAN driver, the method of hopping to different WLAN channels is different. The above error message is a result of trying one of the methods.

from remoteid-mqtt-subscriber.

Well, normally you don't need to do the screen -R DRONESCOUT command. All mqtt debug info is in /tmp/mqtt.log. Having said that, to detach a screen, use this key combination: Ctrl+a followed by d. See this link. Very likely you exited the screen instead.

from remoteid-mqtt-subscriber.

Hi, fastest support is by sending an email to [email protected]
Of course, no problem to post an issue here.

• Normally the dronescout.arm64 application is already started when you boot the device. It is in the screen DRONESCOUT.

root@ds221000000230:~# screen -R
There are several suitable screens on:
        3014.DUMMY      (01/24/2024 11:34:49 AM)        (Detached)
        3010.WATCHDOG   (01/24/2024 11:34:49 AM)        (Detached)
        3000.REMOTE     (01/24/2024 11:34:49 AM)        (Detached)
        2997.DRONESCOUT (01/24/2024 11:34:49 AM)        (Detached)

It can be accessed via screen -R DRONESCOUT If you run it twice there will be unexpected behavior as the application is started twice.

In the latest firmware 20240108-1539, the application provides MQTT debugging output in file /tmp/mqtt.log

If successful, the latest line in this file reads "INFO MQTT: connecting and publishing data". In the latest manual, the different MQTT error codes are described in the section troubleshooting.

So having said above:

• the application is killed, because likely the watchdog scripts detects an error and as a result will kill all dronescout applications.
• I assume that IP address 192.168.0.129 is the IP address of the sensor. Is so, did you follow the steps in 2.5 of the manual to install the MQTT broker on the sensor? If you installed it on another device, please make sure it allows anonymous connections i.e. add "listener 1883" and "allow_anonymous true" to the mosquitto.conf file. In the default setup the MQTT broker is not installed due to security concerns. (If it is not used, it is better to have it not installed by default.)
• The error ConnectionRefusedError: [Errno 111] Connection refused typically means that the script cannot connect to the MQTT broker.

from remoteid-mqtt-subscriber.

Thanks! I was able to get connected and am receiving the status message every minute. Is this result in the DRONESCOUT screen a concern?

QoSlevel: 1
username:
password:
keepalive: 60
clientID: ds01240100000298
SSL mode: 0
SSL verify: 0
SSL CA file: /root/certs/ca.crt
SSL CRT file: /root/certs/client.crt
SSL KEY file: /root/certs/client.key
interface WLAN 1: wlx30eb1f4d9d32
interface WLAN 2: wlx30eb1f4d9c65
interface BT UART 1: /dev/ttyACM0
interface BT USB 1: hci0
threshold_WLAN_USB: -200 dBm
threshold_BT_UART: -200 dBm
threshold_BT_USB: -200 dBm
mqtt localhost 1883 60
sh: 1: ubus: not found
Create monitor thread
Create license thread
Create wlan1 thread
Create wlan2 thread
create wlan hopping thread
channel index 0 | 1
channel index 1 | 2
channel index 2 | 3
channel index 3 | 4
channel index 4 | 5
channel index 5 | 6
channel index 6 | 44
channel index 7 | 149
channel index 8 | 7
channel index 9 | 8
channel index 10 | 9
channel index 11 | 10
channel index 12 | 11
channel index 13 | 13
channel index 14 | 6
channel index 15 | 149
channel index 16 | 44
channel index 17 | 36
channel index 18 | 40
channel index 19 | 48
channel index 20 | 52
channel index 21 | 56
channel index 22 | 60
channel index 23 | 64
channel index 24 | 149
channel index 25 | 6
channel index 26 | 44
channel index 27 | 161
channel index 28 | 165
ls: cannot access '/proc/net/rtl8*/wlx30eb1f4d9d32/monitor': No such file or directory
INFO: device license activated!
ls: cannot access '/proc/net/rtl8*/wlx30eb1f4d9c65/monitor': No such file or directory

It also seems to crash the application when I connect to the DRONESCOUT screen.

from remoteid-mqtt-subscriber.

Was able to successfully receive remote ID data from a drone.

from remoteid-mqtt-subscriber.

I think since I am unfamiliar with the screen command I may not using it properly, but when i attempt to attach to DRONESCOUT using screen -R DRONESCOUT it stops reporting to the MQTT subscriber. Just wanted to point this out in case there was something not correct about this, but it is not an issue as long as i don't run that command.

Thanks again for the assistance.

from remoteid-mqtt-subscriber.