I upgraded to Homeassistant 88.1 and Snips 61.1 and they are not playing well together. Before either update the system worked perfectly. (I rolled back to a previous image and tried reversing the upgrade order.) It is only when both are upgraded to the current version is the issue seen. I see the intents and the slot names are being properly recognized using snips-watch, but Homeassistant is not picking it up. I have restarted the computer several times and have tried restarting both services 2 or 3 different ways and in different orders.
I discovered the issue. HBMQTT, like Hermes, uses ‘probability’. This has been changed to ‘confidence_score’. Here is the traceback information:
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/snips/init.py”, line 108, in message_received
if (request[‘intent’][‘probability’]
KeyError: ‘probability’
To make it work again, replace the 4 instances of ‘probability’ with ‘confidenceScore’.
Works like a charm to restore functionality.
I should clarify for those who are not used to doing this:
Just go to the location: “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/snips"
list the files
copy the file name to make sure you have the proper number of underscores
edit the file
Search and replace lowercase ‘probability’ surrounded by ’ ’ with ‘confidenceScore’ .
Save
reload Homeassistant
Yo’ da MAN! I thank you, and my poor overworked Alexa thanks you.
BTW, my file wasn’t init.py, but snips.py in the components directory.
I am assuming, based on our other thread you are using Hermes. That may be the location of Hermes or the Alexa component, I assume.
It may also be because I’m on 87.1, I see you quoted 88.1. I’m not referencing Alexa as a component, she’s autonomous.
I think I jumped to the conclusion I was using Hermes, and not really, because my assistant’s requirements.txt listed hermes-python.
Hi,
Is there a way to modify this file on Hassio?
I’m currious if there is anything we can do on Hassio as well. It appears the fix is in the dev channel, but won’t be released until next week with .89
I don’t know. If you look at the error log, it will tell you the directory and file name.