I getting continual repeated messages in the logs that I never got before the upgrade
2017-12-19 12:50:13.040 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:5’ has been updated.
2017-12-19 12:50:20.391 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:5’ has been updated.
2017-12-19 12:50:41.410 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:4’ has been updated.
2017-12-19 12:52:33.468 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:5’ has been updated.
2017-12-19 13:00:12.216 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:5’ has been updated.
2017-12-19 13:01:25.941 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:4’ has been updated.
2017-12-19 13:02:33.788 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:5’ has been updated.
2017-12-19 13:05:32.673 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:4’ has been updated.
2017-12-19 13:07:33.868 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:5’ has been updated.
2017-12-19 13:10:38.100 [me.event.ThingUpdatedEvent] - Thing ‘zway:zwayDevice:192_168_1_210:5’ has been updated.
I also get continously repeated messages in the logs.
2017-12-21 22:36:15.085 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
2017-12-21 22:36:20.089 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
2017-12-21 22:36:25.092 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
2017-12-21 22:36:30.094 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
2017-12-21 22:36:35.095 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
2017-12-21 22:36:40.099 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
2017-12-21 22:36:45.101 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
2017-12-21 22:36:50.104 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
2017-12-21 22:36:55.107 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
2017-12-21 22:37:00.109 [me.event.ThingUpdatedEvent] - Thing ‘milight:bridgeV6:iBoxLED’ has been updated.
Nope…not yet. Its still a open issue for me. But “good” to hear, that i am not alone. This means, there is a reproducable issue connected to German language-settings…so there is at least hope for a solution.
I posted this in another topic earlier. Hope it helps.
I ran this in karaf. This was right after I updated to 2.2. I’m no computer wiz so I’m not sure what negative effects this would have but it stopped the flood of milight updates in the log.
A bigger issue with this that I recently noticed is that every ThingUpdatedEvent corresponds to a write to /var/lib/openhab2/jsondb/org.eclipse.smarthome.core.thing.Thing.json and every time that file is written to, OpenHAB creates a backup of the file. This means that the backups are useless, since the oldest one is from just a few minutes ago…
By the looks of the subject of this thread I have the same problem, so followed all suggestions but still can not get it to work. One thing which looks different from what was described above is the output from “openhab-cli start --debug”, after some time I get the following message (of which I do not know if it is related)
openhab> 21:30:22.433 [Start Level: Equinox Container: e8809b83-5429-4dc5-9644-7e56583d83df] ERROR org.openhab.ui.dashboard - [org.openhab.dashboard(20)] The activate method has thrown an exception
java.lang.IllegalArgumentException: Network prefix length is not within bounds
at org.eclipse.smarthome.core.net.NetUtil.networkPrefixLengthToNetmask(NetUtil.java:251) [109:org.eclipse.smarthome.core:0.10.0.b1]
at org.eclipse.smarthome.core.net.NetUtil.getIpv4NetAddress(NetUtil.java:289) [109:org.eclipse.smarthome.core:0.10.0.b1]
at org.eclipse.smarthome.core.net.NetUtil.getIPv4inSubnet(NetUtil.java:326) [109:org.eclipse.smarthome.core:0.10.0.b1]
at org.eclipse.smarthome.core.net.NetUtil.getPrimaryIpv4HostAddress(NetUtil.java:79) [109:org.eclipse.smarthome.core:0.10.0.b1]
at org.openhab.ui.dashboard.internal.DashboardService.activate(DashboardService.java:83) [189:org.openhab.ui.dashboard:2.2.0]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
.....
[Start Level: Equinox Container: 5f334267-7d3b-4ceb-b5b4-f01e09fde248] ERROR org.openhab.ui.dashboard.internal.DashboardService - Error during dashboard startup: alias: '/start/index' is already in use in this or another context
When accessing OpenHab2 via the browser I get a internal server error
java.lang.NullPointerException
at org.openhab.ui.dashboard.internal.DashboardService.getLocalizedText(DashboardService.java:240)
But I am able to access the PaperUI.
Last thing I did was try to install OwnTracks and because the binding did not show up in the list with binding after I hit the install button, I restarted openHab2 and ended up in this situation (log files are empty by the way… )
Any clue as to what may be causing this?
Well no really, in the end I backed up my configuration and reinstalled OpenHAB. The I put back my configuration but this caused OpenHAB to not work (looked it didn’t recognise some of the config files) and I redid my configuration … and now it is working again