[Announcement][Release] Version: 2019-01-24 12:13:13 (Multi Dialogue)

#21

For others, complete reinstall solved my problem.

#22

Hi @rollyfx,

Please could you elaborate what you did reinstall? Jeedom snips plugin? Snips platform?

fx

#23

From memory, moved snips.tml, deleting and installing snips platform with apt , and restoring backup of Jeedom snips plugin.

#24

I got this error with the last stable plugin:

PHP Fatal error:  Call to undefined function SnipsHandler::hotword_detected() in /var/www/html/plugins/snips/core/class/snips.hermes.class.php on line 285
#25

Under any conditions? Or it comes with no reason

#26

I have the variable msgonhotword checked. It should start a scenario, but it isn’t started. As soon as I say the wakeword, it crash.

#27

that’s not related to the msghotword variable, even unchecked I got the same message each time and daemon crash.

Will revert to november version that works …

#28

even reverting to previous version, doesn’t work !

[2019-03-29 14:47:10][ERROR] : Erreur sur la fonction deamon_start du plugin : Can not find taks corn

taks corn ?? task cron ??

So entire snips broken nothing works anymore.

#29

Can you share some log?

#30

I don’t have more log ! I put all there

#31

The new version and old version are using different task cron. I would suggest you change to new version, and grebe some log of this crash. So that I can push the batch as fast as I can. Now I can’t allocate the issue…

#32

resintalled last version
loaded assistant

as soon as I say the hotword (even before parsing intent) I got this:
PHP Fatal error: Call to undefined function SnipsHandler::hotword_detected() in /var/www/html/plugins/snips/core/class/snips.hermes.class.php on line 285

and daemon crash

no other log.

#33

in debug got this
[2019-03-29 14:58:46][INFO] : [SnipsHermes] <__construct> trying to connect: 192.168.0.130:1883
[2019-03-29 14:58:46][DEBUG] : [SnipsHermes] <mqtt_on_connect> Connected to the broker with code: 0 message: Connection Accepted.
[2019-03-29 14:58:46][DEBUG] : [SnipsHermes] <mqtt_on_subscribe> Subscribeed with code 1
[2019-03-29 14:58:46][DEBUG] : [SnipsHermes] <mqtt_on_subscribe> Subscribeed with code 2
[2019-03-29 14:58:46][DEBUG] : [SnipsHermes] <mqtt_on_subscribe> Subscribeed with code 3
[2019-03-29 14:58:46][DEBUG] : [SnipsHermes] <mqtt_on_subscribe> Subscribeed with code 4

and still in cron_execution log:
PHP Fatal error: Call to undefined function SnipsHandler::hotword_detected() in /var/www/html/plugins/snips/core/class/snips.hermes.class.php on line 285

#34

Which Jeedom version you are on?

I dont have this issue, same fresh install.

[2019-03-27 17:38:15][INFO] : [SnipsHermes] <__construct> trying to connect: snips-seeed-master.local:1883
[2019-03-27 17:38:15][DEBUG] : [SnipsHermes] <mqtt_on_connect> Connected to the broker with code: 0 message: Connection Accepted.
[2019-03-27 17:38:15][DEBUG] : [SnipsHermes] <mqtt_on_subscribe> Subscribeed with code 1
[2019-03-27 17:38:15][DEBUG] : [SnipsHermes] <mqtt_on_subscribe> Subscribeed with code 2
[2019-03-27 17:38:15][DEBUG] : [SnipsHermes] <mqtt_on_subscribe> Subscribeed with code 3
[2019-03-27 17:38:15][DEBUG] : [SnipsHermes] <mqtt_on_subscribe> Subscribeed with code 4
[2019-03-27 17:38:15][DEBUG] : [SnipsHandler] <hotword_detected>

Thesnips-hotword will response a detected signal when subscribe to it.

#35

Last jeedom stable
Last plugin stable
Platform previous update (the last one broken all and took days to be fixed so I didn’t updated)

#36

Can you try to add:

require_once dirname(__FILE__) . '/snips.handler.class.php';

to the first line of the /var/www/html/plugins/snips/core/class/snips.hermes.class.php file? and retry

#37

same thing

PHP Fatal error: Call to undefined function SnipsHandler::hotword_detected() in /var/www/html/plugins/snips/core/class/snips.hermes.class.php on line 286

#38

I’v just created an issue, let’s keep the debug process here -> https://github.com/snipsco/snips-jeedom-plugin/issues/15

#39

ok.

just noticed all my callback scenarios are now … empty !

updates are real problem lately both platform and plugins …

#40

I have updated platform, assistant, downloaded assistant, upload into jeedom plugin and redon the callbacks

So I’m all up to date stable version

Still broken anyway.