I will just leave that here for other like me that wondered for hours why they could flash their sonoff, but it did not react once plugged to the main.

You need to setup your arduino with DOUT as flash mode.
Other mode will flash without errors, but the device will appear bricked.
My settings where:

Shenanigans like that makes me happy to work with Linux. But if I had to buy it again, I'd use an ch340 based usb-ttl device just to avoid ftdi chips.
Something like this: http://www.aliexpress.com/item/CTS-DTR-USB-Adapter-Pro-Mini-Download-cable-USB-to-RS232-TTL-Serial-ports-CH340-Replace/32236136728.html?ws_ab_test=searchweb201556_6,searchweb201602_5_505_506_503_504_301_10032_10020_502_10001_10002_10017_10005_10006_10003_10021_10004_10022_10018_10019,searchweb201603_2&btsid=dbfef4d9-1a89-4f88-9906-180148e01e92

Glad I was able to help.

I'm a bit blind here, but your issue seems to be that you are trying to send a raw float value, without encapsulating it inside a message.
Looking at the example, in the 1.5 version it is:

gw.send(pressureMsg.set(pressure, 0));

Looking at the 1.5 API (http://www.mysensors.org/download/sensor_api_15#MyMessage), creating the message from a float should be

MyMessage& set(float value, uint8_t decimals);

So, you should not use

gw.send (PSI);

but

//declare and init the message
MyMessage msg(BARO_CHILD, V_PRESSURE);
//set it's content
msg.set(PSI,4); //float value with a 4 numbers after decimal precision
//and send the message
gw.send (msg);

What is your error message?
In your loop, this looks wrong:

Voltage = (5./1023.)readValue; 

Are you sure you didn't miss an operator or something ?

You are also missing a presentation of your node, and I don't see anything declaring the radio to be used.
What are you trying to do?

Ok, I feel pretty dumb not to have thought of it before, but I've found the issue.

For the sake of anyone running in the same issue, if you are running an ad blocker, try to disable it first.
Looking at the request in Chromium, it said "ERR_BLOCKED_BY_CLIENT"

Turning off the ad blocker resulted in a dashboard as you would expect it.

Sorry for bothering you for something I should have thought of, and thank you for your support.

@jkandasa In order:

• Yes, they are linear
• 3 nodes. 2 nodes have 3 sensors (humidity, temperature and luminosity). 1 node just have humidity and temperature.
  They implement respectively V_HUM, V_TEMP and V_LIGHT_LEVEL
  They all basically are the DHT sensor, and I've added a LDR to report a relative luminosity in rooms.
• I didn't upgraded. I run the 0.2 version on 1 machine, and have tried on another the 0.3
  I downloaded the 0.3 that is available on the site. The file name is mycontroller-standalone-0.0.3-alpha1-bundle.tar.gz
  So no, it's not the snapshot and it was a clean install.
  They both use a MQTT broquer to get data (Latest version of mosquitto).
  I did not use the built in MQTT broker from the 0.3 version
• I'm running on Linux, and usually run Firefox. I tried to access mycontroller with Chromium with the same results.
  This is the dashboard initially:
  
  The strange thing is that I don't see a "metricsData" request in the initial display of the page.
  All the bootstrapping happens in a few ms, and then nothing for the next 6 minutes.
  
  And then, suddenly at the 7th minute, several metricsData request are coming through:
  

My dashboard is then ok, until I reload the page or naviate to another screen.

Hoping that this is relevant to you:
Java version:

openjdk version "1.8.0_72-internal"
OpenJDK Runtime Environment (build 1.8.0_72-internal-b15)
OpenJDK 64-Bit Server VM (build 25.72-b15, mixed mode)

I tried to run it on a similar system (the one running the 0.2 version) with the same symptoms.
I hope it's enough data to help you.
Thanks.

Hello Jkandasa,

First, thank you very much for all the work you have put in your controller, it's a nice product and simple to have working.
I just have tried this last version, but I cannot get the dashboard to display a graph of sensor, like the details of the previous action board was doing.
To be more precise, I cannot get it to display a linear graph without having to wait for several minutes.

I can see all the numerical values from my sensors, but on the linear graph I only have a rotating "please wait" circle.
They stay that way, I think, until (I think) every sensors have updated their values.
I say that, but it's a feeling, not a certainty.
The thing is, if the dashboard is displayed correctly, navigating to any other screen and getting back to the dashboard populates it again with the waiting symbols, for a few minutes.

Is this something known?

The enclosure is very nice too.
Hand made ?

@Terence-Faul not that I know of. And domoticz MQTT support is less than stellar. You cannot configure the topic(s) it listen to, and you need to go through node-red (a node.js app) to transform what the gateway sends.

I honestly couldn't be bothered to install it, and went straight to mycontroller.org.
I might try it out though, as I have a couple of lifx led bulbs that domoticz supports.
Or (probably) I'll wait for openhab 2.0 to reach stable.

@carlierd Ok, I have a couple more in the mail, I'll try this for the next batch. Thanks.

@carlierd Is the resistore the element marqued 102 above the led? And I don't see how this is easier.
My biggest issue was to put my pliers between the led and the adjacent element and not have the magnifying glass move too much while applying the iron tip on the side of the led.

@Terence-Faul The ethernet gateway speaks with the controller directly over TCP.

The MQTT gateway will publish messages from the sensors to a MQTT broker.
The broker is a software that you must install and run that comes in between of the gateway and the controller.
The controller must also connect as a client to the MQTT controller, and it subscribes to the messages pushed by the MQTT gateway.
The controller too can send a command through the broker, that the gateway will see and forward to the node.

The biggest advantage of the MQTT (for me anyway) is that I can use a PC or Android client to also connect to the broker and look at what goes in and out of the gateway.
It allow me to also test different controllers (openhab, domoticz) without touching the one I run usually (mycontroller.org).

Thank you all for chippin in.
I just desoldered the led on one of my last units, and it still boots afterward.
My sight and big fingers are sadly the biggest obstacle in this operation, but now at least I know it can be done.

I was able to take a macro shot, and effectively, I can see a track underneath the led.

I think I'll let the voltage stabilizer untouched, and continue to feed stabilized 3.3V through the VCC pin.
The led was my biggest concern for running the node on battery.

Thanks again everyone!

Thanks for the reply.
I still have 2 units left, so I'll try one this evening.

Hello,

following the "General Tips for Battery Operation", I tried to remove the power led in 2 of my pro mini 3.3V.
One by removing the led (using a small screwdriver as lever) and another by cutting the mark leading to it.
In both cases, this resulted in a board that didn't react anymore to my FTDI programmer.
Both boards where able to be uploaded a simple DHT mysensors sketch prior to the operation.
Evidently, they where not the boards linked from the mysensors pages, I had them from a previous project.
If anyone wonder, this is where I got them: http://www.aliexpress.com/item/Free-Shipping-new-version-5pcs-lot-QFN-Pro-Mini-328-Mini-ATMEGA328-ATMEGA328P-MU-3-3V/32264277091.html

They are obviously clones, and maybe this one doesn't support it, but I still am trying to find a way to get rid of this led.
This got me thinking that I have a few ATmega328P-PU in a drawer.
I'm pretty sure I did burn a bootloader on those, and they seem to be a perfect candidate to have 3.3V low power nodes in my network.
Although, I barely see any occurrences of this solution on the web site or in the forums.
Is there a reason for that, apart being maybe considered too advanced/complicated?
I remember having issue in the past with DHT22 and those on breadboard, giving unreliable results, but I think it was linked to non stabilized power getting below 3V.

I currently am wondering if I should continue with the pro mini boards, or switch to a simpler "boarduino" setup.
And if anyone had a similar issue with removing the led, and could revive the board, I' all hears too.

Thanks.
Tripy.