Possible new error in 0.9.19

Managed to get picroft working after moving from stable to unstable, but I think the upgrade to 0.9.19 has broken things. I’m getting the below error with wake word when starting. Haven’t made any other changes from when it was working. I can go back a version but thought you’d like to know. Prettyparse is still installed.

13:06:09.071 - mycroft.client.speech.listener:create_wake_word_recognizer:235 - INFO - creating wake word engine
13:06:09.081 - mycroft.client.speech.hotword_factory:create_hotword:268 - INFO - creating hey mycroft
13:06:09.118 - mycroft.client.speech.hotword_factory:init:125 - INFO - Found precise executable: /home/mycroft/.mycroft/precise/precise-stream/precise-stream
13:06:09.152 - mycroft.client.speech.listener:create_wakeup_recognizer:253 - INFO - creating stand up word engine
13:06:09.160 - mycroft.client.speech.hotword_factory:create_hotword:268 - INFO - creating wake up
13:06:09.581 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): api.mycroft.ai
[1239] Failed to execute script stream
Traceback (most recent call last):
File “precise/scripts/stream.py”, line 6, in
ImportError: No module named 'prettyparse’
Exception in thread Thread-14:
Traceback (most recent call last):
File “/usr/lib/python2.7/threading.py”, line 810, in __bootstrap_inner
self.run()
File “/usr/lib/python2.7/threading.py”, line 763, in run
self.__target(*self.__args, **self.__kwargs)
File “/usr/local/lib/python2.7/site-packages/mycroft_core-0.9.19-py2.7.egg/mycroft/client/speech/hotword_factory.py”, line 220, in check_stdout
self.has_found = float(line) > 0.5
ValueError: could not convert string to float:

13:06:10.983 - requests.packages.urllib3.connectionpool - DEBUG - https://api.mycroft.ai:443 “GET /v1/device/bf93b0b9-16dc-4057-a7a2-d638cbe5be71 HTTP/1.1” 200 4
12
13:06:11.054 - mycroft.messagebus.client.ws:on_open:58 - INFO - Connected
13:06:12.999 - mycroft.client.speech.mic:listen:523 - DEBUG - Waiting for wake word…
13:06:14.014 - mycroft.client.speech.mic:listen:523 - DEBUG - Waiting for wake word…

Hi, we switched to precise by default with the last release and for a while there was a bad build of precise-stream that was downloaded while it was on unstable. You can try to delete the precise folder

cd /home/mycroft/.mycroft/precise
rm -rf precise-stream

and then restart the mycroft-speech-client to start a new download

/etc/init.d/mycroft-speech-client stop
/etc/init.d/mycroft-speech-client start

Sorry for the delay.

Thank you. That seems to have cleared the wake word issue. Got another problem now as detailed below. I’m guessing I just need to clear down the intent cache? Also, precise-stream is gobbling huge amount of CPU. Is that related?

11:26:56.009 - SKILLS - DEBUG - {“type”: “padatious:register_entity”, “data”: {“file_name”: “/opt/mycroft/skills/mycroft-timer/vocab/en-us/duration.entity”, “n
ame”: “1711479508:duration”}, “context”: null}
11:26:56.032 - mycroft.skills.padatious_service:_register_object:89 - DEBUG - Registering Padatious entity: 1711479508:duration
11:26:56.062 - SKILLS - DEBUG - {“type”: “padatious:register_entity”, “data”: {“file_name”: “/opt/mycroft/skills/mycroft-timer/vocab/en-us/timervalue.entity”,
“name”: “1711479508:timervalue”}, “context”: null}
11:26:56.076 - mycroft.skills.padatious_service:_register_object:89 - DEBUG - Registering Padatious entity: 1711479508:timervalue
FANN Error 3: Wrong version of configuration file, aborting read of configuration file “/home/mycroft/.mycroft/intent_cache/1711479508:{timervalue}.intent.net”
.
11:26:56.103 - SKILLS - DEBUG - {“type”: “padatious:register_entity”, “data”: {“file_name”: “/opt/mycroft/skills/mycroft-timer/vocab/en-us/all.entity”, “name”:
“1711479508:all”}, “context”: null}
*** Error in `python2.7’: free(): invalid next size (normal): 0x74700ba8 ***