Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

MQTT Client Gateway

b0rmann last edited by
Reply Quote 2
1 Reply Last reply
gregl Hero Member last edited by

very tidy!
Reply Quote 0
1 Reply Last reply
rtenklooster last edited by

Nice, looks neat, are you using the ws5100 or the enc28xx?
Are you willing to share the pcb (eagle / fritzing / etc. ) files?
Reply Quote 0
1 Reply Last reply
b0rmann last edited by @rtenklooster

@rtenklooster
ws5100.
share... a bit of later.
I had to fix some little bugs.
Reply Quote 0
1 Reply Last reply
hek Admin last edited by hek

This post is deleted!
Reply Quote 0
1 Reply Last reply
TommySharp last edited by

Very cool! Any more detail you can give on this setup?
Reply Quote 0
1 Reply Last reply

6
Posts

9086
Views

Log in to reply

Suggested Topics

Communication problems between MQTT Gateway (OrangePi) and Node (Arduino Nano)
Troubleshooting • gateway mqtt nrf24 arduino nano communication problems orangepi • • gammlerstyle

7

1
Votes

7
Posts

756
Views

Hi, for everyone who reads all of this, forget about the last few posts. I don't know why it works even when the Interrups are masked out on the radio, but it works now. The error I had occured because of the config of the OrangePi-Gateway. I removed: --extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_RF24_BASE_RADIO_ID=\(0x00,0xFC,0xE1,0xA8,0xA8\) -DMY_DEBUG_VERBOSE_RF24" and wrote: --extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_DEBUG_VERBOSE_RF24" Now I think I have an working OrangePi-Gateway without signing but with interrupt enabled. If there are new problems I will come back here. The next step for me is to activate signing again and bring the node into homeassistant.
MQTT Client Gateway / Node Controller / OTA
Hardware • mqtt ota • • CrankyCoder

50

1
Votes

50
Posts

14275
Views

can you login to the mqtt server with any mqtt client for computer (like mqtt spy or similar)?
MQTT gateway freezes on reboot/powering off and back on.
Troubleshooting • arduino gateway mqtt raspberry pi uno • • kunall

2

0
Votes

2
Posts

1553
Views

I think the something about order of initialisation was changed that fixed this problem. Try 1.4.1
Switching from v1.5 MQTT gateway to ESP8266 MQTT Client gateway
OpenHAB • mqtt esp8266 openhab • • mbj

18

2
Votes

18
Posts

8080
Views

@DirkB19 Think you will get another advantage by changing as well - must be a lot easier to monitor the MQTT messages when topic clearly shows the difference.
HomeGenie via MQTT
HomeGenie • mqtt homegenie • • Cpt Jack

3

1
Votes

3
Posts

6201
Views

Any updates?
[Solved] MQTT gateway problem
Troubleshooting • mqtt ethernet mosquitto mysensors 2.0.0 • • pinkkoff

13

0
Votes

13
Posts

5623
Views

nevermind. now after all upgrades AND BATTERY CHANGE to sensebender it's all fine
MySensors MQTT 'dialect' optionally Homie
General Discussion • mqtt • • Peter Loeffler

11

0
Votes

11
Posts

116
Views

Perhaps my definition about "controller", is a bit broad here. What could be done, is to have a thin "controller", that receives MQTT from the existing gateway, hands out IDs if they are requested from a new node, and translate the message into homie compliant topics. That is all it has to do, should not care about the rest of the automation at all. Should also be able to translate back from homie compliant to mysensors. This could be written in python, c#, javascript, rust etc. The benefit is that you have (relatively) easy editing of configurations at hands, without re-uploading sketches to your gateways / nodes, if you decide that node X should be named Y instead. And I am in no way trying to treat anyone as a fool!

57
Online

11.4k
Users

11.1k
Topics

112.6k
Posts

Copyright 2019 Sensnology | Forum Guidelines | Privacy Policy | Terms of Service

1 / 1