@Yveaux pff, it's clean room ESD class!

@Samuel235 It would be possible, I am planning to implement a GPS, and wireless information would be really nice, 'Hi! I'm stuck at XXXX' :)

There is a small problem though, not enough IO's, so we probobly need to hack and add one more CPU (atmega? ;) that uses the 8 io to the keypad and send data serially between the cpu's (decoding keypad in atmega, send seriell, and tada 7 free io's! :) Plenty enough for wireless chips!

regarding GPS I think I can use the built in USB in the battery compartment, no major mod required for it. :)

Hello everyone!

It's fun seeing this thread alive again!

Sorry I havn't been here for a long while, in the picture you'll see what have been keeping me occupied.. (the orange lawn mower, I'm reverse-engineering it!) and I also moved over from Arduino, atmega328p to esp8266 devices and more advanced cpu's (arm, cortex etc) and 'real' build enviroments..

If there is any interest in my project, https://hackaday.io/project/6717-landlord

The picture pretty much explains how my brain works.. I really need to clean up, might add another picture after that. Behind the mower two rigol devices are hiding, a scope and a p-psu.

I like this one, It's not fanless but hackable and 3 channels; http://www.meilhaus.de/en/rigol+dp832,i2.htm

I have been away for a while but it seams quite some of you are experiencing problems, I'll try to take a look at it. If you find any more details, please let me know!

I just wanted to say hello again to everyone. I had to disappear for a while. Just had too much for my brain to handle. So all my automation project were on halt but will be continued again.

I know there are lot of bugs in this GW and I will hopefullt start developing soon again. Just write your experience you had so far and I'll try to keep up :)

//Damme

@John Could you send me log from MQTTgateway also? (or tcpdump)

@adrianmihai83 Sketch-name was a bug that I fixed in development branch, thought @hek updated master branch also. I can post the fix later on in here.

@adrianmihai83 "home/openHAB/out/Temperature_GF_Corridor/state" is probobly long string, 47 chars. I have not investigated exacly how long it can be but keep it short. And the adress layout is also wrong, is should be something like MyMQTT/21/1/V_LIGHT . MQTTGateway is not compatible with the mosquitto broker you're using.

Or GPS for a very accurate time :)

Hey guys!

I was thinking about AC/DC adapters. And you all should know about safety of using cheap chinese one's. They can actually kill you if they are bad built... So my thought was to test a couple of different one's and look inside them. Right now I use old AC/DC 5v adapters with 5mm plug from old routers and stuff so they should be all ok.. :)

But I don't know if someone already did some research of this? I was mainly looking at adapters with a round 5mm plug, and not USB but I know some of you are using USB adapters too.

Lets gather photos of adapters in this thread!

//Damme

@John then node is started, There was a bug not processing that message which is fixed now.
hasn't been pulled to official yet but can be found at https://github.com/Damme/MQTTGateway/commit/f10843f5efd9c37900624fe57275be11c69e3942

@goose I've fixed this bug, I will do some tests tomorrow before I upload the changes.

http://forum.mysensors.org/topic/303/mqtt-broker-gateway/

@John 'started' is only a internal log message, I've changed how that part works.

I've also fixed a couple of bugs and will test the changes tomorrow before I publish them.
New functionallity there user can choose of MQTT should translate ID to V_TYPE or not too.

@goose I'm a bit busy atm but I'll look at it later!

I had to put my project in the trash bin.. There is not enough RAM in the atmega328 to fit mysensors and SD-lib :) Tried 3 different versions..Too bad..! I could only transmit one package before SRAM got overrunned.

@ServiceXp Now when you sayit... I had a wireless mouse that lowerd my reception. A cheap brand, I did't like it and everytime a sensor transmitted the mouse got laggy.

@ddluk I run my 5v 16mhz at 3.3v.. Direcly off 2 AA batteries too (I think the reported voltage last I checked was 2.88v, Still works just fine. :) (But I have flashed bootloader to disable brownout voltage)

@ServiceXp One major stability change I did was using shorter wire bewteen radio and arduino.

@ToSa I finally figured out why my OTA bootloader didn't read any answers from my GW (Both on I_FIND_PARENT and I_ID_REQUEST) - The answers came to quick! First I tried hardcode a delay 125ms on the GW and it worked, so I changed the code on send write to the following and now all messages arrive. Been testing it for a couple of reboots now. I'm using 5v (at 3.3v) and 16MHz
edit; noticed it misses packages sometimes now but not close to 100% like before, more like 5% now. I'llinvestigate futher then I'm trying to upload data.

  static uint8_t sendAndWait(uint8_t reqType, uint8_t resType) {
  	msg.type = reqType;
  	for (uint8_t i = 0; i < 10; i++) {
  		sendWrite(msg);
  		for (uint8_t j = 0; j < 20; j++) {
  			for (uint8_t j = 0; j < 100; j++) {
  				uint8_t pipe;
  				boolean avail = available(&pipe);
  				wdt_reset();
  				if (avail && pipe<=6) {
  					read(rmsg.array,pipe);
  					if(!(mGetVersion(rmsg) == PROTOCOL_VERSION))
  						continue;
  					if (rmsg.destination == nc.nodeId) {
  						if (mGetCommand(rmsg) == C_INTERNAL) {
  							if (rmsg.type == I_FIND_PARENT_RESPONSE) {
  								if (rmsg.data[0] < nc.distance - 1) {
  									nc.distance = rmsg.data[0] + 1;
  									nc.parentNodeId = rmsg.sender;
  									eeprom_write_byte((uint8_t*)EEPROM_PARENT_NODE_ID_ADDRESS, nc.parentNodeId);
  									eeprom_write_byte((uint8_t*)EEPROM_DISTANCE_ADDRESS, nc.distance);
  								}
  							}
  						}
  						if ((mGetCommand(rmsg) == mGetCommand(msg)) && (rmsg.type == resType))
  							return 1;
  					}
  				}
  				delaym(1);
  			}
  		}
  	}
  	return 0;
  }