Ok, this is odd. I didnt have basicUI installed so I installed it to take some screenshots and suddenly Favorites started working. Maybe installing basicUI restarted/reinitialized something?
If you could enable debug logging if the problem appears again I would be interested in the debug logging of org.openhab.binding.heos when restarting openHAB
Oh btw, my setup is a Heos bar, a Heos subwoofer and two Heos 3 “surround” speakers. No groups because they are all connected to the bar. In openHAB I have one bridge (heos bar) and one thing (heos bar).
Because reinstalling any binding temporarily fixes the problem I thought it had something to do with the core, but I have other bindings like Home Connect installed and the program selection for my dishwasher works fine every time.
The only other thing I could think of is that I cannot link the heos bar channel in the bridge, there is no profile available:
I’m able to link it through habmin and then switch it ON but that doesn’t make a difference.
Heos binding:
299 x Active x 80 x 2.5.2.202002031257 x openHAB Add-ons :: Bundles :: HEOS Binding
Openhab:
[11:38:19] root@openhab:/home/openhabian# dpkg --list | grep openhab
ii openhab2 2.5.1-2 all openhab2
Maybe @MDAR has the same issue when restarting the binding?
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
289
Sorry to disappoint you, everything is working well for me.
Now that I’ve put the correct version of the binding in (and insured that there aren’t any artifacts of the previous version present in Karaf)
hi Everybody
i use the newest buld from the plugin and i have openhab 2.5.3
everything works with denon with play music and volume control.
the only thing i cannot do in a rule is to group special speakers in a rules, i tried evertyhing but whenn the group is not build in heos correctly it wont work.
can somebody help me how to specify a rule, to make a specific group (say speaker 2 and 3 together) (and if speaker 1 2 and 4 is in a group, it’s ungrouped and build the new group 2 and 3
First build the group manually in the HEOS network. Then the group will show up in your Inbox. Add that group (do that for each group you want to use). Use the Group/Ungroup switch channel on every group to group/ungroup that group.
You can group them easily with this switch from a rule also. Just send ON to group them or OFF to ungroup…
@martinvw’s changes are working great for me so far. Thanks! Favorites set up this way seems to work very well.
Forgive me if this has already been discussed (I didn’t find anything searching the thread and I am new to HEOS), but would there be any way to add the ability to get the images (or image URLs) representing the favorites as well? I noticed in the telnet data that it is available from HEOS, and it would be great to use that to create favorite buttons with images on HabPanel.
I’m not sure how this would best be handled, but even if it was raw json data provided by the binding in a channel (like z-wave locks) with the favorite info and image urls that would be really useful!
Hello, I’m trying to play my sound through Openhab 2.5 on my Denon AVR-X2400H receiver. When I install the HEOS binding from the Paper UI, I get the receiver displayed under the sink, but when I write a rule example (playSound (“doorbell.mp3”)), I don’t hear anything from the receiver. I searched a lot and only found the hint that you still have to enter the IP of OpenHAB under “CallbackURL”. However, this entry does not exist anywhere, at least I do not find it. Can somebody help me ?
Got the sink up and running.
It is also displayed in the OpenHab console. With play doorbell.mp3 the sound also arrives.
Unfortunately with this simple rule.
rule “Play Sounds”
when
Item PlaySounds received command ON
then
// Play the sound on the default sink
playSound("doorbell.mp3")
// Play the sound on a specific sink at a specified volume level
playSound("heos:player:-324015404", "doorbell.mp3")
The newest HEOS bindings from the official release do not contain any new features, so feature wise the download is the newest one. However it’s not yet reviewed and merged.
When I wanted to set this up but with the say method I faced some troubles with the volume and such. I have the ambition to also look into this part of the binding because we might need to do more with the feedback when it starts and stops playing.
Fair question, to be completely clear what you are asking, you are not interested in the current playing item but you are interested in the meta-data of the favorites. If someone has a good solution that fits with the architecture of openHAB where I can put then it’s not hard but I fear the modeling is the hardest in this one. For the reference, you would need the field imageUrl in the class BrowseResult in the new code (which has a pending PR).
I included a summary of my changes in the initial message of the pull request. However the most critical change which I made last week is the handling of the reads and the timeouts of such reads. The normal scenarios work very good but I did not yet test actual broken connections by unplugging devices and such.
Another change which was included in the PR is the connection and reconnection on errors timeouts. If you see any strange behavior on that it would be good to know.
Thanks for you work on this @martinvw. I’ve been trying out the new version. Here are my observations so far. Note that some of this behavior might be preexisting.
The main issue I’m currently having is that it never creates all of the channels on the bridge for the speakers. It will create some of them, but never all of them for some reason.
I disconnected a speaker for several minutes. It seemed to reconnect just fine after it started back up. OH was able to communicate with it again.
Speakers show as being online no matter how long they have been powered off. I was expecting them to eventually show as offline.
OpenHAB can send commands to powered off speakers and there is no indication that it failed.
For what it’s worth in the past the main thing I’ve been fighting (before this version too) is the speaker channels in the bridge. Even in your previous version, the binding only creates the channels when it is initialized. If for some reason a speaker isn’t listed in the HEOS app at that time, but later is connected again and discoverable, it will never get a channel in the bridge unless I restart the binding. It would be great if this speaker discovery/channel creation part could happen when speakers are discovered/connected.
If there are other scenarios I can test or if there’s anything you want me to look for in log files let me know.