Connect OR with Mqtt explrrer

Hi ,
I have successfully setup OpenRemote on my Intellij IDE with port number 9000. Now I want connect my OpenRemote with MQTT Client. I gave host as "localhost:9000, port 1883 and 8883, user id and pass on Mqtt explorrer. but this one not connect.


And getting the log.

ERROR [Thread-14 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60049 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-13 17:47:16.341 ERROR [Thread-15 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60050 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-13 17:47:32.907 ERROR [Thread-14 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60049 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-13 17:47:32.907 ERROR [Thread-14 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60049 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-13 17:47:46.350 ERROR [Thread-15 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60050 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-13 17:47:46.350 ERROR [Thread-15 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60050 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-13 17:47:47.358 ERROR [Thread-16 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60052 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-13 17:48:17.357 ERROR [Thread-16 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60052 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-13 17:48:17.357 ERROR [Thread-16 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60052 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-13 17:48:18.369 ERROR [Thread-17 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60053 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]

HOW to connect OR with mqtt client.

Hi Vicky,

Could you try leaving out the port in host (remove :9000), and use 1883 in port.

Don

Hi Don,
Thank you for your response. I tried the same remove 9000, and change port 8883 to 1883. but my mqtt explorer show Disconnect from server. also generate some logs on Intellij IDE.

Logs
2023-02-15 10:42:23.932 ERROR [Thread-2 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60712 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:42:23.932 ERROR [Thread-2 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60712 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:42:24.946 ERROR [Thread-3 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60720 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:42:34.551 ERROR [Thread-4 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60721 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:42:54.953 ERROR [Thread-3 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60720 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:42:54.953 ERROR [Thread-3 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60720 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:43:04.560 ERROR [Thread-4 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60721 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:43:04.560 ERROR [Thread-4 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60721 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:43:05.574 ERROR [Thread-5 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60723 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:43:35.575 ERROR [Thread-5 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60723 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:43:35.575 ERROR [Thread-5 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60723 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:43:36.584 ERROR [Thread-6 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60724 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:44:06.588 ERROR [Thread-6 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60724 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:44:06.588 ERROR [Thread-6 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60724 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:44:07.599 ERROR [Thread-7 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60726 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:44:37.612 ERROR [Thread-7 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60726 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:44:37.612 ERROR [Thread-7 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60726 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:44:38.624 ERROR [Thread-8 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60727 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:45:08.636 ERROR [Thread-8 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60727 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:45:08.636 ERROR [Thread-8 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60727 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:45:09.645 ERROR [Thread-9 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60728 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:45:39.645 ERROR [Thread-9 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60728 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:45:39.645 ERROR [Thread-9 (activemq-netty…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60728 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 10:45:40.655 ERROR [Thread-10 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:60729 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]

**After some time it give some random data of Rotterdam location, also I got data from different asset ID or (UNKNOWN) **

2023-02-15 11:09:43.278 ERROR [Thread-12 (activemq-nett…ads)] org.apache.activemq.artemis.core.server : AMQ224096: Error setting up connection from /127.0.0.1:61476 to /127.0.0.1:1883; protocol CORE not found in map: [MQTT]
2023-02-15 11:20:00.173 FINE [Messaging-AssetQueue-13 ] remote.manager.asset.AssetStorageService : Asset query took 17ms: return count=1
2023-02-15 11:20:00.176 FINE [Messaging-AssetQueue-13 ] remote.manager.asset.AssetStorageService : Asset query took 2ms: return count=1
2023-02-15 11:20:00.182 FINE [Messaging-AssetQueue-13 ] remote.manager.asset.AssetStorageService : Asset query took 5ms: return count=1
2023-02-15 11:20:00.185 FINE [Messaging-AssetQueue-13 ] remote.manager.asset.AssetStorageService : Asset query took 2ms: return count=1
2023-02-15 11:20:00.188 FINE [Messaging-AssetQueue-13 ] remote.manager.asset.AssetStorageService : Asset query took 2ms: return count=1
2023-02-15 11:20:00.193 FINE [Messaging-AssetQueue-13 ] ote.manager.asset.AssetProcessingService : <<< Processing complete in 20ms: Asset ID=2bMjSx0iy1usC9KKhT24h9, Asset name=Weather, Attribute{name=‘currentWeather’, value=‘{“coord”:{“lon”:4.4633,“lat”:51.9188},“weather”:[{“id”:803,“main”:“Clouds”,“description”:“broken clouds”,“icon”:“04n”}],“base”:“stations”,“main”:{“temp”:1.8,“feels_like”:-0.93,“temp_min”:0.55,“temp_max”:2.77,“pressure”:1026,“humidity”:93,“sea_level”:1026,“grnd_level”:1026},“visibility”:10000,“wind”:{“speed”:2.54,“deg”:179,“gust”:3.89},“clouds”:{“all”:60},“dt”:1676440201,“sys”:{“type”:2,“id”:2006594,“country”:“NL”,“sunrise”:1676444281,“sunset”:1676480090},“timezone”:3600,“id”:2747890,“name”:“Gemeente Rotterdam”,“cod”:200}’, timestamp=‘1676440200154’}
2023-02-15 11:20:00.195 FINE [Messaging-AssetQueue-13 ] enremote.container.concurrent.GlobalLock : Lock duration for thread (Messaging-AssetQueue-13): 41ms
2023-02-15 11:20:00.199 FINE [Messaging-AssetQueue-13 ] remote.manager.asset.AssetStorageService : Asset query took 4ms: return count=1
2023-02-15 11:20:00.199 FINE [Messaging-AssetQueue-13 ] enremote.container.concurrent.GlobalLock : Lock duration for thread (Messaging-AssetQueue-13): 0ms
2023-02-15 11:20:00.215 FINE [Messaging-AssetQueue-13 ] ote.manager.asset.AssetProcessingService : <<< Processing complete in 16ms: Asset ID=2bMjSx0iy1usC9KKhT24h9, Asset name=Weather, Attribute{name=‘temperature’, value=‘1.8’, timestamp=‘1676440200176’}
2023-02-15 11:20:00.218 FINE [Messaging-AssetQueue-13 ] enremote.container.concurrent.GlobalLock : Lock duration for thread (Messaging-AssetQueue-13): 23ms
2023-02-15 11:20:00.221 FINE [Messaging-AssetQueue-13 ] remote.manager.asset.AssetStorageService : Asset query took 3ms: return count=1
2023-02-15 11:20:00.221 FINE [Messaging-AssetQueue-13 ] enremote.container.concurrent.GlobalLock : Lock duration for thread (Messaging-AssetQueue-13): 0ms
2023-02-15 11:20:00.231 FINE [Messaging-AssetQueue-13 ] ote.manager.asset.AssetProcessingService : <<< Processing complete in 10ms: Asset ID=2bMjSx0iy1usC9KKhT24h9, Asset name=Weather, Attribute{name=‘humidity’, value=‘93’, timestamp=‘1676440200182’}
2023-02-15 11:20:00.233 FINE [Messaging-AssetQueue-13 ] enremote.container.concurrent.GlobalLock : Lock duration for thread (Messaging-AssetQueue-13): 15ms
2023-02-15 11:20:00.237 FINE [Messaging-AssetQueue-13 ] remote.manager.asset.AssetStorageService : Asset query took 4ms: return count=1
2023-02-15 11:20:00.238 FINE [Messaging-AssetQueue-13 ] enremote.container.concurrent.GlobalLock : Lock duration for thread (Messaging-AssetQueue-13): 0ms
2023-02-15 11:20:00.244 FINE [Messaging-AssetQueue-13 ] ote.manager.asset.AssetProcessingService : <<< Processing complete in 6ms: Asset ID=2bMjSx0iy1usC9KKhT24h9, Asset name=Weather, Attribute{name=‘windSpeed’, value=‘2.54’, timestamp=‘1676440200185’}
2023-02-15 11:20:00.246 FINE [Messaging-AssetQueue-13 ] enremote.container.concurrent.GlobalLock : Lock duration for thread (Messaging-AssetQueue-13): 13ms
2023-02-15 11:20:00.249 FINE [Messaging-AssetQueue-13 ] remote.manager.asset.AssetStorageService : Asset query took 3ms: return count=1
2023-02-15 11:20:00.249 FINE [Messaging-AssetQueue-13 ] enremote.container.concurrent.GlobalLock : Lock duration for thread (Messaging-AssetQueue-13): 0ms
2023-02-15 11:20:00.255 FINE [Messaging-AssetQueue-13 ] ote.manager.asset.AssetProcessingService : <<< Processing complete in 6ms: Asset ID=2bMjSx0iy1usC9KKhT24h9, Asset name=Weather, Attribute{name=‘windDirection’, value=‘179’, timestamp=‘1676440200189’}
2023-02-15 11:20:00.257 FINE [Messaging-AssetQueue-13 ] enremote.container.concurrent.GlobalLock : Lock duration for thread (Messaging-AssetQueue-13): 11ms
2023-02-15 11:20:03.207 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘De Kuip’ executed in: 0ms
2023-02-15 11:20:03.207 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Euromast’ executed in: 0ms
2023-02-15 11:20:03.207 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Markthal’ executed in: 0ms
2023-02-15 11:20:03.207 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Markthal: All chargers in use’ executed in: 0ms
2023-02-15 11:20:03.207 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Ons Park: Brighten lights’ executed in: 0ms
2023-02-15 11:20:03.207 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Ons Park: Dim lights’ executed in: 0ms
2023-02-15 11:20:03.207 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Station: Crowded square’ executed in: 0ms
2023-02-15 11:20:03.207 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Environment monitoring: Alerts’ executed in: 0ms
2023-02-15 11:20:03.208 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Total power consumption’ executed in: 1ms
2023-02-15 11:20:03.209 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Total power production’ executed in: 0ms
2023-02-15 11:20:03.209 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘De Rotterdam: Power balance’ executed in: 0ms
2023-02-15 11:20:03.210 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Parking: Occupied spaces’ executed in: 1ms
2023-02-15 11:20:03.210 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Parking: Almost full’ executed in: 0ms
2023-02-15 11:20:03.210 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘De Rotterdam: Battery use’ executed in: 0ms
2023-02-15 11:20:03.211 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules deployment ‘Light group: On/Off’ executed in: 1ms
2023-02-15 11:20:03.211 FINE [Scheduled task-4 ] org.openremote.manager.rules.RulesEngine : Rules firing took 3ms on: RulesEngine{id=‘RulesEngineId{scope=RealmRuleset, realm=‘smartcity’, assetId=‘null’}’, running=‘true’, deployments=‘[RulesetDeployment{id=1000, name=‘De Kuip’, version=0, status=DEPLOYED}, RulesetDeployment{id=1001, name=‘Euromast’, version=0, status=DEPLOYED}, RulesetDeployment{id=1002, name=‘Markthal’, version=0, status=DEPLOYED}, RulesetDeployment{id=1003, name=‘Markthal: All chargers in use’, version=0, status=DEPLOYED}, RulesetDeployment{id=1004, name=‘Ons Park: Brighten lights’, version=0, status=DEPLOYED}, RulesetDeployment{id=1005, name=‘Ons Park: Dim lights’, version=0, status=DEPLOYED}, RulesetDeployment{id=1006, name=‘Station: Crowded square’, version=0, status=DEPLOYED}, RulesetDeployment{id=1007, name=‘Environment monitoring: Alerts’, version=0, status=DEPLOYED}, RulesetDeployment{id=1008, name=‘Total power consumption’, version=0, status=DEPLOYED}, RulesetDeployment{id=1009, name=‘Total power production’, version=0, status=DEPLOYED}, RulesetDeployment{id=1010, name=‘De Rotterdam: Power balance’, version=0, status=DEPLOYED}, RulesetDeployment{id=1011, name=‘Parking: Occupied spaces’, version=0, status=DEPLOYED}, RulesetDeployment{id=1012, name=‘Parking: Almost full’, version=0, status=DEPLOYED}, RulesetDeployment{id=1013, name=‘De Rotterdam: Battery use’, version=0, status=DEPLOYED}, RulesetDeployment{id=1014, name=‘Light group: On/Off’, version=0, status=DEPLOYED}]’}
2023-02-15 11:24:01.529 FINE [Messaging-ClientEventTop…c-57] remote.manager.asset.AssetStorageService : Asset query took 4ms: return count=3
2023-02-15 11:24:02.781 FINE [Messaging-ClientEventTop…c-53] remote.manager.asset.AssetStorageService : Asset query took 3ms: return count=1
2023-02-15 11:24:02.788 FINE [WebService task-8 ] curity.keycloak.KeycloakIdentityProvider : Loading adapter config for client ‘openremote’ in realm ‘master’
2023-02-15 11:24:02.807 INFO [WebService task-8 ] org.keycloak.adapters.KeycloakDeployment : Loaded URLs from http://127.0.0.1:8081/auth/realms/master/.well-known/openid-configuration

Vicky kumar

If you are connecting to the MQTT broker whilst running inside an IDE then you need to disable TLS and use port 1883…in your screenshot it looks like TLS is still enabled.

1 Like

Hi Rich,
Yes now I am able to connect and send data from mqtt explorer to openremote.