Closed lassem closed 6 years ago
Hey, I'm not the maintainer so not 100% sure, but it would be very helpful if you could test the new thermostat and switch function since it didn't work for me.
Thanks by the way for participating as well!
Hi there,
I am in a flow and just added the dimmers ... please checkout a testing version attached.
Have fun and just let me know if something is not working.
@lassem Thanks for the xml. It helped a lot to find the correct ids and missing devices. org.openhab.binding.freeathome-2.0.0-SNAPSHOT.jar.zip
I've tried to get that build to run quite a few times now, but I can't get it to work. I've downgraded to OpenHAB 2.0.0-1 (since I couldn't get it to build from your branch rebased onto 2.2.0-SNAPSHOT anymore)
Any ideas? Ubuntu 16.04
2018-03-20 23:41:47.574 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.freeathome-2.0.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.freeathome [175]
Unresolved requirement: Import-Package: org.openhab.core.library.types
at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:392)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1253)[4:org.apache.felix.fileinstall:3.5.6]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1225)[4:org.apache.felix.fileinstall:3.5.6]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:512)[4:org.apache.felix.fileinstall:3.5.6]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:361)[4:org.apache.felix.fileinstall:3.5.6]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:312)[4:org.apache.felix.fileinstall:3.5.6]
Hi, I can reproduce the issue. It seems to be linked with the pom.xml and manifest because the addon is properly running in my development environment. However, in oh 2.2. release build I get the same error.
In order to run mvn package successfully, I had to add: Import-Package: ... org.openhab.core.library.types,
to Manifest.mf. Then mvn package is successful, but the dependencies are missing.
If you have an idea to solve it ... just let me know.
I will check the internet ... Best
The org.openhab.core.libraries.type
package seems to live inside the org.openhab.core.compat1x
bundle.
I installed this package https://docs.openhab.org/developers/development/compatibilitylayer.html via the console https://docs.openhab.org/administration/console.html
Not getting an error message in the logs, but not getting the addon either :-/
I got it to work!
Not really sure what fixed it.
I uninstalled openhab2 by running apt-get purge openhab2
Reinstalled openhab 2.2 with a regular apt-get install openhab2
Selected the expert
-package option when configuring openhab.
Downloaded your dimmer version of the addon and it worked.
Tested a dimmer and it works, but this version seems to only find some of my dimmers. The 4-fach ones. I am missing amongst others 2/1 dim actuator ABB800C6DF71 and 1/1 dim actuator ABB700C6C787
Hi @lassem,
I rebuild the jar and now the org.openhab.core.libraries.type are not longer required. I do not know why as I did not changed any code.
However, the binding started successfully with oh 2.2.0 release build and purely ui setup. Seems that some inconsistencies introduced some oh 1. dependencies.
Update will follow.
@lassem Please find a new version attached. I will now include new dimmer device ids: case "9017": // 1/1 dim actuator case "9019": // 2/1 dim actuator
Please check if the binding is now working in openhab simply UI setup and with your dimmers.
Thanks
@ruebox Did you forget to attach the jar?
Yes, just updated it with the switches. You will find it on #10
@ruebox Nevermind, just saw Issue #10 👍
Here's an excerpt from the xmpp communication while in the free@home interface and turning the light on and off.
<datagrab>
<iq xmlns="jabber:client" to="mrha@busch-jaeger.de/rpc" type="set" id="1521825556464">
<query xmlns="jabber:iq:rpc">
<methodCall>
<methodName>RemoteInterface.setDatapoint</methodName>
<params>
<param>
<value>
<string>ABB700C6DF1E/ch0006/idp0000</string>
</value>
</param>
<param>
<value>
<string>0</string>
</value>
</param>
</params>
</methodCall>
</query>
</iq>
<iq type='result' to='installer@busch-jaeger.de/c54216' from='mrha@busch-jaeger.de/rpc' id='1521825556464'
xmlns='jabber:client'>
<query xmlns='jabber:iq:rpc'>
<methodResponse>
<params>
<param>
<value>
<boolean>1</boolean>
</value>
</param>
</params>
</methodResponse>
</query>
</iq>
<message xmlns='jabber:client' type='headline' to='installer@busch-jaeger.de/c54216' 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><?xml version="1.0" encoding="UTF-8"?><project timeStamp="479821"
sessionId="117af773" type="update" mrhaVersion="2.1.6"
mrhaBuild="5966"><privileges/><devices><device serialNumber="ABB700C6DF1E"
domainAddress="CFCC" state="modified" commissioningState="ready"
progress="100"><channels><channel state="modified" i="ch0000"
cid="ABB705E9"><inputs><dataPoint state="modified" i="idp0000"
full="false"><value>0</value></dataPoint></inputs><outputs/><parameters/><scenes/></channel><channel
state="modified" i="ch0006" cid="ABB70262"><inputs><dataPoint
state="modified" i="idp0000" full="false"><value>0</value></dataPoint></inputs><outputs><dataPoint
state="modified" i="odp0000" full="false"><value>0</value></dataPoint></outputs><parameters/><scenes/></channel></channels><parameters/></device></devices></project>
</data>
</update>
</item>
</items>
</event>
</message>
<message xmlns='jabber:client' type='headline' to='installer@busch-jaeger.de/c54216' 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><?xml version="1.0" encoding="UTF-8"?><project timeStamp="479822"
sessionId="117af773" type="update" mrhaVersion="2.1.6"
mrhaBuild="5966"><privileges/><devices><device serialNumber="ABB700C6DF1E"
domainAddress="CFCC" state="modified" commissioningState="ready"
progress="100"><channels><channel state="modified" i="ch0006"
cid="ABB70262"><inputs/><outputs><dataPoint state="modified"
i="odp0001" full="false"><value>0</value></dataPoint></outputs><parameters/><scenes/></channel></channels><parameters/></device></devices></project>
</data>
</update>
</item>
</items>
</event>
</message>
<iq xmlns="jabber:client" to="mrha@busch-jaeger.de/rpc" type="set" id="1521825561652">
<query xmlns="jabber:iq:rpc">
<methodCall>
<methodName>RemoteInterface.setDatapoint</methodName>
<params>
<param>
<value>
<string>ABB700C6DF1E/ch0006/idp0000</string>
</value>
</param>
<param>
<value>
<string>1</string>
</value>
</param>
</params>
</methodCall>
</query>
</iq>
<iq type='result' to='installer@busch-jaeger.de/c54216' from='mrha@busch-jaeger.de/rpc' id='1521825561652'
xmlns='jabber:client'>
<query xmlns='jabber:iq:rpc'>
<methodResponse>
<params>
<param>
<value>
<boolean>1</boolean>
</value>
</param>
</params>
</methodResponse>
</query>
</iq>
<message xmlns='jabber:client' type='headline' to='installer@busch-jaeger.de/c54216' 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><?xml version="1.0" encoding="UTF-8"?><project timeStamp="479823"
sessionId="117af773" type="update" mrhaVersion="2.1.6"
mrhaBuild="5966"><privileges/><devices><device serialNumber="ABB700C6DF1E"
domainAddress="CFCC" state="modified" commissioningState="ready"
progress="100"><channels><channel state="modified" i="ch0000"
cid="ABB705E9"><inputs><dataPoint state="modified" i="idp0000"
full="false"><value>1</value></dataPoint></inputs><outputs/><parameters/><scenes/></channel><channel
state="modified" i="ch0006" cid="ABB70262"><inputs><dataPoint
state="modified" i="idp0000" full="false"><value>1</value></dataPoint></inputs><outputs><dataPoint
state="modified" i="odp0000" full="false"><value>1</value></dataPoint></outputs><parameters/><scenes/></channel></channels><parameters/></device></devices></project>
</data>
</update>
</item>
</items>
</event>
</message>
<message xmlns='jabber:client' type='headline' to='installer@busch-jaeger.de/c54216' 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><?xml version="1.0" encoding="UTF-8"?><project timeStamp="479824"
sessionId="117af773" type="update" mrhaVersion="2.1.6"
mrhaBuild="5966"><privileges/><devices><device serialNumber="ABB700C6DF1E"
domainAddress="CFCC" state="modified" commissioningState="ready"
progress="100"><channels><channel state="modified" i="ch0006"
cid="ABB70262"><inputs/><outputs><dataPoint state="modified"
i="odp0001" full="false"><value>12</value></dataPoint></outputs><parameters/><scenes/></channel></channels><parameters/></device></devices></project>
</data>
</update>
</item>
</items>
</event>
</message>
</datagrab>
Hi. looks like as if some device channels do not start at ch000, but with #channels - 1
Could you please manually adapt the channels of the following devices via PaperUI: Serial - deviceTypeId - discovered channel -> new channel
If all your dimmers are then working. I would generate a new version with adapted discovery.
fixed with 877685f7dc95448b4322c84bc1199ee899278034
closed. please checkout #14
I am mainly creating this to share my getAll.xml file. Included my latest log file as well, albeit it was 4+ MB.
Archive.zip
What can I do to contribute?