-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node-raumserver can not change volume but old windows raumserver is working #39
Comments
Not sure about that. I do not suffer this issue. On which device does the raumserver run? BTW: You have a buffer underun?! |
hello, the raumserver runs on a x64 linux (ubuntu 16.04.3) (direct on this vm host) the only ways to solve this is by restarting the rf device. TransportStatus : "buffer underrun in Kueche" but the device was playing fine the radio stream and i was able to pause/vol+- through the old but not the noderfapi. thanks PS: i tried just to restart the node raumserver.js and this did solve the issue as well - so it must be something wihtin the new raumserver - restarting it did fix the issue |
When does it stop working? Any idea? Maybe if the device comes up from the sleep mode? Does restarting of node raumserver fix this issue or only the restart of the RF device? |
hello, this is within the log
|
Hmm. Holly does not mention that he is rebooting the host. |
I'm not sure if @holli73 has this problem when he restarts the Raumfeld device:
|
I have the same Problem, restart the node-raumserver (del_test.js) and it works but the Reason i dont know. |
hello, i did not re-start the rf-expand on purpose - but i can not tell if it might rebooted on its own - or one of the latest update + reboot caused the node-rf server to fail - but i still do not understand why the old windows api works and if the port changed the node-rf not trying to get the new port? thanks |
May be fixed with latest release. |
hello,
for my new app i'm using the the new node way - but i do have an issue with some task - they do not work as expected - once i restart the rf device the node app is working again - but why is not working when the old raumserver on windows doesn't suffer from this error?
f.ex. - just setting the volume up returns:
{"requestUrl":"/raumserver/controller/setVolume?id=Kueche&value=17","action":"setVolume","error":true,"msg":"Action was rejected","data":{"errorMessage":"Error: connect ECONNREFUSED 192.168.251.200:56421","errorData":null}}
the get renderstate for this room shows:
any idea?
thanks
holli
The text was updated successfully, but these errors were encountered: