Raspberry Pi 3上Eclipse Kura连Kapua成功但无法发消息求助

Let’s walk through both your approaches to get messages flowing from your Raspberry Pi 3 to Kapua. I’ve debugged plenty of these integration hiccups, so let’s start with the Kura setup since that’s where you’re hitting the wall.

1. Fixing Kura Example Publisher Failures (Connected but No Data) #

You mentioned you followed the Kura-Kapua connection guide and got the link working—great, so the base connectivity is there. Now let’s zero in on why messages aren’t going through:

Double-Check Device & Connection Configs #

First, confirm your Kura cloud connection settings match what Kapua expects:

• Kapua Endpoint: Use the local IP address of your Kapua server (not localhost—Kura runs on the Pi, so it needs to reach the server over the network). Default MQTT ports are 1883 (unencrypted) or 8883 (encrypted).
• Credentials: Make sure the client ID, username, and password in Kura’s cloud connection exactly match the device you registered in Kapua. Even a typo here will block messages, even if the connection shows as "connected."

Validate Example Publisher Bundle Settings #

Head to the Kura Web UI (http://<your-pi-ip>:8080) and navigate to the Example Publisher bundle’s configuration page. Tweak these settings:

• Topic: Kapua expects topics in a specific format, like kapua-sys/<your-kapua-account>/<device-client-id>/event. If you’re using a custom topic, ensure Kapua’s device or account has permissions to publish to it.
• Payload: Start with a super simple, valid JSON payload like {"temp": 25}—avoid special characters or malformed JSON, which Kapua might silently reject.
• Publish Interval: Set it to 5 seconds instead of a long interval so you can quickly test if messages come through.

Dig Into Kura Logs for Clues #

SSH into your Raspberry Pi and tail the Kura logs to catch real-time errors:

tail -f /var/log/kura/kura.log

Trigger the Example Publisher to send a message, then look for lines like:

• Message rejected by server: Indicates permission issues in Kapua.
• Invalid topic format: Means your topic doesn’t match Kapua’s requirements.
• Payload validation failed: Points to malformed data.

Check Kapua Server-Side Settings #

Log into the Kapua Web UI and verify:

• Your device shows as Connected under the Devices tab.
• Navigate to the device’s Messages or Events tab to see if any messages are being received (sometimes they’re there but you missed them!).
• Confirm the device’s role has the device_message_publish permission—Kapua’s default roles might not include this, so you may need to adjust permissions in the Accounts section.

2. Direct Raspberry Pi Publishing to Kapua #

If you want to bypass Kura and send messages directly, using Python’s paho-mqtt library is a reliable method. Here’s how to set it up and debug:

Install the MQTT Client #

First, install the paho-mqtt package on your Pi:

pip3 install paho-mqtt

Test with a Minimal Script #

Create a simple Python script (kapua_publish.py) to send test messages:

import paho.mqtt.client as mqtt
import time

# Replace these with your Kapua details
KAPUA_HOST = "192.168.1.100"  # Your Kapua server's local IP
KAPUA_PORT = 1883
CLIENT_ID = "raspberry-pi-3-device"  # Match Kapua's registered device ID
USERNAME = "kapua-username"
PASSWORD = "kapua-password"
TOPIC = "kapua-sys/my-account/raspberry-pi-3-device/event"

def on_connect(client, userdata, flags, rc):
    print(f"Connected to Kapua with result code: {rc}")
    # rc=0 means success; rc=5 means invalid credentials

client = mqtt.Client(client_id=CLIENT_ID)
client.username_pw_set(USERNAME, PASSWORD)
client.on_connect = on_connect

# Connect and start the loop
client.connect(KAPUA_HOST, KAPUA_PORT, 60)
client.loop_start()

# Publish test messages every 5 seconds
while True:
    payload = '{"temperature": 22.7, "humidity": 48}'
    result = client.publish(TOPIC, payload, qos=1)
    # Check if publish was successful
    if result.rc == 0:
        print("Message sent successfully")
    else:
        print(f"Failed to send message: {result.rc}")
    time.sleep(5)

Debug Direct Publishing #

Run the script and watch the output:

• If you get "Connected with result code: 0" but no messages show up in Kapua, double-check the topic format and Kapua permissions (same as the Kura steps above).
• If you get connection errors, test if the Kapua port is open with telnet <kapua-ip> 1883—if it fails, check the server’s firewall settings to allow inbound MQTT traffic.

Quick Network & Firewall Checks #

Don’t overlook the basics:

• Ensure your Pi and Kapua server are on the same local network and can ping each other (ping <kapua-ip> from the Pi).
• Disable any temporary firewalls on both devices while testing to rule out blocked ports.

内容的提问来源于stack exchange，提问作者Ahmad Arif