Version 5.x is the minimum node version for the Roon API and for that reason the lower limit for all extensions. I can add a note that the minimum version for individual extensions can deviate from this. The version installed by the Windows installer is 6.x and this would be a sensible choice for future packages as well.
It would be good to make the minimum node version for an extension explicit, especially when it is higher than that of the Roon API as in your case. There is a facility for this in the package.json file by means of the engines keyword. If you can add this to your package.json file then I will check if I can detect a version mismatch and report this to the user.
I found the issue it was having some problems with the Harmony extension. I checked the journalctl and it had loads of errors for that extension. So I did a full uninstall of all the extension packages and reinstalled the manager and updater. This now runs as a service. I have reinstalled the harmony extension and all seems ok. Will keep an eye on it and report back any more issues.
One thing you instructions missed is making sure the roon-extension-manager.sh and service has the correct permissions to run. So I needed to chmod +x the .sh and copied permissions from other services to the service file.
I noticed that after the automatic update of today my systemd service was down as well, it was also having an issue with the Harmony extension. If the problem returns tomorrow I have to check if a change in one of its dependencies is causing a problem.
Thanks for bringing this up. I will update the instructions.
Tried a manual update and not luck so then removed the extension with npm uninstall and it still wont run I guess the extension manager still thinks it installed in its settings somewhere as I cant run it I could not use its uninstaller.
Was there any indication that the uninstall was successful? Please check if the directory of the extension was completely removed, /root/.RoonExtensions/lib/node_modules/roon-extension-harmony shouldnāt exist anymore. If it is still there you can delete it manually.
Next you start the service again. If it still doesnāt work it may be best to stop the service and delete the complete /root/.RoonExtensions directory. After this you have to manually install the extension manager and updater again.
I donāt know what is causing this problem. The Harmony extension somehow gets corrupted during the auto update process. It can be the termination of the extension or the update itself.
Is your Harmony Hub permanently online and connected with the extension?
I wonder if it makes a difference if there is a connection or not.
Yes it uninstalled fully. I had to remove all the extensions and delete the directory last time so this is only a temp fix and it will break again so I am going to leave it and run the Harmony extension as a service on its own for now. until you find a solution. My harmony hub is on 24/7 and is always connected when the extension is running.
What Iām working on at the moment is to better keep track of the running extensions, if e.g. an extension is killed outside the control of the Extension Manager it will be detected and the state administration will be updated.
Also in the termination of running extensions improvements are in progress, when a terminate signal is sent to an extension a feedback from it is expected before work continues. Especially this last part should help in getting a more robust system. I hope that it also helps in solving the update issue you are encountering. It should at least give more information about what is going on, this can then be helpful in tracking the issue down.
It shouldnāt take too long till the above is ready for releaseā¦
After several failed attempts I ended up removing the roon extensions folder from AppData location and managed to get the service to disappearā¦ and tried a reinstall again but the service cant start - sits there as Automatic and doesnt appear in the extensions list
Any ideas? I tried Run as admin. no firewalls are on and server and client on the same PC (win10pro 1709 as far as I can tell.
The installer ran clean each time I thinkā¦ ill look at the full clean up and see how that goes.
Updateā¦ that did the trickā¦ I think it must have been the npm cache tripping things up.
Donāt think I ever updated from the original beta testing we did anyway for those having issues do the full cleanup and that should get things back on track
anyway for those having issues do the full cleanup and that should get things back on track