razzo04 / rhasspy-mobile-app

A simple mobile app for rhasspy.
MIT License
118 stars 13 forks source link

Start wake word - Rhasspy mobile app keeps stopping #12

Open gitisz opened 2 years ago

gitisz commented 2 years ago

I am using latest 1.7.0 on a Samsung Galaxy S9+ and Lenovo Yoga tab and upon configuring UDP, and selecting "Start wake word", the app immediately crashes. The log located at com.example.rhasspy_mobile_app/files/log.txt only shows evidence that MQTT successfully connected, otherwise there is no stack trace.

The mobile app is set to

Rhasspy base:

{
    "dialogue": {
        "system": "rhasspy"
    },
    "intent": {
        "system": "fsticuffs"
    },
    "microphone": {
        "system": "pyaudio"
    },
    "mqtt": {
        "enabled": true,
        "host": "[fqdn]",
        "password": "[password]",
        "site_id": "rhasspy",
        "username": "[username]"
    },
    "sounds": {
        "system": "aplay"
    },
    "speech_to_text": {
        "system": "kaldi"
    },
    "text_to_speech": {
        "system": "nanotts"
    },
    "wake": {
        "porcupine": {
            "keyword_path": "",
            "sensitivity": "0.9",
            "udp_audio": "0.0.0.0:12333:rhasspy"
        },
        "system": "porcupine"
    }
}

Any thoughts on what might be misconfigured or how/where to identify the exception?

gitisz commented 2 years ago

The app no longer crashes when setting [ip]:[port] vs [fqdn]:[port] in the mobile app ... a little unfamiliar with UDP, but shouldn't DNS still be honored?

razzo04 commented 2 years ago

DNS is still honored with UDP but the app doesn’t check if the supplied an FQDN but it assumes that it is a standard ip address. In the next release, I will make sure that the domain is resolved before sending the UDP packet.