Skip to content
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

[HDanywhere] Add support for new line of matrices & updated the documentation #1883

Merged
merged 1 commit into from
Feb 15, 2017

Conversation

kgoderis
Copy link
Contributor

Signed-off-by: Karel Goderis [email protected]

@mention-bot
Copy link

@kgoderis, thanks for your PR! By analyzing the history of the files in this pull request, we identified @kaikreuzer and @svilenvul to be potential reviewers.


This binding integrates with [HDanywhere](http://www.hdanywhere.co.uk) HDMI matrices.

HDanywhereis a manufacturer of multiroom/distributed audio/video equipment. This binding supports their V3 of the Multiroom+ HDMI matrix running firmware V1.2(20131222), as well as the newer MHUB series of matrices. These matrices support the highest HD resolutions, including 1080p 3D & 4K, use a single Cat5e/6/7 wiring structure with reliable performance up to 100m, have IR passback to allow you to select and control what you watch from every room and are fully compatible with universal remote controls
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HDanywhere is


HDanywhereis a manufacturer of multiroom/distributed audio/video equipment. This binding supports their V3 of the Multiroom+ HDMI matrix running firmware V1.2(20131222), as well as the newer MHUB series of matrices. These matrices support the highest HD resolutions, including 1080p 3D & 4K, use a single Cat5e/6/7 wiring structure with reliable performance up to 100m, have IR passback to allow you to select and control what you watch from every room and are fully compatible with universal remote controls

The matrixes can be controlled by either UDP/IP and/or Serial connections, but due to the lack of feedback on the actual state of the HDMI matrix when using those methods, this binding operates by controlling the built-in webserver of the matrix.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

matrices


## Discovery

The binding does not support a discovery feature
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

feature.


## Thing Configuration

Each thing requires the IP address of the matrix, and the interval in between status updates that are fetched from the matrix. Additionally, the *multiroomplus* has an additional required parameter 'ports' to specify the number of physical ports (e.g. 4x4, 8x8,...) of the matrix
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

matrix.

| port8 | Number | The number of the input port that is connected to the output port 8 |


## Binding Configuration
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate of existing section above.

<implementation class="org.openhab.binding.hdanywhere.internal.HDanywhereHandlerFactory"/>

<reference bind="setItemChannelLinkRegistry" cardinality="1..1" interface="org.eclipse.smarthome.core.thing.link.ItemChannelLinkRegistry" name="ItemChannelLinkRegistry" policy="static" unbind="unsetItemChannelLinkRegistry"/>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So bindings are allowed to use the ItemChannelLinkRegistry now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@watou ;-) I see no reason why they would not be allowed to do so, do you?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't say that I know enough to have a fully informed opinion, but with that huge caveat, no I don't know of a reason! ;-)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it is not, see here.
I guess Karel wants to work around the fact that eclipse-archived/smarthome#595 isn't yet implemented.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same reason it's now used in KNX 2.0 binding?

@kgoderis
Copy link
Contributor Author

kgoderis commented Feb 13, 2017 via email

@kgoderis
Copy link
Contributor Author

kgoderis commented Feb 13, 2017 via email

@kaikreuzer
Copy link
Member

@kaikreuzer Shall we proceed with the workaround until the disable feature is provided?

No, I don't think so. What is the issue with having the state update event? Your binding can still send the "final" state itself as soon as it can provide it? That's how it works for almost all bindings.

@kgoderis
Copy link
Contributor Author

kgoderis commented Feb 13, 2017 via email

@kaikreuzer
Copy link
Member

That's absolutely fine and just the way it is designed. Consider the first update to be the "optimistic, but quick guess" and the second as the "definitive, but slow update".
Problems with devices should be anyhow identified by the binding and reported through the Thing status.

@kgoderis
Copy link
Contributor Author

@kaikreuzer done with the small fixes + auto-update revert.

Copy link
Member

@kaikreuzer kaikreuzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, just some very small remarks.

String response = HttpUtil.executeUrl(httpMethod, url, httpHeaders, stream,
"application/x-www-form-urlencoded; charset=UTF-8", timeout);
} catch (IOException e) {
logger.error("Communication with device failed: {}", e);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you set the ThingStatus to OFFLINE with an according message and reduce the logging to debug?

org.apache.commons.lang,
org.eclipse.smarthome.config.core,
org.eclipse.smarthome.core.autoupdate,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this line can be removed again

org.eclipse.smarthome.core.library.types,
org.eclipse.smarthome.core.thing,
org.eclipse.smarthome.core.thing.binding,
org.eclipse.smarthome.core.thing.link,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dito

@kgoderis
Copy link
Contributor Author

@kaikreuzer done.

Copy link
Member

@kaikreuzer kaikreuzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks

@kaikreuzer kaikreuzer merged commit cacd3f6 into openhab:master Feb 15, 2017
fharni pushed a commit to fharni/openhab2-addons that referenced this pull request Feb 19, 2017
jarlebh pushed a commit to jarlebh/openhab2-addons that referenced this pull request Mar 4, 2017
cweitkamp pushed a commit to cweitkamp/openhab-addons that referenced this pull request Mar 26, 2017
@kgoderis kgoderis deleted the hdanywhere-extend branch April 17, 2017 15:05
tratho pushed a commit to tratho/openhab2-addons that referenced this pull request May 5, 2017
@martinvw martinvw changed the title HDanywhere : Add support for new line of matrices + readme.MD [HDanywhere] Add support for new line of matrices & updated the documentation Jun 25, 2017
@martinvw martinvw added the enhancement An enhancement or new feature for an existing add-on label Jun 25, 2017
@martinvw martinvw added this to the 2.1 milestone Jun 25, 2017
Markinus pushed a commit to Markinus/openhab2-addons that referenced this pull request Jul 2, 2017
aogorek pushed a commit to aogorek/openhab2-addons that referenced this pull request Jul 5, 2017
Markinus pushed a commit to Markinus/openhab2-addons that referenced this pull request Sep 8, 2017
Flole998 pushed a commit to Flole998/openhab-addons that referenced this pull request Dec 30, 2021
* Fix wrong Location_Indoor_Floor_SecondFloor translation
* Remove redundant whitespace chars

Signed-off-by: Wouter Born <[email protected]>
markus7017 pushed a commit to markus7017/openhab-addons that referenced this pull request Aug 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement An enhancement or new feature for an existing add-on
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants