Hi Thomas,
pls. think on state's of push button switches, if you update all states by an reconnect you get a false state from ccu and all rules where triggered. Here helps only a internal switch variable to detect the reconnect and inhibit this rules for a little time. The same problem as on startup.
Regards
Falk
--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/groups/opt_out.
ccu.getConnection().init("", "" + ccu.getConnection().hashCode());
ccu.getConnection().init("http://" + callbackHost + ":" + callbackPort + "/xmlrpc", "" + ccu.getConnection().hashCode());
solves the initial disconnection issue too. I don't know whether this has any drawbacks.
2. Your ccu.getConnection().isAlife()did not discover the disconnection in my tests. The call returns true even if the CCU2 has stopped sending events to our callback XmlRpcServer. So I tried the following: store the timestamp of each call to the CCURF.event() method
and compare it to the current timestamp in HomematicBinding.execute(). If timestamps differ for more than 5 minutes --> perform reconnection. This works for me for about 24 hours now.
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/F02sSMcEk0M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.