I just started testing how I can use your raumkernel for implementing nodes for node-red to control several aspects of my raumfeld system with node-red in connection with MQTT and homebridge and Apple Home.
It works so far but when I monitor some of the core events, on top the systemReady event, I always get all the stuff I expect when I first connect to a system like systemReady and host found and renderers found when I change the config of my system with the normal iOS app.
Is that an intended behaviour?
Because this seems not really right to me. When I monitor the systemReady state and I remove a speaker from a zone then the system is not ready and then ready again and all the renderers are rediscovered. This makes it hard to bind action to those events because they are triggered too often.
I thought this was because of my noob implementation of my first node, just started using js and node and that stuff. But then I tried just the test.js you provide and this does all the same I see with my implementation: events firing when I just remove a speaker to a zone or remove it it seems the whole kernel sets back as if it just connected again to the host...
I just started testing how I can use your raumkernel for implementing nodes for node-red to control several aspects of my raumfeld system with node-red in connection with MQTT and homebridge and Apple Home.
It works so far but when I monitor some of the core events, on top the systemReady event, I always get all the stuff I expect when I first connect to a system like systemReady and host found and renderers found when I change the config of my system with the normal iOS app.
Is that an intended behaviour?
Because this seems not really right to me. When I monitor the systemReady state and I remove a speaker from a zone then the system is not ready and then ready again and all the renderers are rediscovered. This makes it hard to bind action to those events because they are triggered too often.
I thought this was because of my noob implementation of my first node, just started using js and node and that stuff. But then I tried just the test.js you provide and this does all the same I see with my implementation: events firing when I just remove a speaker to a zone or remove it it seems the whole kernel sets back as if it just connected again to the host...