search

micolous / cbus

Use Python to communicate with a Clipsal C-Bus PCI or CNI! Includes MQTT bridge (for Home Assistant), PCI simulator, and reverse engineering notes.
http://cbus.readthedocs.org/
GNU Lesser General Public License v3.0
49 stars 27 forks source link

Support for other applications #19

Open hamBank opened 4 years ago

hamBank commented 4 years ago

Hi,

I've got a cbus install that includes a blind application - I'm not 100% sure if this is a standard cbus app or was custom created for my project. Is there an easy way to add and expose an additional application?

Apart from that - a massive thanks for creating this! I'd been fighting solutions with cgate for years and your code was up and running and working in about 15 minutes.

micolous commented 3 years ago

Glad it could help you :)

According to the protocol docs, there's a Position Feedback for Motorised Blinds, but there's no assigned application ID for it, nor is that part published publicly.

It depends on how your install is set up, and that's highly discretionary – the smaller installs I've looked at generally use Lighting Application (0x38) for everything, even for things like ceiling fans with speed control.

If you have a copy of your project file, Toolkit should tell you what application they're assigned to. Or even let you set up some triggers that let it be controlled by the main lighting application.

hamBank commented 3 years ago

Thanks Michael, Can we expose other application IDs easily if I find what it is using?

On Tue, Oct 13, 2020 at 3:03 PM Michael Farrell notifications@github.com wrote:

Glad it could help you :)

According to the protocol docs, there's a Position Feedback for Motorised Blinds, but there's no assigned application ID for it, nor is that part published publicly.

It depends on how your install is set up, and that's highly discretionary – the smaller installs I've looked at generally use Lighting Application ( 0x38) for everything, even for things like ceiling fans with speed control.

If you have a copy of your project file, Toolkit should tell you what application they're assigned to. Or even let you set up some triggers that let it be controlled by the main lighting application.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/micolous/cbus/issues/19#issuecomment-707471161, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMGIPHAH6TLQPLYOCP5CQLSKPGQXANCNFSM4RPR6ZLA .

micolous commented 3 years ago

It's not just the application ID, it's also what commands it's expecting; and both are kinda non-trivial to plumb.

The low level APIs in libcbus support lighting commands on arbitrary application IDs, but this isn't fully plumbed up through pciprotocol and cmqttd, because I've never had a need for it.

If you can send me your Toolkit project file, then I can probably tell you what's going on. Toolkit should be also able to discover all of the units on a network and download their configuration.