Yamahareceiver Binding problems

yamahareceiver
Tags: #<Tag:0x00007f15d5c616e0>

(Tomasz Maruszak) #60

Afaik the addon can only be upgraded as long as it matches the OH version (2.3.0 addon - 2.3.0 OH). I hope someone will double check that statement.

There are good reasons to move to the latest version. I am also in the middle of other changes and improvements that will ultimately be available as 2.4.0-SNAPSHOT (since the stable 2.3.0 has already been released few weeks ago).


(Pavel) #61

Same behaviour after update to 2.3.0:

2018-06-10 00:40:21.330 [ome.event.ItemCommandEvent] - Item ‘Yamaha_Input’ received command HDMI_1
2018-06-10 00:40:21.334 [vent.ItemStateChangedEvent] - Yamaha_Input changed from AUDIO1 to HDMI_1
2018-06-10 00:40:21.457 [vent.ItemStateChangedEvent] - Yamaha_Input changed from HDMI_1 to AUDIO1
2018-06-10 00:40:25.708 [ome.event.ItemCommandEvent] - Item ‘Yamaha_Input’ received command HDMI_2
2018-06-10 00:40:25.714 [vent.ItemStateChangedEvent] - Yamaha_Input changed from AUDIO1 to HDMI_2
2018-06-10 00:40:25.840 [vent.ItemStateChangedEvent] - Yamaha_Input changed from HDMI_2 to AUDIO1

Another problem is AirPlay. To set it, it should be “AirPlay”, but looks like from AVR come value “AIRPLAY”:

2018-06-10 00:40:21.330 [ome.event.ItemCommandEvent] - Item ‘Yamaha_Input’ received command HDMI_1
2018-06-10 00:40:21.334 [vent.ItemStateChangedEvent] - Yamaha_Input changed from AUDIO1 to HDMI_1
2018-06-10 00:40:21.457 [vent.ItemStateChangedEvent] - Yamaha_Input changed from HDMI_1 to AUDIO1
2018-06-10 00:40:25.708 [ome.event.ItemCommandEvent] - Item ‘Yamaha_Input’ received command HDMI_2
2018-06-10 00:40:25.714 [vent.ItemStateChangedEvent] - Yamaha_Input changed from AUDIO1 to HDMI_2
2018-06-10 00:40:25.840 [vent.ItemStateChangedEvent] - Yamaha_Input changed from HDMI_2 to AUDIO1

P.s. Can I see somewhere else version of binding itself? May be old version left.


(Tomasz Maruszak) #62

This is odd. I have a feeling you still have the old binding. Try doing these checks:

  1. Make sure you don’t have a custom addon JAR under /addons folder.
  2. In Paper UI check if the receiver thing has the input mapping (only the new one has).
  3. Enable trace logging to see what is going on. Then check if you get log statements from InputConverterXML in openhab.log when you change input source.
  4. Not sure how did you upgrade, but would be good to have a clean install (or at least remove folders tmp, kar, cache from /userdata).

(Pavel) #63

I tried “AV1”, “AV2” from Paper UI and it’s help.


(Pavel) #64

I expecting weird problem with manual binding installation. What I did:

  1. Uninstall yamaha binding at paper ui.
  2. Put downloaded jar into /usr/share/openhab2/addons/

But nothing happened. What I should expect? May be needed some additional configuration in files or via UI?


(Tomasz Maruszak) #65

Another user had a similar problem where OH was not picking up the custom binding. I advise to see how he managed to solve this issue.


(Pavel) #66

It fixed somehow after a couple of tries. Don’t know what it was.


(Tomasz Maruszak) #67

Pull request here:


(Kris K) #68

Hello @zarusz I have an issue with the Yamaha binding. When the AVR goes offline for more than a few hours, I need to go into PaperUI and update the thing before it comes back online.

Known issue? Im using this version:

│ Active │ 80 │ 2.3.0.201806201708 │ YamahaReceiver Binding


(Tomasz Maruszak) #69

Hi, I never heard nor observed such an issue.

What OH version are you using (stable/snapshot)?
Are you using my custom build JAR for 2.3.0 (my dropbox link) or is it the official 2.3.0?
Sending me the logs just after it goes offline might help (the openhab.log) to diagnose the issue.