Discussions about projects created on OpenHardware.io.
373
Topics
7017
Posts
@yveaux
One button is reset, the second button is multifunctional. Depends on how many seconds you hold this button. In my program, I use this button to connect via air to other devices and to transfer the device to receive settings (data transmission intervals, led operation and so on). This button is not used in my test sketch
An example of direct connection between devices (without the use of controllers, without changing the SOFTWARE) is my development, which is in the testing stage is the controller of Underfloor heating. This device controls the five contours of the Underfloor heating. Up to 10 such temperature sensors can be connected to this device simply by pressing the connect button. Maximum of two temperature sensors per one relay channel.
PCB design modification | EFEKTA CETA | MySensors – 00:25— Андрей Ламченко
EFEKTA CETA | First HW Test | MySensors – 01:21— Андрей Ламченко
EFEKTA CETA | SW Test2 – 01:32— Андрей Ламченко
Examples of direct connections (micro-networks) based on MySensors can be found here:
Стенд элон мод | Реле, выключатели | MySensors 2 – 01:09— SMART BOX
Test software - Happy nodes | MySensors | Switch | StandAlone mode | Master - Slaves mode – 03:45— Андрей Ламченко
Micro network 2 | MySensors – 01:53— Андрей Ламченко
Seems to be a neat tool to "automatically" convert big part with many pins from a datasheet in pdf format to KiCad's .lib file.
Linux and Windows are supported. Haven't tried it yet, but I think it's cool how many tools opensource community has made and keep inventing very convenient stuff.
https://github.com/Robotips/uConfig
Hello, i have been trying to get the mysensors MQTT GW online for 3 days now with no success.
I can see the messages appearing on the mosquitto broker but cant get the gateway online in paperUI. I have followed the steps in the first post on this page.
[10:43:27] openhabian@openHABianPi:~$ mosquitto_sub -u openhabian -P xxxx -p 1883 -v -t 'mygateway1-out/#'
mygateway1-out/107/3/1/0/0 29
mygateway1-out/107/0/1/0/0 86
mygateway1-out/107/0/1/0/0 87
mygateway1-out/107/3/1/0/0 28
mygateway1-out/107/3/1/0/0 32
mygateway1-out/107/2/1/0/0 19.3
mygateway1-out/107/1/1/0/1 33.3
mygateway1-out/107/3/1/0/0 38
mygateway1-out/107/2/1/0/0 19.4
mygateway1-out/107/2/1/0/0 19.3
mygateway1-out/107/2/1/0/0 19.4
mygateway1-out/107/2/1/0/0 19.3
mygateway1-out/107/2/1/0/0 19.4
mygateway1-out/107/3/1/0/0 37
mygateway1-out/107/3/1/0/0 38
mygateway1-out/107/3/1/0/0 37
mygateway1-out/107/3/1/0/0 38
mygateway1-out/107/3/1/0/0 37
mygateway1-out/107/3/1/0/0 38
mygateway1-out/107/3/1/0/0 37
mygateway1-out/107/2/1/0/0 19.4
mygateway1-out/107/1/1/0/1 33.5
mygateway1-out/107/3/1/0/0 38
Here is my MQTT.cfg file:
#
# Define your MQTT broker connections here for use in the MQTT Binding or MQTT
# Persistence bundles. Replace <broker> with an ID you choose.
#
# URL to the MQTT broker, e.g. tcp://localhost:1883 or ssl://localhost:8883
mqtt:mosquitto.url=tcp://localhost:1883
# Optional. Client id (max 23 chars) to use when connecting to the broker.
# If not provided a random default is generated.
mqtt:mosquitto.clientId=openHab
# Optional. True or false. If set to true, allows the use of clientId values
# up to 65535 characters long. Defaults to false.
# NOTE: clientId values longer than 23 characters may not be supported by all
# MQTT servers. Check the server documentation.
#mqtt:mosquitto.allowLongerClientIds=false
# Optional. User id to authenticate with the broker.
mqtt:mosquitto.user=openhabian
# Optional. Password to authenticate with the broker.
mqtt:mosquitto.pwd=xxxx
# Optional. Set the quality of service level for sending messages to this broker.
# Possible values are 0 (Deliver at most once),1 (Deliver at least once) or 2
# (Deliver exactly once). Defaults to 0.
mqtt:mosquitto.qos=0
# Optional. True or false. Defines if the broker should retain the messages sent to
# it. Defaults to false.
mqtt:mosquitto.retain=false
# Optional. True or false. Defines if messages are published asynchronously or
# synchronously. Defaults to true.
mqtt:mosquitto.async=true
# Optional. Defines the last will and testament that is sent when this client goes offline
# Format: topic:message:qos:retained <br/>
#mqtt:mosquitto.lwt=<last will definition>
My bridge thing:
Logs:
2019-01-21 11:22:57.494 [ERROR] [rotocol.mqtt.MySensorsMqttConnection] - No connection to broker: tcp://localhost:1883
2019-01-21 11:22:57.510 [INFO ] [ateway.MySensorsNetworkSanityChecker] - Network Sanity Checker thread stopped
2019-01-21 11:22:57.524 [hingStatusInfoChangedEvent] - 'mysensors:bridge-mqtt:a07a6f31' changed from INITIALIZING to OFFLINE
2019-01-21 11:22:57.527 [ERROR] [rotocol.mqtt.MySensorsMqttConnection] - Failed connecting to bridge...next retry in 10 seconds (Retry No.:0)
I'm confused, am i or am i not to install mqtt-binding in paperUI?
I allso read about renaming org.eclipse.smarthome.mqtt.cfg to org.eclipse.smarthome.mqttbroker.cfg. Is this the file mqtt.cfg in the services folder of my configuration?
Allso i'm not sure what mqtt-eventbus.cfg actually configures. Is this part of mqtt-binding? (wich i preveously installed and now removed). anyway here is its contents:
# Name of the broker as it is defined in the openhab.cfg. If this property is not available, no event bus MQTT binding will be created.
broker=localhost:1883
# When available, all status updates which occur on the openHAB event bus are published to the provided topic. The message content will
# be the status. The variable ${item} will be replaced during publishing with the item name for which the state was received.
statePublishTopic=mygateway1-out
# When available, all commands which occur on the openHAB event bus are published to the provided topic. The message content will be the
# command. The variable ${item} will be replaced during publishing with the item name for which the command was received.
commandPublishTopic=mygateway1-out
# When available, all status updates received on this topic will be posted to the openHAB event bus. The message content is assumed to be
# a string representation of the status. The topic should include the variable ${item} to indicate which part of the topic contains the
# item name which can be used for posting the received value to the event bus.
stateSubscribeTopic=mygateway1-in
# When available, all commands received on this topic will be posted to the openHAB event bus. The message content is assumed to be a
# string representation of the command. The topic should include the variable ${item} to indicate which part of the topic contains the
# item name which can be used for posting the received value to the event bus.
commandSubscribeTopic=mygateway1-in
I hope someone can help me, I'm still very new to the concept of mqtt. I come from a background of arduino programming so this is all very confusing to me.
I'm running openhab 2.4.0-1 stable release (openhabian) an mysensors binding 2.4 on RPI3
Any help would be appreciated, I've been braking my head on this for three days now.
If I use a serial or ethernet gateway everything works like a charm so it must be a problem with my mqtt configuration
