The Binding is not working, i can not power on my radio. The undok-APP (Android Playstore) is working perfect.
When i enter the command which was mentioned in the binding-wiki, i get the excepted result “fs_ok xxxxx” - so i think there could be a little hope to get this binding running with my radio.
Can anybody help my? Maybe the developer of this binding is reading here too?
I copied the items and sitemap from the binding-wiki to my openhab and changedit to my things, i get messages in openhab-log, if i power on the radio, but radio is still off.
Where can i see, if the binding is working correctly and connecting with my radio?
I did some further tests, also i did a restart of the openhab service. Now the binding is working.
The pin was ok.
But one issue still exists. My Volume Control is from 0 to 20, in the binding it is codes from 0 to 30. Volume Control is not working with my radio.
I get shown the % but i can´t raise/lower the volume.
I added another volume control item in the FS internet radio binding (one for percentage, one for absolute number) which will be part of eclipse smarthome, but I did not yet find time to port these changes back to the openhab 1.x version of the binding. If you want, you could do that and create a pull request for it.
I extended and revised this binding specifically for Eclipse Smarthome: https://github.com/eclipse/smarthome/pull/429
This means that it can also be used in openhab 2, but not in openhab 1.x. The new features for openhab 2 are device discovery (which is not available in openhab 1.x) and an additional item type for controlling the volume as discussed in the PR.
But as far as I understood your second last post, everything is now working for you.
Yes, it is working, but i can’t use the setpoint item for volume, because oft the % error. My radio is in very low volume, i want to change and for example it jumps to 18% in openhab but radio Volumen jumps to 18 (max is 20) and it is very very loud. So all is usable except the volume.
If I find some time, I will add the additional volume item type also to the openhab 1.x binding, but I’m quite busy at the moment, so don’t expect this to happen very soon
Finally, I had some time to look into this issue and there was in fact a bug when posting a new volume to the event bus. Fix is provided in this PR: https://github.com/openhab/openhab/pull/3882