I can not select the serial port yet, so could not test it further, likely have to do some mapping in wine.

Took some time to find out but after:

• Adding a mapping from the Linux serial port to the Wine dosdevice configuration:
  ln -s /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_* ~/.wine/dosdevices/COM3

• Adding to ~/.wine/system.reg:

    [Hardware\\Devicemap\\Serialcomm] 1231984861
    @=""
    "Serial0"="COM1"
    "Serial1"="COM2"
    "Serial2"="COM3" 

I could start MYSController.exe and select COM3 and get:

But after pressing OK things look to work however:

@tekka : Thanks!

I am wondering if with a setup as you point out above you can really have full duplex in real life scenarios.

The two antennas are very close together and I think the isolation is less than 10 dB. The architecture of the receiver is that it has a wide-band LNA so suppose you are receiving a signal at -70 dBm and the other radio is transmitting at 0 dBm. With 10 dB antenna isolation that means it couples in at -10 dBm.

The -10 dBm (although on a other frequency) will clip the wide-band LNA so that you will no longer be able to decode the -70 dBm wanted signal anymore.

I can claim around 50% increase in transfer rate speeds and even better improvement in round-trip time between 2 nodes.

I am surprised... What kind of distance is there between the two nodes?

@murdog: You should probably also have a look at the New library to read Arduino VCC supply level without resistors for battery powered sensor nodes that do not use a voltage regulator but connect directly to the batteries thread.

If you want to make the code generic, you should have the code measure the VCC and scale the measured value according to what you read for VCC.

I am not sure if I can follow you.

Is there a way to enable the controller to be the one that searches for the sensors?

Why would you want to do that, sensors will have to report eventually their values to the gateway/controller, so I see no problem having them register with the gateway/controller.

This would allow for the sensor to be smaller by having the large antenna be placed on the controller.

A large antenna is most of the times a very directional antenna, is that what you mean?

If you want something simple, see http://gizmosnack.blogspot.se/2014/11/power-plug-energy-meter-now-wireless.html.

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.

Currently I'm using rechargeable AAA, which will be switched soon, as the sensor is working fine.

Why would you switch the batteries?

5.2V / 4 = 1,3V so still quite full.

These batteries are low-leakage batteries so provided the initial charge is fine and current consumption the lifespan should be good and at least 50% of that of good alkaline batteries

If the sensor and the gateway are at the same level or about the same level I think using a half-wave dipole or "rubber duck" antenna pointed vertically is a good idea.

That will focus the energy in the horizontal plane and not into the ground or to the air giving about 2 dBi of gain.

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.

@shabba You ask for the plane for the antenna but to for that it is handy to describe your house or setup, one or multiple floors, concrete walls etc?

@rvendrame:

• The ZWave paper you point to describes a problem implementation, not the protocol itself it seems to me:

The root cause of this issue was lack of state validation
in the key exchange protocol handler programmed in the Z-
Wave door lock firmware.

• Yes, if you lose your normal key anybody that knows to which lock it belongs can break in.
• But, if your key has no information on to which lock it belongs to the risk is small, the same is true for a remote.

You should not typ "\n"!
It means that you should press enter on your keyboard.

On Linux I saw that I have to send "\r\n" instead of "\n".
"\r\n" (Carriage return, Line feed) is the Windows return, "\n" only the Linux return.

What kind of protocol is the 433 MHz RF running?

@tekka : Thanks, things work now fine!

Did do some more experimenting using a sort of Ethernet gateway (actual the relayed Serial gateway data) and see that MYSController.exe can connect but once it prints the first data it gives the "File not open." error and no further data is printed.

So it does not look like a serial port issue but something else.

Did not know Lazarus but it looks pretty good!

I have AutoFW disabled.

The funny thing is that things do not work at all if I do not get the "File not open" error.
No, rebooting the gateway does not make the "Gateway startup complete" message re-appear.

Did watch the serial port using interceptty and see data is passed so it seems like Wine is not passing it.