FRITZ!DECT 200 remains in Status INITIALIZING -> changed to binding reacts not on fixed status

Heiko_Fanieng · February 29, 2016, 7:50pm

Hello all,

after spending a weekend without testing OH2 and updating to the latest Cloudbees build #161 the Outlet-function of the linked channels stopped working with this message in the log:

Not delegating command 'ON' for item 'K_Schrank' to handler for channel 'avmfritz:FRITZ_DECT_200:192_168_178_1:087610216689:outlet', because thing is not initialized (must be in status ONLINE or OFFLINE).

Where there some relevant changes between last week where it definitely works and now?

Regards
Heiko

Kai · February 29, 2016, 9:43pm

I didn’t analyze it any closer, but it sounds similar to me as https://github.com/eclipse/smarthome/issues/1075. Something that needs to be looked at, I will add a link on that issue.

Kai · February 29, 2016, 9:46pm

Btw, it is interesting that you say that it worked in the past, because I just remembered that there is an open issue in the tracker about the FRITZ!DECT 200: https://github.com/openhab/openhab2-addons/issues/392

Heiko_Fanieng · February 29, 2016, 10:21pm

Thanks for your fast feedback @Kai,

maybe it depends of the very awesome progress of OH2 in the last months, so i could only confirm what worked last week. For the next test as Beta-Tester i’ll try to keep the nightly-bilding-version of cloudbees in mind for further reports

FRITZ!DECT 200 worked for me last week, i ordered 2 more devices and with [quote=“Heiko_Fanieng, post:1, topic:8148”]
Cloudbees build #161
[/quote] all devices stopped working in the switching part today.

Maybe tomorrow i’ll focus on Philips Hue and/or Z-Wave - i don’t have the intention as beta-tester to expect that everything works as expected

Regards,
Heiko

Kai · February 29, 2016, 10:40pm

Thanks for your patience as a beta tester.
I just analyzed it: The change was indeed due to a recent change in ESH, which now does not automatically set a Thing to ONLINE anymore, but leaves it to the binding to decide whether it should be ONLINE or OFFLINE.
Good news is: I have adapted the AVM binding and successfully tested it.

Heiko_Fanieng · March 1, 2016, 3:41pm

Great News What is the delay between your changes in ESH the nightly builds at cloudless? I don’t want to continue testing if the update isn’t available for me …

Thanks to you and all other maintainer for your great job with OH2!

Kai · March 1, 2016, 3:59pm

The fix was on the binding, not in ESH.
It is contained in this openhab2-addons build, which triggered this distro build, which hence should contain the change.

Heiko_Fanieng · March 1, 2016, 4:50pm

Not shure i’ve got the right version of the AVM-binding ([147:org.openhab.binding.avmfritz:2.0.0.201603010202]) with fresh installed snapshot, but i got this error in the log when trying to switch the device:

17:41:57.443 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while calling handler: java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.NullPointerException
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)[:1.8.0_72]
	at java.util.concurrent.FutureTask.get(FutureTask.java:206)[:1.8.0_72]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:179)[89:org.eclipse.smarthome.core:0.8.0.201602251230]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:72)[89:org.eclipse.smarthome.core:0.8.0.201602251230]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:56)[89:org.eclipse.smarthome.core:0.8.0.201602251230]
	at org.eclipse.smarthome.core.thing.internal.ThingManager.receiveCommand(ThingManager.java:339)[95:org.eclipse.smarthome.core.thing:0.8.0.201602251230]
	at org.eclipse.smarthome.core.items.events.AbstractItemEventSubscriber.receive(AbstractItemEventSubscriber.java:46)[89:org.eclipse.smarthome.core:0.8.0.201602251230]
	at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:192)[89:org.eclipse.smarthome.core:0.8.0.201602251230]
	at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:1)[89:org.eclipse.smarthome.core:0.8.0.201602251230]
	at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:170)[89:org.eclipse.smarthome.core:0.8.0.201602251230]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_72]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_72]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_72]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_72]
Caused by: java.lang.NullPointerException
	at org.openhab.binding.avmfritz.handler.DeviceHandler.handleCommand(DeviceHandler.java:162)[147:org.openhab.binding.avmfritz:2.0.0.201603010202]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$2.call(ThingManager.java:342)[95:org.eclipse.smarthome.core.thing:0.8.0.201602251230]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$2.call(ThingManager.java:1)[95:org.eclipse.smarthome.core.thing:0.8.0.201602251230]
	... 5 more

Kai · March 1, 2016, 9:14pm

Well, this looks very much like the issue mentioned above, which is still open. I only fixed the “remains in INITIALIZING” bug so far…

Heiko_Fanieng · March 1, 2016, 9:35pm

I could confirm that FRITZ!DECT 200 devices are now schon as ONLINE in Paper UI as mentioned in the configuration above.

It could be helpful for beta-Tester to know on what functions it make sense to test it or not

Is it now a part of the binding i have to wait for a fix of robbyb67, who is present in the Issue-Tracker at GitHub and is not present in the forum here?

Kai · March 1, 2016, 10:26pm

Yeah, sorry, I would have loved to fix the NPE last night as well, but I couldn’t test, because my openHAB instance is running on the computer that is plugged into my FRITZ!DECT 200 - so testing it is a bad idea

It could be helpful for beta-Tester to know on what functions it make sense to test it or not

It makes sense to test everything for which there isn’t yet an open issue in the issue tracker!

Cheers,
Kai

peter54 · March 29, 2016, 6:11pm

Hello all,
i am a newbie with openhab. I installed the latest Cloudbees build #214.
i try to get my Fritz!Dect running, but it still remains in status INITIALIZING.

How can I configure the access to my fritz!box (Username and password)?

What about the bridge in the configuration?

Thank you for your help!

peter54 · May 4, 2016, 10:07am

Is there nobody working on this issue? I am really waiting for this binding working well! Thanks very much for your help!

janKG · July 3, 2016, 9:40pm

Just fyi: I submitted a pull request late last night that fixes the problem.

So it’s up to @Kai now I guess

Regards,
Jan

Kai · July 4, 2016, 6:33am

Merged, many thanks, @janKG!

janKG · July 4, 2016, 9:10am

You’re welcome, thanks for the fast merge!