Feature Requests

The only real difference is the name and magnitude. Hecto Pascal vs Pascal

The capability to send SMS is not really needed in the MySensors library itself, but the Adafruit FONA library works together with the MySensors library (DEV version anyway). I added a sketch which make a node a SMS gateway if it is equipped with a SIM800L module. You can find it on Openhardware.io: https://www.openhardware.io/view/11/ACDCBatteries-capable-atmega328p-board The sketch is available under the design files and is now part of the MySensors library examples (again in the development version only). If you want to get notified of the fact that your internet connection is down, you will need to make something on the controller side to notice this and then send a V_TEXT to the node itself, or change a "switch" on the node, so that it can trigger the sending of a SMS.

thank you all. I'll try to create a working sketch.

The problem is not really concerning RGB to HSV or vice-versa (BTW if you have a working-well RGB to HSV code, i'm interested. I'm currently using the FastLED one ...) The idea (and this is the main reason why HSV ever existed) is to get a easy and natural way to describe colors. For anyone in the world it is easyer to say "I want a red, pale, not so bright" light, instead of a" #FFAA11" light! ;-) ;-) When you are from a controller point of view, talking directly in HSV, allows to easily set a dim level (which is a major feature for a light, isn't it?), and a color (Hue). Devs like the Domoticz ones even dropped the Saturation at this time, but they are currently receiving (and could easily send) H(S)V values. Also most (if not all) javascript color pickers are natively talking HSV. About HSL vs HSV I think this not really important because it is just a story of different gamma correction / color space (if i understand well), and for devices intended as a Light (not as screen), color deviation is not a big issue. I just vote for the most used in related software (arduino lib + Javascripts color pickers), to try to match the requested color as accuratly as possible.

Thanks. Knew this, but esp easy has native support for a wiegand reader, where mysensors has not. Had the software (included access control) up and running, but unreliable; as said before. So I'm searching for a substitute for the esp.

I was just yesterday testing a system I'm going to install on the summer cottage, and noticed that I get hardly 2 meters range. Then I noticed the sketch has 'RF24_PA_LOW' by default. Is it OK/safe etc. to use the highest PA level for the PCB antenna versions of nRF24 ?

Thanks, I'll install a domoticz again to my NAS Synology... I don't have choice if I want to use V_TEXT... ;-) So I don't know how to communique between Jeedom and Domoticz efficiantly, I'll search... Great !...

@HenryWhite said: http://www.mysensors.org/build/battery#measuring-and-reporting-battery-level The main site haven't been updated to show examples using the new style (dev branch). When we release 2.0, I'll update all examples, including this one.

In development branch, doxygen is actively being used to document various aspects of the library. Signing is a good example. You can browse the documentation on the ci server: http://ci.mysensors.org/job/MySensorsArduino/branch/development/Doxygen_HTML

@mfalkvidd Thank you very much for pointing me to the dev branch which now implements nodes on the gateway. Things are evolving really fast here ;-) I'm certainly gonna wait until it reach the master branch to use it "in production". While this is just an excellent news solving the sensor-on-gateway issues, it don't solve/standardize multiple arduinos communication. But maybe this feature is outside of the scope od MySensors, and should be developped independently by extending the Wire.h methods. Any other thoughts?

But you don't have to enable the NRF-radio, if you don't want.

I have a "manually" sketch for relay, you may add any number of relays, choose the PINs you want on Arduino. Of course you are limited by the type of the board you are using. You just have to copy/paste the same code and change the relay number 1, 2, 3, 4 etc: https://github.com/Mihai258/HomeAssistant-MySensors-MQTT/blob/master/Single sensor/MySensorMQTT_REL/MySensorMQTT_REL.ino Of course you have also to take care about already used PINs (some of them are used for the NRF24 module, some for LEDs if case etc).

The sensors offer an analog value, so you have to use one of the Ax input of Arduino. I found an example of implementation here: http://www.homautomation.org/2013/09/17/current-monitoring-with-non-invasive-sensor-and-arduino/ I also plan to use such a device in my automation project in the near future and I am already prepared for that, I published few sketches with analog input usage, people have to use as they want the analog input values.

In the BACnet protocol, the messages are not sent directly, but pushed into an internal state machine that remembers (some) of the previously messages sent (i.e. memorize(_msg); send(_msg); ). The state machine also peeks incoming messages and can trigger a message re-send in case of a missed ACK. the difference with MySensors is that all the messages are numbered, otherwise you would not know which message of the last N sent previously was ACKed, but well.. ACKing the last similar message might be good enough. Anyway @SiLeX : if you want to try, this is not that complicated, (if you don't take into account the STREAMs) it will just costs about (1 status byte + 1 timestamp + 1 frame size) x N ; for N frames memorized.

Probably not over the air - between sensors. But someone could possibly create a XBee gateway communicating using the MySensors protocol towards the controller.

@kr0815 Currently you cannot change the channel dynamically, as it is set to RF24_CHANNEL in MyTransportNRF24::init(). You could change the implementation of MyTransportNRF24::init() and pass the channel as a parameter.

Thanks @sundberg84, I'm already using this method with openhab ;) I will be continue to use it.

Thanks - that makes sense. It's probably short lived - micro processors are coming with more and more memory all the time so in a few years it won't matter at all for most things. Regarding the LED's - so does that mean the "approved" way to handle that is to just go in and edit the MyLeds.cpp file? I was hoping to avoid editing anything in the MS library because it becomes very hard to track source code configurations between different builds.

@drock1985 There are rtc available in the SAMD. But there is no battery backup (yet).