-
Notifications
You must be signed in to change notification settings - Fork 16
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
add support for generic command frame (WHO=? WHAT=? WHERE=?) #52
Comments
This function is already expressed in this issue #22 |
In fact the issue is similar, but I prefer the description and specification here, for example to divide WHO,WHAT,WHERE (to avoid wrong frames are sent on the BUS) and to have two separate channels or Things type for sending commands and receiving generic events. |
sorry, the usage in rules should be something like:
(changed .sendCommand(ON) to .sendCommand("16") in the example. In fact, the sendCommand should be able to send a generic WHAT content). |
Assignee to me |
Is possible to have a simple example how to configure properly the "generic device" im try to get own command to the bus i have tryed this code to *.things file: and this code to *.items file: the generic device in things list show "Unknown" state and no linked to relative item. I have found this "v2.5.0.M3.pre12" in Gozilla01 repository but the bus bridge can't connect to the MH200N because is old relase this version have a bus_command but i think is not same as Thanks |
any progress on this? or should this work already? |
Hi,
And use the Exec binding to run the script as you want in openhab. |
Hi, i have a similar problem with my new fresh installation of OH3. No support for the WHO=6. I found your solution @francesco-re-1107 and it's very interesting. The only problem is that i'm not so able with Python. Can anyone specify all the steps to implement the script in the Exec binding from the beginning (starting from python setup)? Thank you sooooo much! |
Expected Behavior
Create a couple of generic things to post generic command frames on the OWN bus and gather the returned information, like for example:
*1*16*77##
(turn light 77 on for 15 minutes).
This would allow to benefit of full OWN features while enhancing the binding more and more.
To gather feedback from the system, a specific channel should be added in order to intercept all events filtered by a specified mask.
Here below how the things and items may be specified to allow this:
This may be useful also for debugging purposes.
The text was updated successfully, but these errors were encountered: