I have entered the address http://192.168.20.100/index.php?v=d&m=jeerhasspy&p=jeerhasspy in the browser to access the console and I also tested instead of the IP address in the config, I have errors like “Invalid access token” in the configuration tab there is a window that is displayed is my jeedom login page.
and it crashed, I will have to restart.
Ok otherwise it will be all for tonight, we are looking at the rest tomorrow, so I am also starting to be quite busy because the end of year celebrations are approaching, so I have to make preparations.
The message “The requested URL was not found on this server” comes from the version info that seems to get a wrong url, I will add a check on this. Seems jeedom never reached your rhasspy at all and entered a stored a wrong version information.
So:
You just need the url to go to your rhasspy.
When you are on this page, note the url and the port
That’s all you need on jeedom side.
Then import your assistant
Back into rhasspy interface, settings, enter the plugin url into (Assistant panel, internal url): Use a remote HTTP server to handle intents
EDIT : I can reproduce what you have / see (<html lang= in version field etc), this is because you enter your Jeedom url into configuration adresse for rhasspy. Will set definitely set a check here !
So all you need is your rhasspy url
I just published a new Beta of the plugin, that now check when importing the assistant if the version returned is really a version number, in case the user didn’t entered the right rhasspy url into plugin configuration.
@Mytika you should update the plugin, then import the assistant. If you finnally got your rhasspy url right, it will be right, else it will reset to rhasspy version to 0.0.0 in the plugin so it won’t give errors.
Got it working the last plugin update.
Now i’m waiting for the rhasspy DEV to add the intents API and also to fix the dividedByZero issue.
I see you are evolved to test the new rhasspy-nlu version…is it working for you ?
Not real, I’m going to get the plugin in the market and for me it was clear that the rest had to be done alone, it’s my dream.
In short, it was I who did not follow the movement
I’ve added a way to load intents even in actual docker version which does not have /api/intents.
No problem for next version as it first check for api/intents, and of not there, use another solution.
Updated the doc to say that… well… you need rhasspy to use rhasspy