2.5 Milestone 5 Issues

Setup, Configuration and Use Installation
,
10

Since switching to milestone 5 on my rapsberry p3, I’m having an issue with mqtt.

I use zigbee2mqtt. As far as I can tell everything works perfectly, execpt mqtt topics that I defined in my things file as command channels (postCommand=“true”). When a message is received for those topics, the mqtt binding seems to send the command to the item 4 times. None command channels work as expected.

For example, I have the thing “Zigbee button daytime set”. The click channel is a command channel (postCommand=“true”)

Thing mqtt:topic:marksbroker:zigbeeButtonDaytimeSet "Zigbee button daytime set" (mqtt:broker:marksbroker){
Channels:
Type string : click		"Click"			[ stateTopic="zigbee2mqtt/zigbee button daytime set", transformationPattern="JS:getZigbeeClick.js", postCommand="true" ]
Type number : voltage		"Voltage"		[ stateTopic="zigbee2mqtt/zigbee button daytime set", transformationPattern="JSONPATH:$.voltage" ]
Type number : battery		"Battery"		[ stateTopic="zigbee2mqtt/zigbee button daytime set", transformationPattern="JSONPATH:$.battery" ]
Type number : linkquality	"Linkquality"		[ stateTopic="zigbee2mqtt/zigbee button daytime set", transformationPattern="JSONPATH:$.linkquality" ]

}

I have an item linked to the click channel

String ZigbeeSwitch_DaytimeSet_Click        			"Daytime button Click [%s]"					{ channel="mqtt:topic:marksbroker:zigbeeButtonDaytimeSet:click" }

If I click the button, zigbee2mqtt sends the mqtt message:

Nov 18 00:13:28 openHABianPi npm[25167]: zigbee2mqtt:info 2019-11-17T23:13:28: MQTT publish: topic ‘zigbee2mqtt/zigbee button daytime set’, payload ‘{“linkquality”:21,“battery”:100,“voltage”:3045,“click”:“single”}’

It sends it 1 time. However, this results in:

2019-11-18 00:13:28.091 [ome.event.ItemCommandEvent] - Item ‘ZigbeeSwitch_DaytimeSet_Click’ received command single
2019-11-18 00:13:28.104 [ome.event.ItemCommandEvent] - Item ‘ZigbeeSwitch_DaytimeSet_Click’ received command single
2019-11-18 00:13:28.113 [ome.event.ItemCommandEvent] - Item ‘ZigbeeSwitch_DaytimeSet_Click’ received command single
2019-11-18 00:13:28.125 [ome.event.ItemCommandEvent] - Item ‘ZigbeeSwitch_DaytimeSet_Click’ received command single
2019-11-18 00:13:28.131 [nt.ItemStatePredictedEvent] - ZigbeeSwitch_DaytimeSet_Click predicted to become single
2019-11-18 00:13:28.158 [nt.ItemStatePredictedEvent] - ZigbeeSwitch_DaytimeSet_Click predicted to become single
2019-11-18 00:13:28.172 [nt.ItemStatePredictedEvent] - ZigbeeSwitch_DaytimeSet_Click predicted to become single
2019-11-18 00:13:28.207 [nt.ItemStatePredictedEvent] - ZigbeeSwitch_DaytimeSet_Click predicted to become single

11

I have a rollershutter item group that was used to open all rollershutters in the morning. now with M5 it doesnt work anymore. did something change, or is it a bug?

log

2019-11-18 07:00:02.270 [WARN ] [rthome.model.script.actions.BusEvent] - Cannot convert ‘UP’ to a command type which item ‘gRollos’ accepts: .

item

Group:Rollershutter gRollos “Rollladen”

rule

gRollos.sendCommand(“UP”)

12

Update: after clearing the cache, openHAB refuses to start:

2019-11-18 09:27:33.254 [SEVERE] [org.apache.karaf.main.Main] - Could not launch framework
java.lang.RuntimeException: Error installing bundle listed in startup.properties with url: mvn:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.6 and startlevel: 1
	at org.apache.karaf.main.Main.installAndStartBundles(Main.java:570)
	at org.apache.karaf.main.Main.launch(Main.java:273)
	at org.apache.karaf.main.Main.main(Main.java:178)
Caused by: java.lang.RuntimeException: Could not resolve mvn:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.6
	at org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
	at org.apache.karaf.main.Main.installAndStartBundles(Main.java:562)
	... 2 more

I suppose all I can do now, is reinstall openHAB2…

13

Did you use the official update script? If not, how did you upgrade? That exception is odd, since Karaf was recently updated to 4.2.7.

14

I updated the package with:

$ sudo apt update
$ sudo apt upgrade
1 Like
15

4 posts were split to a new topic: Console access issues in M5

16

After the upgrade of 1736 to 1759
When sending commands through a MQTT, I get the following warnings:

2019-11-18 17:57:24.185 [WARN ] [qtt.generic.AbstractMQTTThingHandler] - Channel mqtt:topic:g_mqtt:box_heater_ir_things:state is a read-only channel, ignoring command ON
2019-11-18 17:57:25.450 [WARN ] [qtt.generic.AbstractMQTTThingHandler] - Channel mqtt:topic:g_mqtt:box_heater_ir_things:state is a read-only channel, ignoring command OFF

Did I miss something?

17
  1. You are running a snapshot and posted in a Milestone thread.
  2. Snapshot errors are posted as issues on GitHub, not in the community forum. Many developers working on the snapshots do not use the community forum.
18

Have you tried removing the quotes in the command? Just a quick idea.

19

then I get:

2019-11-18 12:41:09.252 [WARN ] [lipse.smarthome.core.items.GroupItem] - Command ‘DOWN’ has been ignored for group ‘gRollos’ as it is not accepted.

21

It you had any manually installed addons they should have been removed before upgrading.

22

New issue here.
Saving/Updating files (rules, items. sitemap…) doesn’t create a new log line in the openhab.log file

1 Like
23

I did fail to upgrade from M4 to M5. Running on MS2012R2 using “update.bat 2.5.0.M5”

PrintAndReturn : 2.5.0.M4 is not formatted correctly (d.d.d)

After changing my current version.properties from 2.5.0.M4 to 2.5.0 i was able to get the script running to completion.

I still do have to delete mqttembedded.bin on every restart to get the embedded broker running.
If mqttembedded.bin is not deleted i get “persistence corrupt: Could not deserialize” and no MQTT in openhab, but everything else works!

No MQTT
Zulu CPU usage 0-1%

2.5.0.M4 MQTT embedded broker running:
Zulu CPU Usage 28-36% constant

2.5.0.M5 MQTT embedded broker running:
Zulu CPU usage: 75-79% constant

Zulu 8.42.0.23-CA-win64

Any ideas to narrow down the root cause?

24

ah oh… that problem was supposed to be fixed just after M3 got released. Here is link to git issue
https://github.com/openhab/openhab2-addons/issues/5527
and here is link to thread with work around

25

Thanks, changing the file location in PaperUI fixed my restart problems. Despite having write access to the new path no mqttembedded.bin is created at the new location. So same effect as deleting it on every restart.

I did just switch from Zulu 8.42.0.23-CA-win64 to Java SE 1.8.0_231-b11 witch brought my CPU usage down to 50-53%(from ~75%)
M4 was ~30%
no MQTT embedded broker running was and is 0-1%

26

Running openHABian on an RPi3.

I ran across something interesting when I upgraded 2.5-M4 to 2.5-M5 through openhabian-config. All my zwave devices stopped working. After looking at the logs it appeared that the Controller ( Aeotec Z-Stick Gen5) kept going offline and then coming back online and repeat over and over. I looked through the zwave logs and nothing jumped out at me. I was not sure what to do so I set that problem aside.

I was getting another error in the logs:
Failed installing 'openhab-misc-restdocs'

I set off to solve that problem and it seems to be a relatively simple fix. The “restdocs” was moved from “misc” to “ui” in the addons.config. Since I setup those addons via PaperUI, I check out the “userdata/config/org/openhab/addons.confg” file. This is what the “misc” line looked like:

misc=",openhabcloud,restdocs"

I had a leading comma plus the restdocs now in the wrong place. I removed the comma and the restdocs and then restarted openHAB.

To my surprise, all the zwave issues disappeared. No more Zwave controller bouncing online/offline. All zwave activities back to normal.

I did some more testing just see if I want would happen.

Leading comma with no restdocs
misc=",openhabcloud"

No zwave controller bouncing, but the zwave network does not appear to respond to commands. The logs indicate that the Lights were changed to ON but the lights never turn on.

No leading comma with restdocs
misc="openhabcloud, restdocs"

Z-wave controller constantly bouncing.

I can only assume the leading comma got in the file do to adding/removing something from the PaperUI. Not sure when that actually happened.

As for the no longer valid “restdocs” in the “misc” category… not sure where to file and issue… is it a zwave issue? or somewhere else?

27

the REST Docs moved to User Interfaces back at Milestone 2. You need to remove the reverence to the old docs & install from the new location.

Here is the Warning yuou received when upgrading.

Warning: REST Docs: This add-on is now part of the UIs. When installing it using textual configuration, update ‘services/addons.cfg’ by removing ‘restdocs’ from ‘misc’ and add it to ‘ui’ instead.

28

Yikes!
so are you saying that shutting down the embedded mqtt server (moquette) makes cpu usage drop from 50% down to 0-1% ?
If so that is not good, David mentioned awhile back (when this first popped up) that there were some bug fixes the moquette guys were working on
Anyhow seems fix for the persistence file is not working correctly… @J-N-K Jan can you take another look at this?

29

Migration of my RB4 from 2.5 m4 to m5 solved my problem on mqtt binding. Now i can restart openhab and the binding go online normally. At any restart I lose the status of all my mqtt object (I don’t know if it’s normal). Actually I did’t look at the cpu status. I’ll investigate this night. Thank you for all

30

Do you have any persistence set up? If not that is the issue, likely.