It’s not that bad , only the last step (step 5) has to be repeated.
The alternative is to find out how to automatically start it when Mac OS starts (e.g. by setting up a service). I know how to do it for Windows and Linux but I’m not familiar with Mac OS. Anyone around who can assist here?
Yes, extensions run under the control of the manager. This gives the possibility to perform all actions from the Roon UI, including starting and stopping an extension.
Hi @Jan_Koudijs, would it be possible for the Alarm Clock extension to define what will be played when the alarm goes off?
I’m using the Alarm Clock extension as a clock radio that plays an internet radio station to wake me up.
But I have to remember to set Roon to the internet radio station at night.
If I play an album and fall asleep then the the Alarm Clock extension wakes me with random music rather than with my favourite radio station.
Not a first world problem though …
Source selection is still something I would like to add but the difficulty is that the user interface possibilities are rather limited. I experimented with Internet Radio selection and it worked quite well with the few stations that I have but how will it work when you have a lot of them? It might not be very user-friendly to scroll through a long list in a small drop-down box. So I’m still a bit in search, but surely open for suggestions.
I might add the possibility to play random tracks or random albums. As you might have seen, I know how to do that
I had an error when running roon-extension-manager :
MOO: reached end of buffer while parsing header
<- undefined undefined undefined
C:\Users\User\.RoonExtensions\node_modules\roon-extension-manager\node_modules\node-roon-api\moo.js:187
let cb = this.requests[msg.request_id].cb;
^
TypeError: Cannot read property 'cb' of undefined
at Moo.handle_response (C:\Users\User\.RoonExtensions\node_modules\roon-extension-manager\node_modules\node-roon-api\moo.js:187:44)
at Transport.transport.onmessage.msg [as onmessage] (C:\Users\User\.RoonExtensions\node_modules\roon-extension-manager\node_modules\node-roon-api\lib.js:411:27)
at WebSocket.Transport.ws.onmessage (C:\Users\User\.RoonExtensions\node_modules\roon-extension-manager\node_modules\node-roon-api\transport-websocket.js:30:14)
at WebSocket.onMessage (C:\Users\User\.RoonExtensions\node_modules\roon-extension-manager\node_modules\ws\lib\WebSocket.js:442:14)
at emitTwo (events.js:126:13)
at WebSocket.emit (events.js:214:7)
at Receiver.onbinary (C:\Users\User\.RoonExtensions\node_modules\roon-extension-manager\node_modules\ws\lib\WebSocket.js:848:10)
at C:\Users\User\.RoonExtensions\node_modules\roon-extension-manager\node_modules\ws\lib\Receiver.js:628:18
at Receiver.applyExtensions (C:\Users\User\.RoonExtensions\node_modules\roon-extension-manager\node_modules\ws\lib\Receiver.js:371:5)
at C:\Users\User\.RoonExtensions\node_modules\roon-extension-manager\node_modules\ws\lib\Receiver.js:604:14
User@CRES MINGW64 ~/.RoonExtensions/node_modules/roon-extension-manager
The error occurs in the Roon API part of the code, therefor I cannot directly relate it to my own code. Was it anything specific you were doing, and did it happen once or can you reproduce it? It would be very helpful if you can provide me with some steps that lead to the problem.
@ben, It hits a specific log line in moo.js: MOO: reached end of buffer while parsing header, provides this a hint to you?
Thank you for your message. I did not succeed in reproducing the problem. All I can add is that after installing the manager extension, I tried to play with the radio extension. I had another mistake later, that the extension had lost the core. Do not worry about that, if I have anything else I’ll tell you. Thanks again, dp.
One new feature is implemented: The manager and the repository can now be updated manually, previously they could only be updated via the auto update function.
if auto update is enabled then the changes will be pulled in the next time an update is performed.
After the auto update the Extension Manager and Repository can be selected from the extension list for manual update:
I installed the extension manager last night and loaded the Alarm Clock module…
I set up two alarms… one to stop the zone at 23:15 (Mon-Fri) and the second to start the zone at 06:00 am…
It worked fine last night and the music stopped on the right time…but in the morning , nothing happenned… I checked Roon and noticed that the extension was not loaded…
I run Node again this afternoon and the extension is back on… will test the behavioir again tonight and tomorrow…
But wanted to know if this first faillure is normal… and have I done anything wrong ?
Again, this morning… the extension manager has disappeared from Roon…
It look like for some reasons the extension manager has stopped working…
Any suggestion to solve the problem will be greatly appreciated…