I've been able to get MySensors working with HomeGenie using the MQTT gateway. It doesn't have two-way communication or software-based pairing yet, but I'll work on those in the future.
@ericvdb
Yes, I know about the 5V. But the adapter brings it down to 3.3V for the radio, that is the reason for using it and the adapter is equipped with the AMS 1117 3.3V chip. Seems to work OK but I really do not have any hard facts to prove it.
One thing I may test is to wire the 5V also directly to this adapter instead of taking it out from the Arduino 5V pin. This is to find out if this Arduino Nano clone might have too small capacity for feeding the radio at certain occasions.
Might be helpful for somebody... Things configuration for OpenHab2:
Bridge mysensors:bridge-eth:gateway_2 [ ipAddress="192.168.178.50", tcpPort=5003, sendDelay=200, enableNetworkSanCheck=true ] {
/** define things connected to that bridge here */
light sonoff01 [ nodeId="0", childId="0", requestAck=true ]
}
Now the RPi based on a new install of Raspbian Jessie, OpenHab 1.8.0 and Mosquitto is up and running and the ESP8266 MQTT client does connect without any problems. I have not changed anything in the code but Mosquitto is now based on the RPi repository for Jessie and not the mosquito_wheezy one. That seems to have fixed it so those versions are likely different but I have not put any time into checking this.
@alexeinz figured it out, apparently had to add experimental and get latest mosquitto for the conf file to work correctly , now the bridge is working perfectly
--- broker.conf file in /etc/mosquitto/conf.d
the topics coming from gw will appear under sensor/# on mosquitto
connection MMQTTtoSensor
address 192.168.1.234 <-gw ip
clientid MyMQTT
cleansession true
notifications true
topic # in 2 sensor/ MyMQTT/
Qu3Uk,
I did get a chance to test with a Fitbit recently. It technically worked, but not all that well. The thing is, the Fitbit only advertises every 2 seconds so latency is a bit high. But worse, its apps really want to be connected to it often to sync; and whenever it's connected, it stops advertising and the detector then can't pick it up.
TommySharp,
At this point I don't plan to modify the board much but having it read environmental sensors would be a cool feature!
For that, would be nice to make little beacons that read sensors and advertise/broadcast the readings every few seconds. Then they could be very low-power, run on coin-cells for months, and could be placed anywhere instead of needing it to be hooked up to USB power like the main board is. Like these: https://sen.se/peanuts/ I'm curious if it could read them.
As for enclosures, I know. I would love to have some nice ones but at this point I'm making too many boards to 3D print enclosures, but too few to afford injection-molding tooling to make a custom case.
@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.