Unable to set log level through console

All,

I have some issues with a zigbee device, so I wanted to set the log levels to debug as per best-practice

openhabian@openhabHost:~ $ ssh -p 8101 openhab@localhost
Password authentication
Password: 

                           _   _     _     ____  
   ___   ___   ___   ___  | | | |   / \   | __ ) 
  / _ \ / _ \ / _ \ / _ \ | |_| |  / _ \  |  _ \ 
 | (_) | (_) |  __/| | | ||  _  | / ___ \ | |_) )
  \___/|  __/ \___/|_| |_||_| |_|/_/   \_\|____/ 
       |_|       3.3.0 - Release Build

Use '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
To exit, use '<ctrl-d>' or 'logout'.

openhab> log:set debug org.openhab.binding.zigbee                                                                           
Error executing command: Unable to set level for logger
openhab>                                                               

It seems the file has got the right permissions

openhabian@openhabHost:~ $ ls -ltr /var/lib/openhab/etc/log4j2.xml
-rw-r--r-- 1 openhab openhab 6278 Oct 30 18:13 /var/lib/openhab/etc/log4j2.xml

Any idea? Am I missing something obvious?

Thanks!
Max

Please try with uppercase DEBUG

Thanks for the prompt feedback

Like this?

openhab> log:set DEBUG org.openhab.binding.zigbee
Error executing command: Unable to set level for logger

:sob:

Yes, strange, never saw such an error.

Take a look at this.

Thanks, unfortunately it seems everything in the right form - I have added both conf files, perhaps somebody could spot some inconsistencies.

Thanks
Max

openhabian@openhabHost:~ $ ls -ltr /var/lib/openhab/etc/org.ops4j.pax.logging.cfg
-rw-r--r-- 1 openhab openhab 65 Oct 30 20:27 /var/lib/openhab/etc/org.ops4j.pax.logging.cfg
openhabian@openhabHost:~ $ cat /var/lib/openhab/etc/org.ops4j.pax.logging.cfg 
org.ops4j.pax.logging.log4j2.config.file=${karaf.etc}/log4j2.xml
openhabian@openhabHost:~ $ ls -ltr /var/lib/openhab/etc/log4j2.xml
-rw-r--r-- 1 openhab openhab 6278 Oct 30 20:27 /var/lib/openhab/etc/log4j2.xml
openhabian@openhabHost:~ $ cat /var/lib/openhab/etc/log4j2.xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?><Configuration monitorInterval="10">

	<Appenders>
		<!-- Console appender not used by default (see Root logger AppenderRefs) -->
		<Console name="STDOUT">
			<PatternLayout pattern="%d{HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n"/>
		</Console>

		<!-- Rolling file appender -->
		<RollingFile fileName="${sys:openhab.logdir}/openhab.log" filePattern="${sys:openhab.logdir}/openhab.log.%i.gz" name="LOGFILE">
			<PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n"/>
			<Policies>
				<OnStartupTriggeringPolicy/>
				<SizeBasedTriggeringPolicy size="16 MB"/>
			</Policies>
			<DefaultRolloverStrategy max="7"/>
		</RollingFile>

		<!-- Event log appender -->
		<RollingRandomAccessFile fileName="${sys:openhab.logdir}/events.log" filePattern="${sys:openhab.logdir}/events.log.%i.gz" name="EVENT">
			<PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n"/>
			<Policies>
				<OnStartupTriggeringPolicy/>
				<SizeBasedTriggeringPolicy size="16 MB"/>
			</Policies>
			<DefaultRolloverStrategy max="7"/>
		</RollingRandomAccessFile>

		<!-- Audit file appender -->
		<RollingRandomAccessFile fileName="${sys:openhab.logdir}/audit.log" filePattern="${sys:openhab.logdir}/audit.log.%i.gz" name="AUDIT">
			<PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n"/>
			<Policies>
				<OnStartupTriggeringPolicy/>
				<SizeBasedTriggeringPolicy size="8 MB"/>
			</Policies>
			<DefaultRolloverStrategy max="7"/>
		</RollingRandomAccessFile>

		<!-- OSGi appender -->
		<PaxOsgi filter="*" name="OSGI"/>

		<!-- Zwave custom file appender -->
		<RollingRandomAccessFile fileName="${sys:openhab.logdir}/zwave.log" filePattern="${sys:openhab.logdir}/zwave.log.%i" name="ZWAVE">
			<PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n"/>
				<Policies>
					<OnStartupTriggeringPolicy/>
					<SizeBasedTriggeringPolicy size="16 MB"/>
				</Policies>
		</RollingRandomAccessFile>
	</Appenders>

	<Loggers>

		<!-- Root logger configuration -->
		<Root level="WARN">
			<AppenderRef ref="LOGFILE"/>
			<AppenderRef ref="OSGI"/>
		</Root>

		<!-- Karaf Shell logger -->
		<Logger level="OFF" name="org.apache.karaf.shell.support">
			<AppenderRef ref="STDOUT"/>
		</Logger>

		<!-- Security audit logger -->
		<Logger additivity="false" level="INFO" name="org.apache.karaf.jaas.modules.audit">
			<AppenderRef ref="AUDIT"/>
		</Logger>

		<!-- openHAB specific logger configuration -->

		<Logger level="INFO" name="org.openhab"/>

		<Logger level="ERROR" name="openhab.event.ItemStateEvent"/>
		<Logger level="ERROR" name="openhab.event.ItemAddedEvent"/>
		<Logger level="ERROR" name="openhab.event.ItemRemovedEvent"/>
		<Logger level="ERROR" name="openhab.event.ItemChannelLinkAddedEvent"/>
		<Logger level="ERROR" name="openhab.event.ItemChannelLinkRemovedEvent"/>
		<Logger level="ERROR" name="openhab.event.ChannelDescriptionChangedEvent"/>
		<Logger level="ERROR" name="openhab.event.ThingStatusInfoEvent"/>
		<Logger level="ERROR" name="openhab.event.ThingAddedEvent"/>
		<Logger level="ERROR" name="openhab.event.ThingUpdatedEvent"/>
		<Logger level="ERROR" name="openhab.event.ThingRemovedEvent"/>
		<Logger level="ERROR" name="openhab.event.InboxUpdatedEvent"/>
		<Logger level="ERROR" name="openhab.event.RuleStatusInfoEvent"/>
		<Logger level="ERROR" name="openhab.event.RuleAddedEvent"/>
		<Logger level="ERROR" name="openhab.event.RuleRemovedEvent"/>
		<Logger level="ERROR" name="openhab.event.StartlevelEvent"/>
		<Logger level="ERROR" name="openhab.event.AddonEvent"/>

		<Logger additivity="false" level="INFO" name="openhab.event">
			<AppenderRef ref="EVENT"/>
			<AppenderRef ref="OSGI"/>
		</Logger>

		<!-- openHAB user based script logger configuration -->
		<Logger level="TRACE" name="org.openhab.automation.script"/>

		<Logger level="ERROR" name="javax.jmdns"/>
		<Logger level="ERROR" name="org.jupnp"/>

		<!-- This suppresses all Maven download issues from the log when doing feature installations -->
		<!-- as we are logging errors ourselves in a nicer way anyhow. -->
		<Logger level="ERROR" name="org.ops4j.pax.url.mvn.internal.AetherBasedResolver"/>

		<!-- Filters known issues of pax-web (issue link to be added here). -->
		<!-- Can be removed once the issues are resolved in an upcoming version. -->
		<Logger level="OFF" name="org.ops4j.pax.web.pax-web-runtime"/>

		<!-- Filters known issues of lsp4j, see -->
		<!-- https://github.com/eclipse/smarthome/issues/4639 -->
		<!-- https://github.com/eclipse/smarthome/issues/4629 -->
		<!-- https://github.com/eclipse/smarthome/issues/4643 -->
		<!-- Can be removed once the issues are resolved in an upcoming version. -->
		<Logger level="OFF" name="org.eclipse.lsp4j"/>

		<!-- Filters warnings for events that could not be delivered to a disconnected client. -->
		<Logger level="ERROR" name="org.apache.cxf.jaxrs.sse.SseEventSinkImpl"/>

		<!-- Filters known issues of KarServiceImpl, see -->
		<!-- https://github.com/openhab/openhab-distro/issues/519#issuecomment-351944506 -->
		<!-- Can be removed once the issues are resolved in an upcoming version. -->
		<Logger level="ERROR" name="org.apache.karaf.kar.internal.KarServiceImpl"/>

		<!-- Filters warnings about unavailable ciphers when JCE is not installed, see -->
		<!-- https://github.com/openhab/openhab-distro/issues/999 -->
		<Logger level="ERROR" name="org.apache.karaf.shell.ssh.SshUtils"/>

		<!-- Filters known issues of javax.mail, see -->
		<!-- https://github.com/openhab/openhab-addons/issues/5530 -->
		<Logger level="ERROR" name="javax.mail"/>

		<!-- Filters disconnection warnings of the ChromeCast Java API, see -->
		<!-- https://github.com/openhab/openhab-addons/issues/3770 -->
		<Logger level="ERROR" name="su.litvak.chromecast.api.v2.Channel"/>

		<!-- Added by Karaf to prevent debug logging loops, see -->
		<!-- https://issues.apache.org/jira/browse/KARAF-5559 -->
		<Logger level="WARN" name="org.apache.sshd"/>
		<!-- Logger level="DEBUG" name="org.openhab.binding.zwave"/ -->

		<!-- Zwave custom logger -->
		<Logger additivity="false" level="INFO" name="org.openhab.binding.zwave">
			<AppenderRef ref="ZWAVE"/>
		</Logger>

	</Loggers>

</Configuration>

What happens if you enter:

log:list | grep -i zigbee

Edit: Just another idea(silly question). Is the binding installed ?

openhab> bundle:list -s | grep -i binding
160 x Active x  80 x 3.4.0.M3               x org.openhab.core.binding.xml
253 x Active x  80 x 3.4.0.M3               x org.openhab.binding.amazonechocontrol
254 x Active x  80 x 3.4.0.M3               x org.openhab.binding.astro
255 x Active x  80 x 3.4.0.M3               x org.openhab.binding.avmfritz
256 x Active x  80 x 3.4.0.M3               x org.openhab.binding.exec
257 x Active x  80 x 3.4.0.M3               x org.openhab.binding.homematic
258 x Active x  80 x 3.4.0.M3               x org.openhab.binding.http
259 x Acti

I had the same issue with OH 3.3 release and the Netatmo binding. My β€œcure” was to create an entry in the log4j.xml for the binding.
After that was done, I was able to switch log-levels via the console.

I did not investigate further, unfortunately. One similarity I could think of is that I also have an additional appender to log an unrelated item.

Interesting

openhab> log:list | grep -i zigbee                                                                                            
openhab>                                 

while the binding is installed (I have a few zigbee devices installed and working)

openhab> bundle:list -s | grep -i binding                                                                                     
159 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.core.binding.xml
267 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.astro
268 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.avmfritz
269 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.chromecast
270 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.exec
271 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.icloud
272 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.kodi
273 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.mpd
274 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.mqtt
275 β”‚ Active β”‚  81 β”‚ 3.3.0                  β”‚ org.openhab.binding.mqtt.espmilighthub
276 β”‚ Active β”‚  81 β”‚ 3.3.0                  β”‚ org.openhab.binding.mqtt.generic
277 β”‚ Active β”‚  82 β”‚ 3.3.0                  β”‚ org.openhab.binding.mqtt.homeassistant
278 β”‚ Active β”‚  82 β”‚ 3.3.0                  β”‚ org.openhab.binding.mqtt.homie
279 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.network
280 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.telegram
281 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.tradfri
282 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.wled
283 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zigbee
284 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zigbee.cc2531
285 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zigbee.console
286 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zigbee.console.ember
287 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zigbee.console.telegesis
288 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zigbee.ember
289 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zigbee.serial
290 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zigbee.telegesis
291 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zigbee.xbee
292 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.zwave
openhab>                                                                                

Does this bing us further in the troubleshooting?

Max

Ok, I will keep this in mind. I would love to avoid manual interventions :wink:

Let’s wait for @fibu-freak’s opinion on my command output.

Max

Sorry, but I thought, that it could be possible that the bundle is not installed. But as one can see, there is a lot stuff in.

But if you make a log:list | grep -i zigbee nothing is shown. Are all the other bindings in your log:list , and are their levels changeable

openhab> log:list
Logger                                             β”‚ Level
───────────────────────────────────────────────────┼──────
ROOT                                               β”‚ WARN
javax.jmdns                                        β”‚ ERROR
javax.mail                                         β”‚ ERROR
openhab.event                                      β”‚ WARN
openhab.event.AddonEvent                           β”‚ ERROR
openhab.event.ChannelDescriptionChangedEvent       β”‚ ERROR
openhab.event.InboxUpdatedEvent                    β”‚ ERROR
openhab.event.ItemAddedEvent                       β”‚ ERROR
openhab.event.ItemChannelLinkAddedEvent            β”‚ ERROR
openhab.event.ItemChannelLinkRemovedEvent          β”‚ ERROR
openhab.event.ItemRemovedEvent                     β”‚ ERROR
openhab.event.ItemStateEvent                       β”‚ ERROR
openhab.event.RuleAddedEvent                       β”‚ ERROR
openhab.event.RuleRemovedEvent                     β”‚ ERROR
openhab.event.RuleStatusInfoEvent                  β”‚ ERROR
openhab.event.StartlevelEvent                      β”‚ ERROR
openhab.event.ThingAddedEvent                      β”‚ ERROR
openhab.event.ThingRemovedEvent                    β”‚ ERROR
openhab.event.ThingStatusInfoEvent                 β”‚ ERROR
openhab.event.ThingUpdatedEvent                    β”‚ ERROR
org.apache.cxf.jaxrs.sse.SseEventSinkImpl          β”‚ ERROR
org.apache.karaf.jaas.modules.audit                β”‚ INFO
org.apache.karaf.kar.internal.KarServiceImpl       β”‚ ERROR
org.apache.karaf.shell.ssh.SshUtils                β”‚ ERROR
org.apache.karaf.shell.support                     β”‚ OFF
org.apache.sshd                                    β”‚ WARN
org.eclipse.lsp4j                                  β”‚ OFF
org.jupnp                                          β”‚ ERROR
org.openhab                                        β”‚ INFO
org.openhab.binding.amazonechocontrol              β”‚ ERROR
org.openhab.binding.homematic                      β”‚ ERROR
org.ops4j.pax.url.mvn.internal.AetherBasedResolver β”‚ ERROR
org.ops4j.pax.web.pax-web-runtime                  β”‚ OFF
su.litvak.chromecast.api.v2.Channel                β”‚ ERROR
openhab>

As you can see in my snippet of my bundle-list there is a bundle for the avmfritz binding but not so in my log-list.
And i tried:

openhab> bundle:list -s | grep -i avm
255 x Active x  80 x 3.4.0.M3               x org.openhab.binding.avmfritz
openhab> log:list | grep -i org.openhab.binding.avmfritz
openhab>

openhab> log:set error org.openhab.binding.avmfritz
openhab> log:list | grep -i org.openhab.binding.avmfritz
org.openhab.binding.avmfritz                       x ERROR

openhab> log:set debug org.openhab.binding.avmfritz
openhab> log:list | grep -i org.openhab.binding.avmfritz
org.openhab.binding.avmfritz                       x DEBUG
openhab>

And the result in frontail is a lot of this:

2022-11-01 22:56:31.087 [DEBUG] [al.handler.AVMFritzBaseBridgeHandler] - Poll FRITZ!Box for updates avmfritz:fritzbox:7490
2022-11-01 22:56:31.690 [DEBUG] [nal.hardware.FritzAhaContentExchange] - HTTP response: 200
2022-11-01 22:56:31.691 [DEBUG] [nal.hardware.FritzAhaContentExchange] - HTTP response: 200
2022-11-01 22:56:31.693 [DEBUG] [nal.hardware.FritzAhaContentExchange] - GET response complete: <devicelist version="1" fwversion="7.29"><device identifier="11960 1003400" id="17" functionbitmask="320" fwversion="03.54" manufacturer="AVM" productname="Comet DECT"><present>1</present><txbusy>0</txbusy><name>Comet DECT #1 Arbeitszimmer</name><battery>50</battery><batterylow>0</batterylow><temperature>

Edit: Maybe you can try it with your AVM-Binding too ??!!

1 Like

as the file has the right permissions - does your openhab java process run with permissions of openhab ?
That of course should be the case but it would be an explanation that files could not be written.

1 Like

Apologize, @fibu-freak, quite busy days.

I have now tried what you suggested and what I see is different

openhab> bundle:list -s | grep -i avm                                                                                                                         
268 β”‚ Active β”‚  80 β”‚ 3.3.0                  β”‚ org.openhab.binding.avmfritz
openhab> log:list | grep -i org.openhab.binding.avmfritz                                                                                                      
openhab> log:set error org.openhab.binding.avmfritz                                                                                                           
Error executing command: Unable to set level for logger
openhab>                                                         

So, it seems there is a general issue with the logging!

Max

Hi @Wolfgang_S

I would say yes

openhabian@openhabHost:~ $ ps -ef | grep java
openhab    714     1  3 Oct30 ?        09:48:43 /usr/bin/java -XX:-UsePerfData -Dopenhab.home=/usr/share/openhab -Dopenhab.conf=/etc/openhab -Dopenhab.runtime=/usr/share/openhab/runtime -Dopenhab.userdata=/var/lib/openhab -Dopenhab.logdir=/var/log/openhab -Dfelix.cm.dir=/var/lib/openhab/config -Djava.library.path=/var/lib/openhab/tmp/lib -Djetty.host=0.0.0.0 -Djetty.http.compliance=RFC2616 -Dnashorn.args=--no-deprecation-warning -Dorg.apache.cxf.osgi.http.transport.disable=true -Dorg.ops4j.pax.web.listening.addresses=0.0.0.0 -Dorg.osgi.service.http.port=8080 -Dorg.osgi.service.http.port.secure=8443 -Djava.awt.headless=true -Dfile.encoding=UTF-8 -XX:+ExitOnOutOfMemoryError --add-reads=java.xml=java.logging --add-exports=java.base/org.apache.karaf.specs.locator=java.xml,ALL-UNNAMED --patch-module java.base=/usr/share/openhab/runtime/lib/endorsed/org.apache.karaf.specs.locator-4.3.7.jar --patch-module java.xml=/usr/share/openhab/runtime/lib/endorsed/org.apache.karaf.specs.java.xml-4.3.7.jar --add-opens java.base/java.security=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.naming/javax.naming.spi=ALL-UNNAMED --add-opens java.rmi/sun.rmi.transport.tcp=ALL-UNNAMED --add-opens java.base/java.io=ALL-UNNAMED --add-opens java.base/java.lang.reflect=ALL-UNNAMED --add-opens java.base/java.text=ALL-UNNAMED --add-opens java.base/java.time=ALL-UNNAMED --add-opens java.desktop/java.awt.font=ALL-UNNAMED --add-exports=java.base/sun.net.www.protocol.file=ALL-UNNAMED --add-exports=java.base/sun.net.www.protocol.ftp=ALL-UNNAMED --add-exports=java.base/sun.net.www.protocol.http=ALL-UNNAMED --add-exports=java.base/sun.net.www.protocol.https=ALL-UNNAMED --add-exports=java.base/sun.net.www.protocol.jar=ALL-UNNAMED --add-exports=java.base/sun.net.www.content.text=ALL-UNNAMED --add-exports=jdk.xml.dom/org.w3c.dom.html=ALL-UNNAMED --add-exports=jdk.naming.rmi/com.sun.jndi.url.rmi=ALL-UNNAMED --add-exports=java.rmi/sun.rmi.registry=ALL-UNNAMED --add-exports=java.security.sasl/com.sun.security.sasl=ALL-UNNAMED -Dkaraf.instances=/var/lib/openhab/tmp/instances -Dkaraf.home=/usr/share/openhab/runtime -Dkaraf.base=/var/lib/openhab -Dkaraf.data=/var/lib/openhab -Dkaraf.etc=/var/lib/openhab/etc -Dkaraf.log=/var/log/openhab -Dkaraf.restart.jvm.supported=true -Djava.io.tmpdir=/var/lib/openhab/tmp -Djava.util.logging.config.file=/var/lib/openhab/etc/java.util.logging.properties -Dkaraf.startLocalConsole=false -Dkaraf.startRemoteShell=true -classpath /usr/share/openhab/runtime/lib/boot/org.apache.karaf.diagnostic.boot-4.3.7.jar:/usr/share/openhab/runtime/lib/boot/org.apache.karaf.jaas.boot-4.3.7.jar:/usr/share/openhab/runtime/lib/boot/org.apache.karaf.main-4.3.7.jar:/usr/share/openhab/runtime/lib/boot/org.apache.karaf.specs.activator-4.3.7.jar:/usr/share/openhab/runtime/lib/boot/osgi.core-7.0.0.jar:/usr/share/openhab/runtime/lib/jdk9plus/istack-commons-runtime-3.0.10.jar:/usr/share/openhab/runtime/lib/jdk9plus/jakarta.xml.bind-api-2.3.3.jar:/usr/share/openhab/runtime/lib/jdk9plus/javax.annotation-api-1.3.2.jar:/usr/share/openhab/runtime/lib/jdk9plus/jaxb-runtime-2.3.3.jar:/usr/share/openhab/runtime/lib/jdk9plus/org.apache.servicemix.specs.activation-api-1.2.1-1.2.1_3.jar:/usr/share/openhab/runtime/lib/jdk9plus/txw2-2.3.3.jar org.apache.karaf.main.Main

I don’t know whether it’s stupid or if it helps what I propose, but have you ever tried

sudo openhab-cli reset-ownership

in the shell-console ?

Cheers,
Peter

@fibu-freak

no, I never did it. Unfortunately it does not solve the issue :frowning:

Thanks anyway!
Max

openhabian@openhabHost:~ $ sudo openhab-cli reset-ownership
[sudo] password for openhabian: 

This command gives openHAB control of its own directories.
May resolve permission errors during startup or configuration.
openHAB directories will be owned by openhab:openhab

Okay to Continue? [y/N]: y
openhabian@openhabHost:~ $ ssh -p 8101 openhab@localhost
Password authentication
Password: 

                           _   _     _     ____  
   ___   ___   ___   ___  | | | |   / \   | __ ) 
  / _ \ / _ \ / _ \ / _ \ | |_| |  / _ \  |  _ \ 
 | (_) | (_) |  __/| | | ||  _  | / ___ \ | |_) )
  \___/|  __/ \___/|_| |_||_| |_|/_/   \_\|____/ 
       |_|       3.3.0 - Release Build

Use '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
To exit, use '<ctrl-d>' or 'logout'.
openhab> log:list | grep -i org.openhab.binding.avmfritz
openhab> log:set debug org.openhab.binding.zigbee
Error executing command: Unable to set level for logger