No mqtt subscribe to mosquitto

Hi Forum,

I have read the appropriate documentation for days, but there is still no mqtt subscription to mosquitto.
Configuration:
Java: Sun Java 1.8.0

Software: OpenHAB 1.8.3

Addons: org.openhab.action.mqtt-1.8.3.jar org.openhab.binding.mqttitude-1.8.3.jar
org.openhab.persistence.rrd4j-1.8.3.jar
org.openhab.binding.mqtt-1.8.3.jar org.openhab.persistence.mqtt-1.8.3.jar

items:
Number kessel_abgas “temp [%.1f]” {mqtt="<[broker:openhab/house/heizung/ofen/temp/kessel_abgas:state:default]"}

openhab.cfg:
root@speicher42:/opt/openhab/configurations/items# grep mqtt …/openhab.cfg
mqtt-persistence:broker=broker
mqtt-persistence:topic=/house/heizung/broker/temp/kessel_abgas.csv
mqtt:broker.url=tcp://192.168.2.200:1883
mqtt:broker.clientId=openhab
mqtt:broker.user=valentin
mqtt:broker.pwd=xyz

mosquitto output:
1482923442: New connection from 192.168.2.200 on port 1883.
1482923442: New client connected from 192.168.2.200 as openhab (c1, k60, u’valentin’).

tcpdump:
<shows successfull TCP/IP and Layer 7 connection, but no subscription/attempt to topic /house/heizung/ofen/temp/kessel_abgas>

Subscription via unix-cmdline works:
mosquitto_sub -h 192.168.2.200 -u valentin -P xyz -p 1883 -t house/heizung/ofen/temp/kessel_abgas >> /tmp/abgas

Any help is highly appreciated,

Thanks in advance,

Valentin

You need to have the same channel name, so try:
Number kessel_abgas "temp [%.1f]" {mqtt="<[broker:house/heizung/ofen/temp/kessel_abgas:state:default]"}

sihui, Thanks! :slight_smile:
I had this configuration before. I changed it to the proposed line. Unfortuateley, there is no success:

13:17:06.968 [DEBUG] [.b.mqtt.internal.MqttActivator:34 ] - MQTT binding has been started.
13:17:06.993 [DEBUG] [m.internal.MqttEventBusBinding:68 ] - MQTT: Activating event bus binding.
thats all :frowning:

Did you try subscribing to all topics in verbose mode via wildcard?

pi@raspberrypi3:~ $ mosquitto_sub -v -t /#
/esp8266three/temperature/outside 6.2

At least it should give you the correct topic for your item …

pi@kotten ~/trepo/bin $ mosquitto_sub -h 192.168.2.200 -u house -P xyz -p 1883 -v -t house/#
house/heizung/ofen/online Ofen online
house/heizung/ofen/temp/kessel_abgas 171.7500
house/heizung/ofen/temp/kessel_vorlauf 62.0000
house/heizung/ofen/temp/kessel_ruecklauf 45.5000
house/heizung/ofen/temp/kessel_wwspeicher 10.8750
house/heizung/ofen/temp/kessel_puffer1 61.1250
house/heizung/ofen/temp/kessel_puffer_rl 46.4375
house/heizung/ofen/temp/puffer2 58.6250
house/heizung/ofen/temp/kessel_ruecklauf 46.0000
house/heizung/ofen/temp/kessel_puffer_rl 46.5625
house/heizung/ofen/temp/kessel_vorlauf 62.5000

Hmmm … what about

mosquitto_sub -h 192.168.2.200 -u house -P xyz -p 1883 -v -t /#
?

I’m not a MQTT specialist :slight_smile: but that looks to me as your topic is /house/house at the beginning.

The documentation at https://github.com/openhab/openhab/wiki/MQTT-Binding shows that the syntax of item line is
Item myItem {mqtt="<>[<< broker>>:<>:<>:<>], …"}

My home.item meets this syntax.

Number kessel_abgas {mqtt="<[broker:house/heizung/ofen/temp/kessel_abgas:state:default]"}

Nevertheless, even minor changes in the items-file does not cause any requests (visible via tcpdump) from OpenHAB to mosquitto-Broker. This does not meet my expectation? Only the successfull establish process of the connection is visible with tcpdump.
Any request of mosquitto_sub is visible with tcpdump!

Is there any dependency between mqtt-topic and other parts of the OpenHAB-configuration?

Thanks in advance, Valentin

I did not doubt that.
But I guess you are subscribing to a wrong topic: house/heizung/ofen/temp/kessel_abgas

And if you would using my syntax
mosquitto_sub -h 192.168.2.200 -u house -P xyz -p 1883 -v -t /#
it would show you the correct topic.

It’s worth a try …

mosquitto_sub -h 192.168.2.200 -u house -P xyz -p 1883 -v -t /#

does not deliver any output after minutes … :frowning:

But I didn’t see, that OpenHAB is requesting that topic from mosquitto.

That’s possibly misleading, in that the number of sections divided by colons differs between “in” binding and “out” binding config strings. I don’t see a problem with your particular example of the “in” binding string.

Make sure that the messages published to house/heizung/ofen/temp/kessel_abgas consist of decimal digits, use only a period (not comma) to separate decimal values, no thousands separator, and no leading or trailing spaces. In other words, the message cannot be interpreted as a Number unless it is properly formatted.

sihue, watou: Thanks for your answers to the thread :slight_smile:

As you read in my former posts, the command-line mosquitto-client reads well formated data.

Unfortunately, as proofed by tcpdump, no subscribe-request is issued by OpenHAB, thus the issue seems to be located in OpenHAB. (successfull establishment of the connection is shown by tcpdump, though)

I tried to debug OpenHAB with the following lines in logback.xml

 < logger name="org.openhab" level="INFO"/>
 < logger name="org.openhab.binding.mqtt" level="DEBUG" />
 < logger name="org.openhab.io.transport.mqtt" level="DEBUG" />

This does’nt lead to any more diagnostic output :frowning:

You don’t happen to have another client with the same clientId, do you?

Different user than valentin?

I changed the clientId to be sure:

Creating new client for ‘tcp://192.168.2.200:1883’ using id ‘myopenhab’ and file store ‘/tmp/broker’

The user “house” was indeed a typo. Should always be valentin :slight_smile:

Launching the openHAB runtime in debug mode…
Listening for transport dt_socket at address: 8001
osgi> 15:05:30.348 [DEBUG] [.s.internal.SchedulerActivator:36 ] - Scheduler has been started.
15:05:30.420 [INFO ] [uartz.impl.StdSchedulerFactory:1175 ] - Using default implementation for ThreadExecutor
15:05:30.455 [INFO ] [rtz.core.SchedulerSignalerImpl:61 ] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
15:05:30.456 [INFO ] [rg.quartz.core.QuartzScheduler:243 ] - Quartz Scheduler v.2.1.7 created.
15:05:30.459 [INFO ] [org.quartz.simpl.RAMJobStore :154 ] - RAMJobStore initialized.
15:05:30.462 [INFO ] [rg.quartz.core.QuartzScheduler:268 ] - Scheduler meta-data: Quartz Scheduler (v2.1.7) ‘openHAB-job-scheduler’ with instanceId 'NON_CLUSTERED’
Scheduler class: ‘org.quartz.core.QuartzScheduler’ - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool ‘org.quartz.simpl.SimpleThreadPool’ - with 2 threads.
Using job-store ‘org.quartz.simpl.RAMJobStore’ - which does not support persistence. and is not clustered.

15:05:30.462 [INFO ] [uartz.impl.StdSchedulerFactory:1324 ] - Quartz scheduler ‘openHAB-job-scheduler’ initialized from specified file: './etc/quartz.properties’
15:05:30.463 [INFO ] [uartz.impl.StdSchedulerFactory:1328 ] - Quartz scheduler version: 2.1.7
15:05:30.464 [INFO ] [rg.quartz.core.QuartzScheduler:534 ] - Scheduler openHAB-job-scheduler_$_NON_CLUSTERED started.
15:05:30.471 [DEBUG] [o.config.core.ConfigDispatcher:146 ] - Processing openHAB default configuration file ‘/opt/openhab/configurations/openhab_default.cfg’.
15:05:30.560 [DEBUG] [o.config.core.ConfigDispatcher:168 ] - Processing openHAB main configuration file ‘/opt/openhab/configurations/openhab.cfg’.
15:05:30.652 [DEBUG] [.o.core.internal.CoreActivator:93 ] - UUID file already exists at ‘/opt/openhab/webapps/static/uuid’ with content '51f4c550-ddca-43b4-af81-b7f014987425’
15:05:30.653 [DEBUG] [.o.core.internal.CoreActivator:115 ] - Created file ‘/opt/openhab/webapps/static/version’ with content '1.8.3’
15:05:30.654 [INFO ] [.o.core.internal.CoreActivator:61 ] - openHAB runtime has been started (v1.8.3).
15:05:30.734 [DEBUG] [a.internal.AutoUpdateActivator:31 ] - AutoUpdate binding has been started.
15:05:32.308 [DEBUG] [.p.i.PersistenceModelActivator:23 ] - Registered ‘persistence’ configuration parser
15:05:32.340 [DEBUG] [.c.t.i.TransformationActivator:38 ] - Transformation Service has been started.
15:05:32.415 [DEBUG] [m.internal.MultimediaActivator:34 ] - Multimedia I/O bundle has been started.
15:05:32.455 [DEBUG] [.s.i.DiscoveryServiceActivator:27 ] - Discovery service has been started.
15:05:32.467 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl:93 ] - mDNS service has been started
15:05:32.486 [DEBUG] [.io.transport.mqtt.MqttService:123 ] - Starting MQTT Service…
15:05:32.555 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl:53 ] - Service Discovery initialization completed.
15:05:32.585 [INFO ] [.io.transport.mqtt.MqttService:108 ] - MQTT Service initialization completed.
15:05:32.586 [INFO ] [o.i.t.m.i.MqttBrokerConnection:114 ] - Starting MQTT broker connection 'broker’
15:05:32.592 [DEBUG] [o.i.t.m.i.MqttBrokerConnection:294 ] - Creating new client for ‘tcp://192.168.2.200:1883’ using id ‘myopenhab’ and file store '/tmp/broker’
15:05:32.788 [DEBUG] [.i.internal.ItemModelActivator:24 ] - Registered ‘item’ configuration parser
15:05:32.958 [DEBUG] [o.o.c.i.items.ItemRegistryImpl:137 ] - Item provider ‘GenericItemProvider’ has been added.
15:05:34.111 [DEBUG] [.o.m.s.i.SitemapModelActivator:23 ] - Registered ‘sitemap’ configuration parser
15:05:34.248 [DEBUG] [io.rest.internal.RESTActivator:33 ] - REST API has been started.
15:05:34.353 [INFO ] [org.atmosphere.util.IOUtils :370 ] - META-INF/services/org.atmosphere.cpr.AtmosphereFramework not found in class loader
15:05:34.405 [INFO ] [sphere.cpr.AtmosphereFramework:2601 ] - Atmosphere is using org.atmosphere.cpr.DefaultAnnotationProcessor for processing annotation
15:05:34.407 [INFO ] [cpr.DefaultAnnotationProcessor:138 ] - AnnotationProcessor class org.atmosphere.cpr.DefaultAnnotationProcessor$BytecodeBasedAnnotationProcessor being used
15:05:34.428 [WARN ] [cpr.DefaultAnnotationProcessor:178 ] - Unable to detect annotations. Application may fail to deploy.
15:05:34.473 [INFO ] [sphere.cpr.AtmosphereFramework:1891 ] - Auto detecting atmosphere handlers /WEB-INF/classes/
15:05:34.510 [INFO ] [sphere.cpr.AtmosphereFramework:639 ] - Installed AtmosphereHandler org.atmosphere.handler.ReflectorServletProcessor mapped to context-path /* and Broadcaster Class org.atmosphere.jersey.JerseyBroadcaster
15:05:34.511 [INFO ] [sphere.cpr.AtmosphereFramework:1945 ] - Auto detecting WebSocketHandler in /WEB-INF/classes/
15:05:34.513 [INFO ] [sphere.cpr.AtmosphereFramework:1602 ] - Installed WebSocketProtocol org.atmosphere.websocket.protocol.SimpleHttpProtocol
15:05:34.576 [INFO ] [.a.h.ReflectorServletProcessor:103 ] - Installing Servlet com.sun.jersey.spi.container.servlet.ServletContainer
15:05:34.767 [INFO ] [c.s.j.s.i.a.WebApplicationImpl:815 ] - Initiating Jersey application, version 'Jersey: 1.18.1 02/19/2014 03:28 AM’
15:05:34.772 [INFO ] [c.s.j.s.i.a.WebApplicationImpl:826 ] - Adding the following classes declared in META-INF/services/jersey-server-components to the resource configuration:
class org.atmosphere.jersey.AtmosphereResourceConfigurator
15:05:34.879 [INFO ] [j.s.i.a.DeferredResourceConfig:101 ] - Instantiated the Application class org.openhab.io.rest.RESTApplication
15:05:36.373 [INFO ] [sphere.cpr.AtmosphereFramework:2435 ] - AtmosphereInterceptor CORS Interceptor Support will always be executed first
15:05:36.375 [INFO ] [sphere.cpr.AtmosphereFramework:2404 ] - Installed AtmosphereInterceptor CORS Interceptor Support with priority FIRST_BEFORE_DEFAULT
15:05:36.377 [INFO ] [sphere.cpr.AtmosphereFramework:2404 ] - Installed AtmosphereInterceptor Default Response’s Headers Interceptor with priority AFTER_DEFAULT
15:05:36.380 [INFO ] [sphere.cpr.AtmosphereFramework:2404 ] - Installed AtmosphereInterceptor Android Interceptor Support with priority AFTER_DEFAULT
15:05:36.382 [INFO ] [sphere.cpr.AtmosphereFramework:2404 ] - Installed AtmosphereInterceptor SSE Interceptor Support with priority AFTER_DEFAULT
15:05:36.384 [INFO ] [sphere.cpr.AtmosphereFramework:2404 ] - Installed AtmosphereInterceptor JSONP Interceptor Support with priority AFTER_DEFAULT
15:05:36.387 [INFO ] [sphere.cpr.AtmosphereFramework:2404 ] - Installed AtmosphereInterceptor Atmosphere JavaScript Protocol with priority AFTER_DEFAULT
15:05:36.388 [INFO ] [sphere.cpr.AtmosphereFramework:2404 ] - Installed AtmosphereInterceptor Browser disconnection detection with priority AFTER_DEFAULT
15:05:36.395 [INFO ] [sphere.cpr.AtmosphereFramework:935 ] - Using EndpointMapper class org.atmosphere.util.DefaultEndpointMapper
15:05:36.398 [WARN ] [sphere.cpr.AtmosphereFramework:941 ] - No BroadcasterCache configured. Broadcasted message between client reconnection will be LOST. It is recommended to configure the org.atmosphere.cache.UUIDBroadcasterCache
15:05:36.398 [INFO ] [sphere.cpr.AtmosphereFramework:949 ] - Default Broadcaster Class: org.atmosphere.jersey.JerseyBroadcaster
15:05:36.399 [INFO ] [sphere.cpr.AtmosphereFramework:950 ] - Broadcaster Polling Wait Time 100
15:05:36.400 [INFO ] [sphere.cpr.AtmosphereFramework:951 ] - Shared ExecutorService supported: true
15:05:36.402 [INFO ] [sphere.cpr.AtmosphereFramework:958 ] - Messaging Thread Pool Size: 10
15:05:36.402 [INFO ] [sphere.cpr.AtmosphereFramework:968 ] - Async I/O Thread Pool Size: 10
15:05:36.403 [INFO ] [sphere.cpr.AtmosphereFramework:979 ] - Using BroadcasterFactory: org.atmosphere.cpr.DefaultBroadcasterFactory
15:05:36.405 [INFO ] [sphere.cpr.AtmosphereFramework:980 ] - Using WebSocketProcessor: org.atmosphere.websocket.DefaultWebSocketProcessor
15:05:36.406 [INFO ] [sphere.cpr.AtmosphereFramework:990 ] - Invoke AtmosphereInterceptor on WebSocket message true
15:05:36.407 [INFO ] [sphere.cpr.AtmosphereFramework:991 ] - HttpSession supported: false
15:05:36.408 [INFO ] [sphere.cpr.AtmosphereFramework:993 ] - Atmosphere is using DefaultAtmosphereObjectFactory for dependency injection and object creation
15:05:36.409 [INFO ] [sphere.cpr.AtmosphereFramework:994 ] - Atmosphere is using async support: org.atmosphere.container.JettyAsyncSupportWithWebSocket running under container: jetty/8.1.3.v20120522 with WebSocket enabled.
15:05:36.412 [INFO ] [sphere.cpr.AtmosphereFramework:996 ] - Atmosphere Framework 2.2.5 started.
15:05:36.413 [INFO ] [sphere.cpr.AtmosphereFramework:998 ] -

    For Atmosphere Framework Commercial Support, visit
    http://www.async-io.org/ or send an email to support@async-io.org

15:05:36.415 [INFO ] [penhab.io.rest.RESTApplication:144 ] - Started REST API at /rest
15:05:36.418 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:66 ] - Registering new service _openhab-server._tcp.local. at port 8080
15:05:40.387 [DEBUG] [o.o.i.s.i.DiscoveryServiceImpl:66 ] - Registering new service _openhab-server-ssl._tcp.local. at port 8443
15:05:41.903 [INFO ] [c.internal.ModelRepositoryImpl:80 ] - Loading model 'home.sitemap’
15:05:42.164 [INFO ] [c.internal.ModelRepositoryImpl:80 ] - Loading model 'db4o.persist’
15:05:42.208 [INFO ] [c.internal.ModelRepositoryImpl:80 ] - Loading model 'exec.persist’
15:05:42.220 [INFO ] [c.internal.ModelRepositoryImpl:80 ] - Loading model 'rrd4j.persist’
15:05:42.230 [INFO ] [c.internal.ModelRepositoryImpl:80 ] - Loading model 'mqtt.persist’
15:05:42.238 [INFO ] [c.internal.ModelRepositoryImpl:80 ] - Loading model 'logging.persist’
15:05:42.270 [INFO ] [c.internal.ModelRepositoryImpl:80 ] - Loading model 'home.items’
15:05:42.289 [DEBUG] [i.internal.GenericItemProvider:154 ] - Processing binding configs for items from model 'home.items’
15:05:42.292 [DEBUG] [i.internal.GenericItemProvider:133 ] - Read items from model 'home.items’
15:05:43.153 [INFO ] [.o.u.w.i.servlet.WebAppServlet:80 ] - Started Classic UI at /classicui/openhab.app
15:05:43.540 [DEBUG] [.r.internal.RuleModelActivator:42 ] - Registered ‘rules’ configuration parser
15:05:43.561 [DEBUG] [m.r.internal.engine.RuleEngine:77 ] - Started rule engine
15:05:46.260 [DEBUG] [.a.mqtt.internal.MqttActivator:34 ] - Mqtt action has been started.
15:05:46.276 [DEBUG] [o.p.m.i.MqttPersistenceService:100 ] - Deactivating MQTT Persistence
15:05:46.278 [WARN ] [o.p.m.i.MqttPersistenceService:123 ] - mqtt-persistence:message
15:05:46.279 [DEBUG] [o.p.m.i.MqttPersistenceService:81 ] - Configuration updated for MQTT Persistence.
15:05:46.280 [DEBUG] [o.p.m.i.MqttPersistenceService:88 ] - Activating MQTT Persistence
15:05:46.285 [DEBUG] [.p.internal.PersistenceManager:146 ] - Initializing mqtt persistence service.
15:05:46.350 [DEBUG] [.p.internal.PersistenceManager:428 ] - Scheduled strategy mqtt.everyMinute with cron expression 0 * * * * ?
15:05:46.354 [DEBUG] [.p.internal.PersistenceManager:428 ] - Scheduled strategy mqtt.everyHour with cron expression 0 0 * * * ?
15:05:46.357 [DEBUG] [.p.internal.PersistenceManager:428 ] - Scheduled strategy mqtt.everyDay with cron expression 0 0 0 * * ?
15:05:46.375 [DEBUG] [.rrd4j.internal.RRD4jActivator:31 ] - RRD4j persistence bundle has been started.
15:05:46.395 [DEBUG] [.p.rrd4j.internal.RRD4jService:395 ] - Unknown property name : org.openhab.persistence.rrd4j
15:05:46.396 [DEBUG] [.p.rrd4j.internal.RRD4jService:364 ] - config ‘objectClass’ should have the format 'name.configkey’
15:05:46.397 [INFO ] [.p.rrd4j.internal.RRD4jService:407 ] - Removing invalid defintion component = null heartbeat = 0 min/max = 0.0/0.0 step = 0 0 archives(s) = [] 0 items(s) = []
15:05:46.398 [DEBUG] [.p.rrd4j.internal.RRD4jService:405 ] - Created default_other = GAUGE heartbeat = 3600 min/max = NaN/NaN step = 1 6 archives(s) = [ MAX xff = 0.999 steps = 1 rows = 3600 MAX xff = 0.999 steps = 10 rows = 1440 MAX xff = 0.999 steps = 60 rows = 1440 MAX xff = 0.999 steps = 900 rows = 2880 MAX xff = 0.999 steps = 21600 rows = 1460 MAX xff = 0.999 steps = 86400 rows = 3650] 0 items(s) = []
15:05:46.399 [DEBUG] [.p.rrd4j.internal.RRD4jService:405 ] - Created default_numeric = GAUGE heartbeat = 60 min/max = NaN/NaN step = 60 6 archives(s) = [ AVERAGE xff = 0.5 steps = 1 rows = 480 AVERAGE xff = 0.5 steps = 4 rows = 360 AVERAGE xff = 0.5 steps = 14 rows = 644 AVERAGE xff = 0.5 steps = 60 rows = 720 AVERAGE xff = 0.5 steps = 720 rows = 730 AVERAGE xff = 0.5 steps = 10080 rows = 520] 0 items(s) = []
15:05:46.402 [DEBUG] [.p.internal.PersistenceManager:146 ] - Initializing rrd4j persistence service.
15:05:46.414 [DEBUG] [.p.internal.PersistenceManager:428 ] - Scheduled strategy rrd4j.everyMinute with cron expression 0 * * * * ?
15:05:46.417 [DEBUG] [.p.internal.PersistenceManager:428 ] - Scheduled strategy rrd4j.everyHour with cron expression 0 0 * * * ?
15:05:46.420 [DEBUG] [.p.internal.PersistenceManager:428 ] - Scheduled strategy rrd4j.everyDay with cron expression 0 0 0 * * ?
15:05:46.428 [DEBUG] [p.r.i.charts.RRD4jChartServlet:118 ] - Starting up rrd chart servlet at /rrdchart.png
15:05:46.431 [DEBUG] [.m.internal.MqttitudeActivator:33 ] - Mqttitude binding has been started.
15:05:46.449 [DEBUG] [.b.m.internal.MqttitudeBinding:84 ] - Activating Mqttitude binding
15:05:46.452 [DEBUG] [.b.mqtt.internal.MqttActivator:34 ] - MQTT binding has been started.
15:05:46.475 [DEBUG] [m.internal.MqttEventBusBinding:68 ] - MQTT: Activating event bus binding.
15:06:00.040 [DEBUG] [.p.internal.PersistenceManager:328 ] - Item group ‘Temperature’ does not exist.
15:07:00.004 [DEBUG] [.p.internal.PersistenceManager:328 ] - Item group ‘Temperature’ does not exist.

mosquitto output:

1483452332: New connection from 192.168.2.200 on port 1883.
1483452332: New client connected from 192.168.2.200 as myopenhab (c1, k60, u’valentin’).

Please check your persist/mqtt.persist file if you really intend to use MQTT persistence. If you don’t intend to use it, remove org.openhab.persistence.mqtt-1.8.3.jar from your addons directory.

Hmm. Do you have any MQTT Event Bus binding configuration somewhere? Do you intend to use this binding? If not, make sure you have not configuration for it.

openhab.cfg:

chart:provider=default
folder:items=10,items
folder:persistence=10,persist
folder:rules=10,rules
folder:scripts=10,script
folder:sitemaps=10,sitemap
hue:secret=openHABRuntime
logging:pattern=%date{ISO8601} - %-25logger: %msg%n
mqtt:broker.clientId=myopenhab
mqtt:broker.pwd=xyz
mqtt:broker.url=tcp://192.168.2.200:1883
mqtt:broker.user=valentin
mqtt-persistence:broker=broker
mqtt-persistence:topic=/villaer/heizung/broker/temp/kessel_abgas.csv
ntp:hostname=ptbtime1.ptb.de
persistence:default=rrd4j
tcp:refreshinterval=250

Thus, no config for mqtt eventbus.

I removed org.openhab.persistence.mqtt-1.8.3.jar and restarted openhab.

Still, no subscription to mosquitto with topic home/heizung/ofen/temp/kessel_abgas :frowning:

but successfull connection:
1483458812: New connection from 192.168.2.200 on port 1883.
1483458813: New client connected from 192.168.2.200 as myopenhab (c1, k60, u’valentin’).

Have you had any success yet? I am getting pretty much the exact same issue. OH connects to mosquitto, but it doesn’t actually subscribe to anything.

I am on OH2 though

Unfortunately, not :frowning:

Thanks for your hint. thus, I will not give OH2 a try … :frowning: and spent some more hours on that …

Nevertheless, we do not want to resign.

Have you tried any debugging switches? “logback.xml” ??

Hi Guys,

I am also trying to get mosquito and openhab 1.9 talking. When i use mosquito_sub with /owntracks/jcid/# i get all the needed data for that user… I just cant figure out the openhab.cfg and items portion…

mosquitto_sub -h localhost -p 1883 -v -t 'owntracks/jcid/#'

In openhab.cfg i tried

mqtt-eventbus:broker=mosquitto
#mqtt-eventbus:commandPublishTopic=/openHAB/out/${item}/command
mqtt-eventbus:stateSubscribeTopic=/owntracks/jcid

which shows me a SUBSCRIBE at least but cant figure out how to get that to my items in “Items”

Received SUBSCRIBE from root.1486587664442
1486587691:     /owntracks/jcid/# (QoS 2)

In items i have

String  Jay_Presence   "Jay @ Home"   { mqtt="<[mosquitto:owntracks/jcid/#]" }

tried a bunch of things and no luck…

heeelp! :wink: