General Discussion

Thank you. I will try this and report back.

@rickmontana83 have a look at http://zbar.sourceforge.net/ for example...

You'll find plenty of multi sensors examples here on the forum.

Well, do not share any genes with that guy. In fact, I'm a sport-analfabet. [image: 1435211652481-sports_cheat_sheet.png] https://xkcd.com/1107/

@Cliff-Karlsson I is getting a little off-topic but the Ninja Spheres are open-source and should be able to act as a controller (i.e. gateway between Wifi/LAN and ZigBee. If you look for something out of the box than MySensors is probably not the way to go..

Just my $0.02... Be careful with any while loops that could go on forever under "perfect storm" conditions. It's usually a safe bet that eventually your device will get into a state where comms will fail forever. If you're stuck in a while loop waiting for a successful send then you have no chance to detect or correct the error, and given how tricky it is to debug Arduinos you'll probably never figure out what went wrong. The device will just go silent, and a little while later the batteries will run out (because it's sitting there trying to send over and over). Do yourself a favor and put a fail-safe && retries++ < MAX_RETRIES clause on your while loop. This doesn't speak directly to your case, but in a broad sense my assumption going in to any wireless design is that packets will be dropped, so I always design with that constraint in mind, rather than trying to design a system where no drops occur. For example, you might consider adding a "resync" timer that sends the current state regardless of changes every so often. So even if something is dropped you have a bounded amount of time where things are in the wrong state. I do this with my presentations: Every 5 minutes my sensors retransmit all presentation messages just in case the controller missed the first set, or the controller reset, or whatever... Handling lossy comms is not usually too hard if you aren't trying to back-engineer that into a system that was designed with the assumption that messages would always succeed. Incidentally, this is more or less the same as "UDP" vs "TCP" networking, if you've ever worked in that realm. So strategies would overlap pretty nicely.

@Tango2 I had been doing this a different way until I noticed the GW should be able to do it. BTW, It is only working on one node, not sure why :(. Anyway, my alternate solution allows be to send "settings: to the nodes. For example, change the loop time or measurement unit. This is not the complete code, just the relevant parts (hopefully). void setup() { gw.begin(incomingMessage, nodeID); } void loop() { gw.process(); } void incomingMessage(const MyMessage &message) { if (message.type == 97) { Serial.print("Recvd Time"); Serial.println(time); timeReceived=true; } if (message.type == 98) { int reqsleep = atoi( message.data ); SLEEP_TIME = reqsleep*1000; Serial.print( "Changing sleep to: " ); Serial.println( String(reqsleep) ); } if (message.type == 99) { int requnit = atoi( message.data ); Serial.print( "Changing units to: " ); if(requnit == M){ metric = true; Serial.println( "metric" ); } else { metric = false; Serial.println( "imprerial" ); } } } Using this code, I can send things from openhab, or any serial command I suppose. My openhab rules Send Units: sendCommand(Arduino, "101;99;1;0;99;M\n") Send Time: var Number time1 time1 = now().getMillis() / 1000 sendCommand(Arduino, "101;97;1;0;97;" + time1 + "\n")

WHOO Everything seems to be working now:) //Mathias

:flushed: :satisfied:

My setup looks like this: MQTT Client Gateway <-> mosquitto mqtt server <-> OpenHab With this setup you can have multiple MQTT Client Gateway (with different topics).

thanks for the corrections

There isn't any official page for this yet as this has mostly been experimental features. We should probably set one up at some time. To send out an OTA firmware I would recommend using the MYSController which has a nice GUI for it. But you still need to compile your code and grab the hex-file to send. All this isn't exactly beginner-level stuff. Would have been nice if someone could wrap all this up and incorporate it in the Arduino IDE or something.

thanks for the help.. is there a way to send.msg directly to another node without mucking with "MyMessage". ie.. sent a msg on the fly to fire a relay on another module. i have looked through the api and don't really understand how i can send it with out upsetting the rest of the sketch. thanks again hope it makes sense. Phil

@edweather said: http://www.mysensors.org/build/uv The documentation on site is wrong. A0 is the correct pin. Thanks for reporting, I'll update.

Thanks - I will give it a try.