ruebox / openhab2-addons

Add-ons for openHAB 2.x
Eclipse Public License 1.0
16 stars 6 forks source link

Snapshot - 240318 #14

Closed ruebox closed 6 years ago

ruebox commented 6 years ago

New snapshot with the following fixes based on commit: 88c0ff78a709f3489a01f026670f1311c1bf463c is available.

New supported deviceIds:

solves issues #2, #9, #7

Please checkout the jar and provide feedback what is working and what not.

Thx in advance for your support and patient. Hope we are reaching the baseline on stability and well working things :-)

Support needed:

To get an overview on the working and not working devices, I generate a wiki page that is listing all supported devices incl. deviceTypeId. Could you please add a new column! Thx!

org.openhab.binding.freeathome-2.0.0-SNAPSHOT-240318.jar.zip

BastianZim commented 6 years ago

Hey, thanks for the update. Installed it on a fresh version and dimmers and thermostats now work for me. I still can't get the switches to work (1/1 2/2 and 8/8), I attached the code from the webUI below for my 8/8 when I clicked on a lamp:

<iq xmlns="jabber:client" to="mrha@busch-jaeger.de/rpc" type="set" id="1521916169080"><query xmlns="jabber:iq:rpc"><methodCall><methodName>RemoteInterface.setDatapoint</methodName><params><param><value><string>ABB259EF2651/ch000C/idp0000</string></value></param><param><value><string>1</string></value></param></params></methodCall></query></iq> 1521916169.0820723

<iq type='result' to='installer@busch-jaeger.de/380e16' from='mrha@busch-jaeger.de/rpc' id='1521916169080' xmlns='jabber:client'><query xmlns='jabber:iq:rpc'><methodResponse><params><param><value><boolean>1</boolean></value></param></params></methodResponse></query></iq> 1521916169.1474571

<message xmlns='jabber:client' type='headline' to='installer@busch-jaeger.de/380e16' from='mrha@busch-jaeger.de'><event xmlns='http://jabber.org/protocol/pubsub#event'><items node='http://abb.com/protocol/update'><item id='1'><update xmlns='http://abb.com/protocol/update'><data>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;project timeStamp=&quot;91789&quot; sessionId=&quot;7c23e0b&quot; type=&quot;update&quot; mrhaVersion=&quot;2.1.6&quot; mrhaBuild=&quot;5966&quot;&gt;&lt;privileges/&gt;&lt;devices&gt;&lt;device serialNumber=&quot;ABB700C83D95&quot; domainAddress=&quot;9376&quot; state=&quot;modified&quot; commissioningState=&quot;ready&quot; progress=&quot;100&quot;&gt;&lt;channels&gt;&lt;channel state=&quot;modified&quot; i=&quot;ch0000&quot; cid=&quot;ABB70303&quot;&gt;&lt;inputs&gt;&lt;dataPoint state=&quot;modified&quot; i=&quot;idp0000&quot; full=&quot;false&quot;&gt;&lt;value&gt;1&lt;/value&gt;&lt;/dataPoint&gt;&lt;/inputs&gt;&lt;outputs/&gt;&lt;parameters/&gt;&lt;scenes/&gt;&lt;/channel&gt;&lt;/channels&gt;&lt;/device&gt;&lt;device serialNumber=&quot;ABB700CBAC7D&quot; domainAddress=&quot;9376&quot; state=&quot;modified&quot; commissioningState=&quot;ready&quot; progress=&quot;100&quot;&gt;&lt;channels&gt;&lt;channel state=&quot;modified&quot; i=&quot;ch0000&quot; cid=&quot;ABB705E9&quot;&gt;&lt;inputs&gt;&lt;dataPoint state=&quot;modified&quot; i=&quot;idp0000&quot; full=&quot;false&quot;&gt;&lt;value&gt;1&lt;/value&gt;&lt;/dataPoint&gt;&lt;/inputs&gt;&lt;outputs/&gt;&lt;parameters/&gt;&lt;scenes/&gt;&lt;/channel&gt;&lt;/channels&gt;&lt;parameters/&gt;&lt;/device&gt;&lt;device serialNumber=&quot;ABB259EF2651&quot; domainAddress=&quot;9376&quot; state=&quot;modified&quot; commissioningState=&quot;ready&quot;&gt;&lt;channels&gt;&lt;channel state=&quot;modified&quot; i=&quot;ch000C&quot; cid=&quot;ABB20208&quot;&gt;&lt;inputs&gt;&lt;dataPoint state=&quot;modified&quot; i=&quot;idp0000&quot; full=&quot;false&quot;&gt;&lt;value&gt;1&lt;/value&gt;&lt;/dataPoint&gt;&lt;/inputs&gt;&lt;outputs&gt;&lt;dataPoint state=&quot;modified&quot; i=&quot;odp0000&quot; full=&quot;false&quot;&gt;&lt;value&gt;1&lt;/value&gt;&lt;/dataPoint&gt;&lt;/outputs&gt;&lt;parameters/&gt;&lt;scenes/&gt;&lt;/channel&gt;&lt;/channels&gt;&lt;parameters/&gt;&lt;/device&gt;&lt;/devices&gt;&lt;/project&gt; </data></update></item></items></event></message> 1521916169.311708

The only reason I can come up with is that not every channel is used and that some channels are used to control lights, whereas others are inputs from motion sensors and physical switches in the wall.

ruebox commented 6 years ago

Hi, channel scheme is different for this device. Thx for the log. Generated a new issue #15. Could you please check if the switch is working if you manually change the channel ch0000 -> ch000C? Thx.

BastianZim commented 6 years ago

Hi, no problem, glad to help. But that wouldn't explain why I can't see the other switches that aren't 8/8, right?

ruebox commented 6 years ago

I generate a wiki page where all supported devices are listed incl. Device typeId. Perhaps the ids of your devices are not supported yet. In the configuration of the bridge, you could active the "Dummy things enabled". Then all things are discovery and the deviceTypeId will be visible. image

BastianZim commented 6 years ago

Ok, thanks, dummies are already enabled, then I'll have a look at the devices page. Do you know if there is a way to find the device ID from the B+J webUI?

One thing that just came to my mind, is that my things have a cabled connection and maybe that's the problem since B+J came out with wireless version some time ago. Maybe you could add as well to the wiki whether they are cabled or wireless.

BastianZim commented 6 years ago

Alright, I've added everything now and you were right they are indeed different devices, probably due to wireless vs. wired. If you want to implement them, they should be in my files, otherwise, I can send them to you again.

Thanks!

BastianZim commented 6 years ago

Just FYI, I also added the value test for items that you can test once they are implemented.

BastianZim commented 6 years ago

And changing it to ch000C makes it work, but only for that channel, not for everything that is connected to the device.

lassem commented 6 years ago

Okay, dimmers now work, but there's still a problem with the type I think:

image

No slider and looks more like a roller shutter than a dimmer. The fading works though, it takes 5 or so seconds to fade from lowest to highest. The stop-button has no function and the value in the fading field seem to be reverse of what one would think, but the actual operation is correct. Ie. 0 = full effect on arrow up. 100 = lowest effect on arrow down. Stop/square button = no function.

ruebox commented 6 years ago

replaced by #20 .