I added the new version of your binding and added to following to the openhab.cfgįinally, I created some dimmers in the ems file:ĭimmer Light_GF_Living_D1 "Up-light" (GF_Living, Lights)
I meant to post an Rx like this:ĭespite my cut 'n' paste error, I'm not getting updates from external switch presses.įor testing I've created an 'out of the box' openhab instance using the demo sample configuration & add-ons. They've just ignored the stateless practice, and injected the item registry into the binding so that they can get the dim state of the device, and send the appropriate onward command. Seem's like other's have also had problems with the stateless nature of bindings - !category-topic/openhab/discussions/UeexB3MRLBU. X10, so that we can have a simple binding that:Ī) In addition to on/off, sends the correct dim/bright commandsī) Monitors for state changes initiated outside of openHAB (i.e. I'd be grateful if you can think of any way around the above problems of Item state, and then posts a message back on the mqqt queue for the rubyīridge to pass to Mochad. Trigger on each item command received event and call a lambda function which calculates whether the command should be 'dim' or 'bright' and the relative amounts based on the current Processes all inbound messages in openHAB and updates the openHAB itemįor commands originating from openHAB items, I have individual rules that I have a ruby script that is bridging between Mochad and Mosquitto mqttįorwards all Rx tagged Mochad messages to openHAB. Part (though I'm not sure about it's stability or reliabity), by using MQTT Needs to know the current state, which reading the binding developmentĭocumentation, seems to be not considered good practice.įor now, I have a temporary set up which appears to be working for the most However, the problem with this is that the binding
Openhab2 dropbox plugin code#
For suchĭevices, it may be useful to add a parameter 'supportsExtendedCommands' orĪlso I had a look at the code in your binding to modify it to to supportĭim/bright commands. "Dim" command will ALWAYS dim from the current brightness level.
Relative values (with range 0 - 31 instead of the 62 for xdim). Work is to send only 'Dim' or 'Bright' commands, both of which are For these, the only way to get dimming to I've tried sending xdim directly through netcat,īut the devices don't respond. The X10 devices I have (about 10 different units) though they claim to
Unfortunately I couldn't get this to work with any of openhab messages always have Tx) and so can beĪlso FYI, I noticed in your binding you use 'xdim' for sending exactīrightness levels. Messages received from physical hardware buttons. Dim/BrightĪpply to the last device that had an On function. You'll note that the On/Off responses are sent over two lines. Up to date with device states as it can be given the limitations of X10.Ġ2/22 15:50:08 Rx PL House: B Func: Bright(13)Ġ2/22 15:50:12 Rx PL House: B Func: Dim(16) Physical button to turn on/off/dim a specific light, so that OpenHAB is as scenes), as well as tracking status changes when someone uses a Thanks for coming back, and yes that is exactly what I've been trying to do
0 kommentar(er)
