I have started setting up my openHAB2 and using the "avmfritz binding from Robert Bausdorf"
as the binding description shows there is support for: FRITZ!Powerline 546E and FRITZ!DECT 200 so no wonder it cannot find my Comet Dect Thermostats, i have linked to the Fritzbox.
is there a way to use them also? Possible Robert Bausdorf read this and can contact me ? 
Best Regards from Karlsruhe
Hannes
Are there some news about the Comet DECT integration?
I used one of the comet DECT and it would be great to control it by Openhab2
Is is possible to controll it by using HTTP GET and SEND requests?
Have you found a way to control it?
Best regards from Voerde (Niederrhein)
Stefan
Hi everyone,
I added support for the new heating thermostat provided by AVM and EUROtronic Technology GmbH. Because I don’t own such devices I’m looking for test users. Please have a look at my fork. Thank you.
https://github.com/openhab/openhab2-addons/issues/1687
“temperature”, “actual_temp”, “set_temp”, “eco_temp”, “comfort_temp” and “battery_low”
demo.things:
Bridge avmfritz:fritzbox:1 [ ipAddress="192.168.xxx.xxx", password ="xxx", user="xxx" ] {
Comet_DECT CD1 [ ain="aaaaaabbbbbb" ]
}
demo.items:
Group gCOMETDECT "Comet DECT heating thermostat" <temperature>
Number COMETDECTActualTemp "Actual measured temperature [%.1f °C]" (gCOMETDECT) { channel="avmfritz:Comet_DECT:1:CD1:actual_temp" }
Number COMETDECTSetTemp "Thermostat temperature setpoint [%.1f °C]" (gCOMETDECT) { channel="avmfritz:Comet_DECT:1:CD1:set_temp" }
Switch COMETDECTBattery "Battery low" (gCOMETDECT) { channel="avmfritz:Comet_DECT:1:CD1:battery_low" }
demo.sitemap:
sitemap demo label="Main Menu"
{
Frame "Comet DECT heating thermostat" {
Text item=COMETDECTActualTemp icon="temperature"
Setpoint item=COMETDECTSetTemp minValue=8.0 maxValue=28.0 step=0.5 icon="temperature"
Switch item=COMETDECTBattery icon="battery"
}
}
Hi,
first of all thank you very much for adding the Comet Dect Device.
I just installed the binding on the on the offical release 2.0 of OH.
I did the following:
Number Living_Heating_Target_1 "Zieltemperatur [%.1f °C]" <heating> (Living, Heating) { channel="avmfritz:Comet_DECT:192_168_178_1:109710470592:set_temp" }
Frame label="Heizung" {
Setpoint item=Living_Heating_Target_1 minValue=8.0 maxValue=28.0 step=0.5
}
This works as expected. The Temperature gets updated on the Fritzbox and on the Comet device!
But i get the following Exception on every Update (every 15 seconds);
16:10:17.006 [ERROR] [.binding.avmfritz.handler.BoxHandler] -
java.lang.NullPointerException
at org.openhab.binding.avmfritz.handler.BoxHandler.updateThingFromDevice(BoxHandler.java:194)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.openhab.binding.avmfritz.handler.BoxHandler.addDeviceList(BoxHandler.java:133)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.openhab.binding.avmfritz.internal.hardware.callbacks.FritzAhaUpdateXmlCallback.execute(FritzAhaUpdateXmlCallback.java:70)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.openhab.binding.avmfritz.internal.hardware.FritzahaContentExchange.onComplete(FritzahaContentExchange.java:71)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:193)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:185)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:453)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.responseSuccess(HttpReceiver.java:400)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.messageComplete(HttpReceiverOverHTTP.java:266)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseContent(HttpParser.java:1487)[71:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1245)[71:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.parse(HttpReceiverOverHTTP.java:156)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:117)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:69)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:89)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:123)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)[72:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[83:org.eclipse.jetty.util:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[83:org.eclipse.jetty.util:9.2.19.v20160908]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
16:10:32.017 [ERROR] [.binding.avmfritz.handler.BoxHandler] -
java.lang.NullPointerException
at org.openhab.binding.avmfritz.handler.BoxHandler.updateThingFromDevice(BoxHandler.java:194)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.openhab.binding.avmfritz.handler.BoxHandler.addDeviceList(BoxHandler.java:133)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.openhab.binding.avmfritz.internal.hardware.callbacks.FritzAhaUpdateXmlCallback.execute(FritzAhaUpdateXmlCallback.java:70)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.openhab.binding.avmfritz.internal.hardware.FritzahaContentExchange.onComplete(FritzahaContentExchange.java:71)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:193)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:185)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:453)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.responseSuccess(HttpReceiver.java:400)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.messageComplete(HttpReceiverOverHTTP.java:266)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseContent(HttpParser.java:1487)[71:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1245)[71:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.parse(HttpReceiverOverHTTP.java:156)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:117)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:69)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:89)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:123)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)[72:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[83:org.eclipse.jetty.util:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[83:org.eclipse.jetty.util:9.2.19.v20160908]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
Hey there, I am going to look into this. Can you please activate logging for the binding and post your xml-response for the update request of your AHA interface?
Did you configure automatic profiles for your device? I assume not.
Here is the log of the binding,containing the response from the fritzbox:
21:01:52.423 [DEBUG] [g.avmfritz.handler.DeviceListPolling] - polling fritzbox org.openhab.binding.avmfritz.config.AvmFritzConfiguration@12d319[IP=192.168.178.1,port=<null>,proto=http,user=<null>,password=,pollingInterval=15,asyncTimeout=10000,syncTimeout=2000]
21:01:52.428 [DEBUG] [ternal.hardware.FritzahaWebInterface] - GETting URL http://192.168.178.1/webservices/homeautoswitch.lua?switchcmd=getdevicelistinfos&sid=27fe605ec5a48cce
21:01:53.058 [DEBUG] [nal.hardware.FritzahaContentExchange] - HTTP response 200
21:01:53.060 [DEBUG] [nal.hardware.FritzahaContentExchange] - HTTP response 200
21:01:53.062 [DEBUG] [nal.hardware.FritzahaContentExchange] - response complete: <devicelist version="1"><device identifier="10971 0470592" id="16" functionbitmask="320" fwversion="03.66" manufacturer="AVM" productname="Comet DECT"><present>1</present><name>Heizung Wohnzimmer</name><temperature><celsius>245</celsius><offset>0</offset></temperature><hkr><tist>49</tist><tsoll>48</tsoll><absenk>30</absenk><komfort>44</komfort></hkr></device><device identifier="08761 0267918" id="17" functionbitmask="896" fwversion="03.59" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>Steckdose TV</name><switch><state>1</state><mode>manuell</mode><lock>0</lock></switch><powermeter><power>82820</power><energy>91788</energy></powermeter><temperature><celsius>245</celsius><offset>0</offset></temperature></device></devicelist>
21:01:53.248 [DEBUG] [.binding.avmfritz.handler.BoxHandler] - set device model: org.openhab.binding.avmfritz.internal.ahamodel.DeviceModel@41f9cb[ain=109710470592,bitmask=320,isDectRepeater=false,isPowermeter=false,isTempSensor=true,isSwitchableOutlet=false,isHeatingThermostat=true,id=16,manufacturer=AVM,productname=Comet DECT,fwversion=03.66,present=1,name=Heizung Wohnzimmer,<null>,<null>,org.openhab.binding.avmfritz.internal.ahamodel.TemperatureModel@db2253[celsius=24.5,offset=0.0],org.openhab.binding.avmfritz.internal.ahamodel.HeatingModel@1d640ef[tist=24.5,tsoll=24.0,absenk=15.0,komfort=22.0,lock=<null>,errorcode=<null>,batterylow=<null>,nextchange=<null>]]
21:01:53.252 [DEBUG] [.binding.avmfritz.handler.BoxHandler] - update thing avmfritz:Comet_DECT:192_168_178_1:109710470592 with device model: org.openhab.binding.avmfritz.internal.ahamodel.DeviceModel@41f9cb[ain=109710470592,bitmask=320,isDectRepeater=false,isPowermeter=false,isTempSensor=true,isSwitchableOutlet=false,isHeatingThermostat=true,id=16,manufacturer=AVM,productname=Comet DECT,fwversion=03.66,present=1,name=Heizung Wohnzimmer,<null>,<null>,org.openhab.binding.avmfritz.internal.ahamodel.TemperatureModel@db2253[celsius=24.5,offset=0.0],org.openhab.binding.avmfritz.internal.ahamodel.HeatingModel@1d640ef[tist=24.5,tsoll=24.0,absenk=15.0,komfort=22.0,lock=<null>,errorcode=<null>,batterylow=<null>,nextchange=<null>]]
21:01:53.254 [DEBUG] [.binding.avmfritz.handler.BoxHandler] - about to update thing avmfritz:Comet_DECT:192_168_178_1:109710470592 from device org.openhab.binding.avmfritz.internal.ahamodel.DeviceModel@41f9cb[ain=109710470592,bitmask=320,isDectRepeater=false,isPowermeter=false,isTempSensor=true,isSwitchableOutlet=false,isHeatingThermostat=true,id=16,manufacturer=AVM,productname=Comet DECT,fwversion=03.66,present=1,name=Heizung Wohnzimmer,<null>,<null>,org.openhab.binding.avmfritz.internal.ahamodel.TemperatureModel@db2253[celsius=24.5,offset=0.0],org.openhab.binding.avmfritz.internal.ahamodel.HeatingModel@1d640ef[tist=24.5,tsoll=24.0,absenk=15.0,komfort=22.0,lock=<null>,errorcode=<null>,batterylow=<null>,nextchange=<null>]]
21:01:53.267 [ERROR] [.binding.avmfritz.handler.BoxHandler] -
java.lang.NullPointerException
at org.openhab.binding.avmfritz.handler.BoxHandler.updateThingFromDevice(BoxHandler.java:194)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.openhab.binding.avmfritz.handler.BoxHandler.addDeviceList(BoxHandler.java:133)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.openhab.binding.avmfritz.internal.hardware.callbacks.FritzAhaUpdateXmlCallback.execute(FritzAhaUpdateXmlCallback.java:70)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.openhab.binding.avmfritz.internal.hardware.FritzahaContentExchange.onComplete(FritzahaContentExchange.java:71)[243:org.openhab.binding.avmfritz:2.1.0.201702022035]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:193)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:185)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:453)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.responseSuccess(HttpReceiver.java:400)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.messageComplete(HttpReceiverOverHTTP.java:266)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseContent(HttpParser.java:1487)[71:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1245)[71:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.parse(HttpReceiverOverHTTP.java:156)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:117)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:69)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:89)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:123)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)[72:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[83:org.eclipse.jetty.util:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[83:org.eclipse.jetty.util:9.2.19.v20160908]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
21:01:53.275 [DEBUG] [.binding.avmfritz.handler.BoxHandler] - set device model: org.openhab.binding.avmfritz.internal.ahamodel.DeviceModel@5c5dab[ain=087610267918,bitmask=896,isDectRepeater=false,isPowermeter=true,isTempSensor=true,isSwitchableOutlet=true,isHeatingThermostat=false,id=17,manufacturer=AVM,productname=FRITZ!DECT 200,fwversion=03.59,present=1,name=Steckdose TV,org.openhab.binding.avmfritz.internal.ahamodel.SwitchModel@17662ca[state=1,mode=manuell,lock=0],org.openhab.binding.avmfritz.internal.ahamodel.PowerMeterModel@98148d[power=82.820,energy=91.788],org.openhab.binding.avmfritz.internal.ahamodel.TemperatureModel@19efc09[celsius=24.5,offset=0.0],<null>]
What do you exactly mean by “automatic profiles”?
Hi,
thank you. I worked out a solution for the NPE. The problem is, that the binding expects a <batterylow> tag within the response of the fb. There is no such tag in your version.
I uploaded a new .jar file with my last commit 17ab448. Please try that one.
btw: “automatic profiles” is a very silly expression. Why did I use that??? I should use the term “schedules”. I think that is much better.
Thank you very much for your work! I just updated the binding and it works as expected, the error logs are gone.
I guess in my case i cant use the channel “Battery Level Low”, which is ok for me.
Today I played around with the channels of the “Comet Dect”. They all work fine, excepted “Battery Level Low”, which makes now sense as mentioned in your post.
In my opion just one minor thing would nice to be changed.
The two “Actual Temperature” and “Actual Temperature of heating thermostat” showing the exact same Temperatue.
At least for me there is no difference. So I took a look in the response from the fb:
<device identifier="10971 0470592" id="16" functionbitmask="320" fwversion="03.66" manufacturer="AVM" productname="Comet DECT">
<present>1</present>
<name>Heizung Wohnzimmer</name>
<temperature>
<celsius>240</celsius>
<offset>5</offset>
</temperature>
<hkr>
<tist>48</tist>
<tsoll>44</tsoll>
<absenk>30</absenk>
<komfort>44</komfort>
</hkr>
</device>
As you can see the fb provides an Offset, which is used to tell the Comet it actually warmer or colder then mesasured.
Maybe it makes more sense to show the Offset temperature in one these channels.
btw: I use automatic schedules from the fb, but it work anyways. You just have to be aware that the Temperature will change, if a schedule change is triggered. But this gets of course updated to OH.
Greetings!
Hi,
the binding work’s perfectly with my FB7490, FritzOS6.80. Wich Firmware running @ your fb? New items came with the new firmware . I’m using one Comet and two DECT300.
Thank you, too. Nice to hear.
Which FRITZ!OS version do you use? Which FRITZ!Box do you own?
I asked for automatic schedules because the interface version I tested returns in addition to the <batterylow>-tag more information about the next schedule time and the next temperature to be set.
The two channels for the Actual Temperature are connected to different parameters of the interface. Let’s have a look at your xml-response in the above post. First there is one <temperature>-tag for the Comet DECT device. This tag is connected to the first channel “temperature” (similar to a Fritz!DECT 200 device). The <tist>-tag within the <hkr>-tag is connected to the second channel “actual_temp” (only provided by a heating thermostat). I assume that both channels show the same value, but they are handled different in the binding.
Your suggestion for an “offset” channel is nice. I put that on my TODO-list.
I have the fb 6490 with frtizos 6.50. I dont think there is a newer version for this fb, right now.
Seems they hav enhanced the interface with version 6.80.
Maybe there is a way to check the os version and depeding on the version you can provide more channels?
I think smarthome functionality came with fritzOS 6.60. Laborversion?
here my new devicelist
<a class="attachment" href="//community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/0/0f3d216094cf9b6cb1f4e76e5e6d1a7ce7ca8f17.xml">fritz.xml</a> (3.8 KB)I am afraid checking FRITZ!OS version via the interface is not possible. I have to mention it in the documentation of the binding.
In the first moment I thought I can use the functionbitmask-attribute. This should indicate which functions are supported by each device. But I cannot detect any differences between both of your the xml-snippets exept the functionbitmask of the DECT200. Do you? Since FRITZ!OS 6.60 it says 2944. Before it was 896. Only new part is the “devicelock”-tag for DECT200.
Comet DECT and DECT300 both say functionbitmask 320. “lock”, “devicelock”, “errorcode”, “batterylow” and “nextchange”-tags are completely missing in the old version.
The device-tag attribute “version” always returns 1.
The tutorial on binding development of oh2 tells me in the Thing Type Definitions section that I can declare some channels as “advanced”. If “advanced” is set to true the user interface will hide this channel by default. Maybe I should use that feature on the “battery_low” (“next_temp”, “next_change”) channel(s).
I found a NPE
2017-02-06 07:09:46.145 [ERROR] [.binding.avmfritz.handler.BoxHandler] -
java.lang.NullPointerException
at org.openhab.binding.avmfritz.handler.BoxHandler.updateThingFromDevice(BoxHandler.java:203)[12:org.openhab.binding.avmfritz:2.1.0.201702051325]
at org.openhab.binding.avmfritz.handler.BoxHandler.addDeviceList(BoxHandler.java:137)[12:org.openhab.binding.avmfritz:2.1.0.201702051325]
at org.openhab.binding.avmfritz.internal.hardware.callbacks.FritzAhaUpdateXmlCallback.execute(FritzAhaUpdateXmlCallback.java:70)[12:org.openhab.binding.avmfritz:2.1.0.201702051325]
at org.openhab.binding.avmfritz.internal.hardware.FritzahaContentExchange.onComplete(FritzahaContentExchange.java:71)[12:org.openhab.binding.avmfritz:2.1.0.201702051325]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:193)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:185)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:453)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.responseSuccess(HttpReceiver.java:400)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.messageComplete(HttpReceiverOverHTTP.java:266)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseContent(HttpParser.java:1487)[75:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1245)[75:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.parse(HttpReceiverOverHTTP.java:156)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:117)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:69)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:89)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:123)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)[76:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[87:org.eclipse.jetty.util:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[87:org.eclipse.jetty.util:9.2.19.v20160908]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
2017-02-06 07:09:46.320 [ERROR] [.binding.avmfritz.handler.BoxHandler] -
java.lang.NullPointerException
at org.openhab.binding.avmfritz.handler.BoxHandler.updateThingFromDevice(BoxHandler.java:203)[12:org.openhab.binding.avmfritz:2.1.0.201702051325]
at org.openhab.binding.avmfritz.handler.BoxHandler.addDeviceList(BoxHandler.java:137)[12:org.openhab.binding.avmfritz:2.1.0.201702051325]
at org.openhab.binding.avmfritz.internal.hardware.callbacks.FritzAhaUpdateXmlCallback.execute(FritzAhaUpdateXmlCallback.java:70)[12:org.openhab.binding.avmfritz:2.1.0.201702051325]
at org.openhab.binding.avmfritz.internal.hardware.FritzahaContentExchange.onComplete(FritzahaContentExchange.java:71)[12:org.openhab.binding.avmfritz:2.1.0.201702051325]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:193)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:185)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:453)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpReceiver.responseSuccess(HttpReceiver.java:400)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.messageComplete(HttpReceiverOverHTTP.java:266)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseContent(HttpParser.java:1487)[75:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1245)[75:org.eclipse.jetty.http:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.parse(HttpReceiverOverHTTP.java:156)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:117)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:69)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:89)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:123)[73:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)[76:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[87:org.eclipse.jetty.util:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[87:org.eclipse.jetty.util:9.2.19.v20160908]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
from the dect300? every 15s
new insights:
devicelock == keylock (Tastensperre am Thermostat)
lock == lock (Manuellen Zugriff für Telefon, App oder Benutzeroberfläche deaktivieren)
Make sense. Does the “devicelock” disable the new switch on sound feature like clapping or knocking, too?
The NPE is thrown because of the missing channels “next_change” and “next_temp” for the DECT300 device. Provide an update soon.
//EDIT: new .jar file can be found here.
No , the switch on sound has a separatly checkbox at fb-ui.
I’ll try to use Comet Dect with following thing
Bridge avmfritz:fritzbox:192_168_2_1 [ ipAddress=“192.168.2.1”, password =“xxxxx”, user=“xxx” ]
{
Comet_DECT CD1 [ ain=“1234567890” ]
}
But i get nothing (not in event.log)
Can anyone find my error?
Hi,
there is a not working example of the fritzbox thing configuration in the documentation. See discussion here: https://github.com/openhab/openhab2-addons/pull/1963 and here: [avmfritz] FRITZ!DECT 200 jsut "INITIALIZING" and items don't work
Dear SnakeEater
Sorry. With FRITZ_DECT_200 it works perfect. But not with Comet Dect thermostat