Debug logging in OH3?

Hello, when I try to set log levels in OH3 to DEBUG the way I would in 2.5, I can’t see anything in the list for my bindings. Previously there were 3 or 4 for zigbee, a few for zwave, etc. Now I don’t see them.

The documentation page also just shows debug logging instructions for 2.5; is there anything for OH3 yet?

Reason for my logging need is that multiple brands of zigbee light bulbs won’t add to the system and just sit in unknown - discovery not completed. I had this issue in 2.5 and never resolved it. One weird thing is after upgrading to OH3, one brand of bulbs that previously would not discover (GE bulbs) now just work automatically, but my Sengled and Hue bulbs still won’t work.


The debug logging from the Karaf console has not changed.

When I do a log:list now, none of my bindings show up, whereas they previously did. What am I doing wrong?

1 Like

Not sure. I added the zigbee tag to get the help of @chris

1 Like

By default I don’t think any bindings are specifically added to the logging config. You must have added those yourself at some point and will need to add them again in OH 3

The logging docs have been updated for quite some time before OH 3 release.

Be sure to follow the links though. Pretty much everything about the loggers outside of identifying the logger name you want to modify the setting for is defined by the logger libraries.

If the example configs are not updated in the add-on readmes, please file an issue so they can be updated to the new XML format.

Yep now you’ve gotta be a rocket scientist to work out how to turn it on. Seriously the documentation is so damn poor. Provide some examples! The console displays SFA now. OH is just getting way too complex and over the top now.

Instead of complaining about poor documentation, why not try to contribute to make improvements?

BTW, it is not a good idea to double post your HABpanel questions in different posts.

I cant update it Hans if I dont know how to use it!

What exactly don‘t you know how to use?
Enable debug log for a certain binding?
This has been explained so many times in different post.
Open the condole by entering

openhab-cli console

After logging in enter

log:set DEBUG (or TRACE) org.openhab.binding.“bindingname“

I thought i’d look at log:get , one looked like it would do the trick - itemstatevent, so I set it to INFO


openhab> log:get
Logger │ Level
javax.jmdns │ ERROR
javax.mail │ ERROR
org.apache.karaf.jaas.modules.audit │ INFO
org.apache.karaf.kar.internal.KarServiceImpl │ ERROR │ ERROR │ OFF
org.apache.sshd │ ERROR
org.eclipse.lsp4j │ OFF
org.eclipse.smarthome │ INFO
org.jupnp │ ERROR
org.openhab │ INFO
org.openhab.binding.doorbird │ OFF │ OFF
org.openhab.ui.paper │ WARN
org.openhab.ui.paper.internal │ INFO
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime │ OFF
smarthome.event │ INFO
smarthome.event.InboxUpdatedEvent │ ERROR
smarthome.event.ItemAddedEvent │ ERROR
smarthome.event.ItemRemovedEvent │ ERROR
smarthome.event.ItemStateEvent │ INFO
smarthome.event.ThingAddedEvent │ ERROR
smarthome.event.ThingRemovedEvent │ ERROR
smarthome.event.ThingStatusInfoEvent │ INFO

Are you still on openHAB 2.x ?
openHAB 3 should not have any smarthome references in the log settings.

I’m on OH3.1. Funny isn’t it?

No, leftovers from upgrade.
Change the loggers to start with org.openhab…

Brand new server, not an upgrade

I had an issue after upgrading from 2.5 to 3.0 with the following:

The org.ops4j.pax.logging.cfg seemed to have not been upgraded to refer to log4j2.xml.

I manually edit the file and this seemed to resolve a lot of logging issues I had.

What is in your org.ops4j.pax.logging.cfg?

I changed mine and all it has now is:


I will check this evening, when getting access to my server…

Hm, strange, as your logging config still shows entries for paperUI or smarthome bundles.
Shure you did not restore any openHAB 2.x configs ?
I checked with my configs, clearly showing no smarthome bundles, those are openHAB bundles now. You can start to manually reconfigure those with log:set command and then remove the old entries with log: remove…

Yes I did a openhab restore, but you asked if it was an upgrade - its not an upgrade.

thanks ill do that now

No worries, my question was not clear in that respect…:wink:

1 Like

No problem. Am i right in saying that this log will create the on/off events?

org.openhab                                        │ INFO

As its on, but I dont see them