OpenHAB integration

[espenaf]

Hi

The android app stopped working when I upgraded my phone recently and with my XPA-11 having to go inn for repair, it was perfect time to work on creating an Emotiva integration (aka. binding) for the home automation project called OpenHAB

I have just published the first beta version of the binding.

The binding has only been tested with an XMC-2, so need feedback from people with other devices.

Support for all notification types in version 2.0 and 3.0 of the protocol, and adds support for Menu Controls, Zone 2, Radio Tuner and all most other remote functionality.

The binding can be installed from the Community Marketplace directly in OpenHAB.

Espen

[espenaf]

Just pushed a new version to the Marketplace that has the following changes:

* Adds Radio Tuner functionality
* Adds i18n labels for EN and NO
* Adds missing trim support for Height and Width speakers
* Lots of small fixes

Screenshots of the Controls in the OpenHAB BasicUI

Browser:



OpenHAB Android app:

[espenaf]

Pushed a new update with the following changes:

* Added ability to view and control the menu.
* Added automatic connect, disconnect on missing keepAlive and reconnect if device is available again.
* Lots of small fixes.

By using the different building blocks in OpenHAB I have created UI that mimics the front panel and menu controls and display. This makes it possible to fully control the menu remotly. Below are screenshots of a typical menu selection on my XMC-2, and then the mirrored version in the OpenHAB UI via a browser.

[espenaf]

The latest version adds Zone 2 functionality, so now most things should just work. All changes can be installed via the Marketplace Addon at community.openhab.org/t/emotiva-av-processor-binding/154406

[espenaf]

Just pushed a new version which does a lot of cleanups and makes it ready for review and an eventual inclustion into a future version of OpenHAB.

During development I have found a few strange issues that I wanted to hear if anybody else developing remotes have encountered? It is somewhat mentioned in another thread.

Some input commands sent to the device will produce the wrong result:

* analog1 -> Analog 3
* analog3 -> Analog 1
* coax1 -> Coax 3
* coax3 -> Coax 1
* optical1 -> Station 6
* optical2 -> Optical 1
* optical3 -> Optical 2
* optical4 -> Optical 3
* zone2_analog1 -> Z2: Analog 3
* zone2_analog3 -> Z2: Analog 1
* zone2_coax1 -> Z2: Coax 3
* zone2_coax3 -> Z2: Coax 1
* zone2_optical1 -> Z2: Station 6
* zone2_optical2 -> Z2: Optical 1
* zone2_optical3 -> Z2: Optical 2
* zone2_optical4 -> Z2: Optical 2

Atleast there is some consistententy to the flipping of the sources, but still not what I had expected.

The ARC and and zone2_ARC is also not working for me. These might be false positives, as I suspect there needs to be some actual input on the sources.

[klinemj]

I think in a recent podcast they mentioned a new app for control. Your application sounds interesting, though.

Mark

[espenaf]

Apr 30, 2024 15:41:17 GMT -5 espenaf said:

Just pushed a new version which does a lot of cleanups and makes it ready for review and an eventual inclustion into a future version of OpenHAB.

During development I have found a few strange issues that I wanted to hear if anybody else developing remotes have encountered? It is somewhat mentioned in another thread.

Some input commands sent to the device will produce the wrong result:

* analog1 -> Analog 3
* analog3 -> Analog 1
* coax1 -> Coax 3
* coax3 -> Coax 1
* optical1 -> Station 6
* optical2 -> Optical 1
* optical3 -> Optical 2
* optical4 -> Optical 3
* zone2_analog1 -> Z2: Analog 3
* zone2_analog3 -> Z2: Analog 1
* zone2_coax1 -> Z2: Coax 3
* zone2_coax3 -> Z2: Coax 1
* zone2_optical1 -> Z2: Station 6
* zone2_optical2 -> Z2: Optical 1
* zone2_optical3 -> Z2: Optical 2
* zone2_optical4 -> Z2: Optical 2

Atleast there is some consistententy to the flipping of the sources, but still not what I had expected.

The ARC and and zone2_ARC is also not working for me. These might be false positives, as I suspect there needs to be some actual input on the sources.

This has been confirmed as a bug by Emotiva, and they are working on a fix. From what I am seeing it only happens if a remote application handles EmotivaNotify messages fully, if thoese are skipped and the remote just switch based on user input, I will not happen.

[espenaf]

I other news, OpenHAB 4.2 was released during the summer with the Emotiva binding. The Binding documentation can be found at www.openhab.org/addons/bindings/emotiva/

It was interesting to build this integration, and now I can finally control my XMC-2 via scripting and keyboard shortcuts, like with the following to the OpenHAB REST API:

curl -v -X POST --header "Content-Type: text/plain" --header "Accept: application/json" --data "HTPC" "http://127.0.0.1:8080/rest/items/XMC2_Source"

Espen