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.
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.
I have a project going with openhab and thethingbox. I only use Mqtt with a combination of nrf24l01 and esp8266 modules. thethingbox server is simply used as a catch all for all mqtt messages from sensors or openhab. i parse all the message coming into ththingbox and take action depending on the message. If my door or window sensor is tripped a message is sent to Twitter. I also send temp and humidity readings to thingspeak and my cell phone reports long and lat coordinates to thingspeak so that my lights can come on as I approach the house. My next project is to setup ip cameras and motion sensors and sent pics to drop box.
Openhab is really not hard, you just have to keep at it, once you get it you will kick yourself for over complicating it
Mike
Actually, it's not 100% MySensors-related, but I have a working setup consisting of iBeacon (either HM10-based or PI-based) and Beecon app.
When Beecon senses the iBeacon it can trigger various actions, eg make http requests or call IFTTT recipes
@scurb This looks very interesting and my factor now to save me from having to create my own :-). I have been planning to do the same thing (although maybe on a smaller software scale) by writing a simple Python server that would pull serial packets off of a gateway arduino (either running mysensors or something I write myself) and pipe this through MQTT to openHAB. I have two questions:
How do you interface with a sensor network? Do you go through a serial connection to read the serial packet format (a,b,c,d)? I see several implementations that put the mqtt client directly on the Arduino, but it seems much cheaper for me to just plug it into a USB port to get a virtual serial port instead of investing in a separate ethernet shield
How does an item configurations look like for a switch in openHAB? I'm looking to build a toggle switch which toggles light on or off every time it is activated, and I cannot really understand how to configure the switch to allow this behaviour for an mqtt input.
Feel free to take the second question with me directly since this might not be very interesting to the others in the forum
sensor id is not the same as node id.
sensor id = 255 is used for internal stuff like id request and battery level for node. You can assign 0-254 to your own attached sensors (to the arduino node).
Although it should not be too difficult to make the MQTT Gateway with WiFi work on hardware and software level it is a bad idea on system level:
WiFi and MySensensor NRF24L01+ use the same 2.4 GHz band and with the antennas close a transmit from one will block the other and vice-versa.
@UglyKidJoe
I have been using OpenHAB and MQTT for a number of years now.
The reason for using MQTT and not just a serial connection from the MySensors GW is partly the flexibility as many have stated previously here. Easy to test, using e.g. the mqtt.fx tool. If you want to know what is going on you simply connect to the MQTT stream and "snoop" on the messages.
Another reason is that I am running three geographical sites on one OH installation. OH is running on a NUC at my home. There is also an MQTT GW here. Two other My Sensors MQTT-GW are running remotely in two summer houses. The three GW connect over internet to a cloud-based MQTT broker and OH connects to the same broker. In that way I do not have to open any ports into my home network for access should I have had a local MQTT-broker at home.
