Pimatic plugin no longer works with new evok release
error [pimatic-unipi-evok]: [UniPiUpdateManager] Web Socket Closed
error [pimatic-unipi-evok]: [UniPiUpdateManager] Web Socket Error: Error: getaddrinfo ENOTFOUND 82ws 82ws:80
-
pimatic & unipi plugin
-
@bill-blacksoll Which version of evok do you have installed? What is the URL you have configured to let the plugin contact the evok server? Make sure the address contained in the URL can be resolvable. If you’re using a hostname try to use the IP address of the evok server instead.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Resolved this but now i get another…
error [pimatic-unipi-evok]: [UniPiUpdateManager] Error: unable to get device status, exception caught: SyntaxError: Unexpected token oI use evok 2.0, not the legacy version and yes the URL is resolvable
-
@bill-blacksoll said in pimatic & unipi plugin:
I use evok 2.0, not the legacy version and yes the URL is resolvable
Ok, evok 2.0 isn’t supported yet as I am lagging behind with the testing. Regarding the syntax error that a know issue with evok 2.0 which has already been fixed. If you’re impatient you can try to install plugin from the github master using “Method 1” as described here: https://forum.pimatic.org/topic/1114/updated-how-to-install-a-plugin-from-github-using-npm-or-git
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Ok ! So i’m waiting for the new version of plugin with evok 2.0 support.
Do you see it any time soon ? Will i see it in the updates-page of my installation ?
Will you support neuron also ?
Thanks ! -
@bill-blacksoll said in pimatic & unipi plugin:
Ok ! So i’m waiting for the new version of plugin with evok 2.0 support.
Do you see it any time soon ? Will i see it in the updates-page of my installation ?Should be available within the next two weeks and yes, it will be highlighted on the updates-page of your setup.
Will you support neuron also ?
Yes it should, but I have no neuron board to test with.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Thanks for the quick support
@mwittig said in pimatic & unipi plugin:
Yes it should, but I have no neuron board to test with.
Maybe Tomas can help with this !
-
@bill-blacksoll said in pimatic & unipi plugin:
Thanks for the quick support
You are welcome.
Maybe Tomas can help with this !
Good point. I’ll ask him about this. My understanding is that Evok hides all the board specifics. As the pimatic plugin uses the Evok REST (and WebSocket) API which is also used by the Evok web application I think it should work without problems with Neuron. However, there might be subtle differences, such as device types the pimatic plugin should handle.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Wow ! i’m impressed
you are fast…
Keep up the great job ! -
@bill-blacksoll Thanks, will do!
If you have a Neuron board to test with please let me know about your findings.
I have noticed there are some further tweaks required to support fully Neuron as it seems to use additional device types.
Do you know what what a “neuron” state in Evok terms typically represents?
https://evok-2.api-docs.io/1.02/models/neuron-state
https://evok-2.api-docs.io/1.02/json/get-neuron-state-json
https://evok-2.api-docs.io/1.02/json/change-neuron-state-json"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
