Core: Snips update required

Created on 2 Dec 2018  路  12Comments  路  Source: home-assistant/core

Home Assistant release with the issue:
0.82.1

Last working Home Assistant release (if known):
?

Operating environment (Hass.io/Docker/Windows/etc.):
DietPi +Hass.io

Component/platform:
Snips.ai component

Description of problem:
Error in addon logs

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

snips:

Traceback (if applicable):

2018-12-02 16:26:57,198 INFO spawned: 'snips-nlu' with pid 103
1543764417: New connection from 127.0.0.1 on port 1883.
1543764417: New client connected from 127.0.0.1 as 6161961aa962493fac614f35e9c9e791 (c0, k10).
INFO:snips_nlu_hermes: loading model at path "/usr/share/snips/assistant/nlu_engine"
ERROR:snips_nlu       : Unable to read file '/usr/share/snips/assistant/nlu_engine/nlu_engine.json'
 -> caused by: Expected model version 0.16.0 but found 0.17.0

ERROR:rumqtt::client  : 6161961aa962493fac614f35e9c9e791 Disconnected: (Error(SyncMpsc(Disconnected), State { next_error: None, backtrace: None }))
1543764417: Socket error on client 6161961aa962493fac614f35e9c9e791, disconnecting.
2018-12-02 16:26:57,238 INFO exited: snips-nlu (exit status 1; not expected)
2018-12-02 16:26:58,240 INFO gave up: snips-nlu entered FATAL state, too many start retries too quickly

Additional information:

snips waiting-for-reply

Most helpful comment

I still have the same issue with snips addon 5.0 on Raspberry 3B+ with hassio 141 beta channel, HA 0.84. Any idea?

1544871729: New client connected from 127.0.0.1 as d6c90f652fb94c90a142b3f6022ea6c1 (c0, k10). INFO:snips_nlu_hermes: loading model at path "/usr/share/snips/assistant/nlu_engine" /usr/bin/snips-asr: symbol lookup error: /usr/bin/snips-asr: undefined symbol: nnet3model_create_dynamic 2018-12-15 12:02:09,974 INFO exited: snips-asr (exit status 127; not expected) ERROR:snips_nlu : Unable to read file '/usr/share/snips/assistant/nlu_engine/nlu_engine.json' -> caused by: Expected model version 0.16.0 but found 0.17.0 2018-12-15 12:02:10,004 INFO gave up: snips-asr entered FATAL state, too many start retries too quickly 1544871730: Socket error on client d6c90f652fb94c90a142b3f6022ea6c1, disconnecting. 2018-12-15 12:02:10,008 INFO exited: snips-nlu (exit status 1; not expected) 2018-12-15 12:02:11,012 INFO gave up: snips-nlu entered FATAL state, too many start retries too quickly

All 12 comments

I have the same problem with this error.

ERROR:snips_nlu       : Unable to read file '/usr/share/snips/assistant/nlu_engine/nlu_engine.json'
 -> caused by: Expected model version 0.16.0 but found 0.17.0

snips does not recognize what I say.

I still have the same issue with snips addon 5.0 on Raspberry 3B+ with hassio 141 beta channel, HA 0.84. Any idea?

1544871729: New client connected from 127.0.0.1 as d6c90f652fb94c90a142b3f6022ea6c1 (c0, k10). INFO:snips_nlu_hermes: loading model at path "/usr/share/snips/assistant/nlu_engine" /usr/bin/snips-asr: symbol lookup error: /usr/bin/snips-asr: undefined symbol: nnet3model_create_dynamic 2018-12-15 12:02:09,974 INFO exited: snips-asr (exit status 127; not expected) ERROR:snips_nlu : Unable to read file '/usr/share/snips/assistant/nlu_engine/nlu_engine.json' -> caused by: Expected model version 0.16.0 but found 0.17.0 2018-12-15 12:02:10,004 INFO gave up: snips-asr entered FATAL state, too many start retries too quickly 1544871730: Socket error on client d6c90f652fb94c90a142b3f6022ea6c1, disconnecting. 2018-12-15 12:02:10,008 INFO exited: snips-nlu (exit status 1; not expected) 2018-12-15 12:02:11,012 INFO gave up: snips-nlu entered FATAL state, too many start retries too quickly

same here, updated to snips 5.0 an hass.io 0.84.3
```1545151866: New connection from 127.0.0.1 on port 1883.
1545151866: New client connected from 127.0.0.1 as cd6ebd54b09f4020b760fd0a52b7198b (c0, k10).
INFO:snips_nlu_hermes: loading model at path "/usr/share/snips/assistant/nlu_engine"
ERROR:snips_nlu : Unable to read file '/usr/share/snips/assistant/nlu_engine/nlu_engine.json'
-> caused by: Expected model version 0.16.0 but found 0.17.0

1545151866: Socket error on client cd6ebd54b09f4020b760fd0a52b7198b, disconnecting.d54b09f4020b760fd0a52b7198b, disconnecting.
```

Same issue here. I got both errors. If I download a new assistant.zip from snips.ai console, i got Expected model version 0.16.0 but found 0.17.0

With my old assistant.zip, I got :

ERROR:snips_tts: Could not start MQTT client on localhost:1883
 -> caused by: Connection refused (os error 111)
2018-12-30 17:38:51,372 INFO exited: snips-tts (exit status 1; not expected)
ERROR:snips_dialogue: Could not start MQTT client on localhost:1883
 -> caused by: Connection refused (os error 111)
2018-12-30 17:38:51,533 INFO exited: snips-dialogue (exit status 1; not expected)
ERROR:snips_hotword: Could not start MQTT client on localhost:1883
 -> caused by: Connection refused (os error 111)
2018-12-30 17:38:51,625 INFO exited: snips-hotword (exit status 1; not expected)
2018-12-30 17:38:51,633 INFO gave up: snips-dialogue entered FATAL state, too many start retries too quickly
2018-12-30 17:38:51,634 INFO gave up: snips-hotword entered FATAL state, too many start retries too quickly
ERROR:snips_audio_server: Could not start MQTT client on localhost:1883
 -> caused by: Connection refused (os error 111)
2018-12-30 17:38:51,640 INFO exited: snips-audio-server (exit status 1; not expected)
2018-12-30 17:38:51,646 INFO gave up: snips-audio-server entered FATAL state, too many start retries too quickly
ERROR:snips_nlu: Could not start MQTT client on localhost:1883
 -> caused by: Connection refused (os error 111)
2018-12-30 17:38:51,671 INFO exited: snips-nlu (exit status 1; not expected)
ERROR:snips_asr: Could not start MQTT client on localhost:1883
 -> caused by: Connection refused (os error 111)
2018-12-30 17:38:51,694 INFO gave up: snips-nlu entered FATAL state, too many start retries too quickly
2018-12-30 17:38:51,707 INFO exited: snips-asr (exit status 1; not expected)
2018-12-30 17:38:54,721 INFO spawned: 'snips-tts' with pid 256
2018-12-30 17:38:54,733 INFO spawned: 'snips-asr' with pid 257
ERROR:snips_tts: Could not start MQTT client on localhost:1883
 -> caused by: Connection refused (os error 111)
2018-12-30 17:38:54,910 INFO exited: snips-tts (exit status 1; not expected)
ERROR:snips_asr: Could not start MQTT client on localhost:1883
 -> caused by: Connection refused (os error 111)
2018-12-30 17:38:54,987 INFO gave up: snips-tts entered FATAL state, too many start retries too quickly
2018-12-30 17:38:54,994 INFO exited: snips-asr (exit status 1; not expected)
2018-12-30 17:38:55,002 INFO gave up: snips-asr entered FATAL state, too many start retries too quickly

While mosquitto's log say that snips is connected

1546187728: Warning: Mosquitto should not be run as root/administrator.
1546187728: New connection from 172.30.32.1 on port 1883.
1546187729: Socket error on client <unknown>, disconnecting.
1546187729: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1546187729: New client connected from 172.30.32.1 as 8eeb973a-f150-4356-9003-d1fef857f738 (c1, k60, u'homeassistant').
1546187751: New connection from 172.30.33.2 on port 1883.
[INFO] found addons on local database
1546187751: Client core-snips.main-mqtt disconnected.
1546187751: New client connected from 172.30.33.2 as core-snips.main-mqtt (c0, k60, u'addons').
1546187882: New connection from 172.30.32.1 on port 1883.
1546187882: New client connected from 172.30.32.1 as mosqsub|508-core-ssh (c1, k60).
1546187907: Socket error on client core-snips.main-mqtt, disconnecting.
1546187943: New connection from 172.30.33.2 on port 1883.
[INFO] found addons on local database
1546187944: Client core-snips.main-mqtt disconnected.
1546187944: New client connected from 172.30.33.2 as core-snips.main-mqtt (c0, k60, u'addons').

The components has often this issue after update hass but thanks anyway, when it's working, it's really great.

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

I still have the same issue, just on a newer version. Hassio 0.89.2 with snips add-on 5.1.
After the breaking change on the snips-side, I couldn't update the assistant, but the old one worked. Since hassio version 0.89, neither the old nor the new assistant works.
The error I get:

ERROR:snips_nlu_hermes: nlu thread ended with error: Unable to read file '/usr/share/snips/assistant/nlu_engine/nlu_engine.json'
 -> caused by: Expected model version 0.17.0 but found 0.19.0
ERROR:snips_nlu       : Fail to wait end of pipeline
 -> caused by: Unable to read file '/usr/share/snips/assistant/nlu_engine/nlu_engine.json'
 -> caused by: Expected model version 0.17.0 but found 0.19.0

This should be opened in the hassio-addons repository, but in any case this should be working as of 13 days ago with version 5.2.

Looks like the problem returned although I cannot know for sure as I just started fiddling with home assistant (Snips add-on 5.2):

INFO:snips_hotword_lib::universal: Loading model "/usr/share/snips/assistant/custom_hotword", hotword_key: Some("hey_snips"), model_id: Some("hey_snips_3.1_2018-04-13T15:27:35_model_0019")
ERROR:snips_nlu_hermes: nlu thread ended with error: Unable to read file '/usr/share/snips/assistant/nlu_engine/nlu_engine.json'
-> caused by: Expected model version 0.19.0 but found 0.17.0

ERROR:snips_nlu : Fail to wait end of pipeline
-> caused by: Unable to read file '/usr/share/snips/assistant/nlu_engine/nlu_engine.json'
-> caused by: Expected model version 0.19.0 but found 0.17.0

1555738610: Socket error on client snips-nlu|56-core-snips-1, disconnecting.

Hi,
I think you need to update the snips console file assistant.zip. connect to web site snips and download again your assistant.zip file. Put in your home assistant a.d it should work again

Still getting the same error on the current version (4-July, '19). I don't know where to download the assistant.zip file from. So far all I've done is install the Hass.io add-on through the Hass Community Add-on store. Any assistance available?

Go go console.snips (search Google) to get jour assistant

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sogeniusio picture sogeniusio  路  3Comments

Konstigt picture Konstigt  路  3Comments

sibbl picture sibbl  路  3Comments

piitaya picture piitaya  路  3Comments

arangates picture arangates  路  3Comments