Feature Requests

@Jan-Gatzke the delimiter is "\n"

If anyone is interested in trying out the implementation using UDP packets sent to the subnet broadcast address, check out my pull request https://github.com/mysensors/Arduino/pull/66

@sigolhi It is already on the list for 2.0.

@tbowmo Thats right. But more imprtantly, the whole purpose of my signing development is to allow sensor nodes to trust the "sender". But this of course chains all the way to the controller, and with the MiOS tunnel, that chains outside the walls and then signing does not matter at all. Anybode with access to my MiOS account (which is hackable) can then access potentially my doorlock. And that would be...bad... I know that MiOS intention is sort of honorable; easily provide remote access to your HA system. However, they should provide better support to opt-out of that option. If I wanted to access stuff remotely, I open a SSH tunnel with my two-factor authentication and then I have total access to my LAN. But we are gliding off topic here :) @epierre basically answered my question and killed the overall topic since my query was if the current HW design could support this. If a much more gateway HW is required, then there are better alternatives to pursue.

@Dirk_H There isn't any limit. But keep the number of hops low if possible.

I'm not sure if you have in mind re=using your hardware with new MySensors based firmware, or if you want to keep your existing RF network and just add a gateway between that and the Veralite/MySensors network. I'm guessing the former, from your questions about arduino compatibility. Board compatibility should be good. You may need to change some pin numbers in the MySensors libraries and/or example sketches to match your jeenode and moteino pinouts. A bigger question is the radio interface. Originally the MySensors library and sensors were designed for the nRF24L01+, but there is an ongoing sub-project to add RadioHead support, including support for the RFM69 - I'm not sure about the RFM12B but you can check. If your RF network is working well, and if you run into any large trouble porting the MySensors system to your hardware (radios), you could also consider creating some kind of bridge or gateway - perhaps MQTT based. An all-MySensors solution (described above) would have some advantages tho.

ty hek, I knew it was possible but trying to get it all in one now will be fun. also got an idea for a dual controller, is this possible? I want to have the ethernet one as the hub, but run around with a portable raspberry pi that also runs something like pi dome but a remote version. I must sound like I am asking for the moon from a community of people donating their time but thought it would be an addition worth while

I would think you could do this by setting up a sensor as a switch. Another one would be set up to communicate with the first instead of sending to the gateway. The first one is made to set itself as "off"(no presence) on the gateway if it hasn't received a ping from the actual presence sensor in the past, say, 5 seconds. When it does see a ping, switch set to on.

PERCENTAGE will come in next release. You'll have to use V_DIMMER for the time being.

You are right, that is a possible solution for my problem. I think changing software should be favoured over changing hardware.

I'm planning on setting up a similar setup to top up a header tank for toilet water from a large tank. I have a couple of floats and a distance sensor. My initial idea was to use the distance sensor to trigger pump but I now think I'm going to use 1 float to trigger the pump when the header thank is low and the 2nd float will be at the bottom the large tank to stop the pump running if there is no water left. I will use the distance sensor to update a display inside the house to show how much water is in the storage tank.

...no .. I know .. but I must explain this .. : I know .. receiver on first upload data for TX Fifo .. and listen .. if receive valid packet then send ack with data from TX fifo . but I mean this : repeater periodicaly contact gateway and udate some easy data .. for example date time , network structure , how many node are in network , if some registered node are visible or not , etc .. and if see gateway .. this is example : my node is not directly connected to gateway .. byt by two repeater .. all repeate every 10minutes ask for gateway just for easy ping only ACK , if receive ACK then know all information what I wrote.. but will know that see gateway .. and update ACK payload .. if my sensor node send data to gateway and don't want ACK .. then received hardware ACK and will know that last 10minutes repeater seen gateway .. yes it's not for 100% .. but wery efective .. to inform all other sensor node but not network load . only sensor node that really need to know 100% if gateway received packet use ACK for gateway.. look I'm not tested .. but in fact ... if sensor send data trought repeater and repeater not see gateway .. still received hardware ACK ?? why ?? not efective contact repeater what don't see gateway.. then i have this idea.. this will be very efective network.. I thinks that serial gateway need RTC on I2C and some small ram .. and inform automaticaly network for this information.. gateway will do more important work

Sorry didn't know this.

thank you for your answer

Thank you!

@Tim no and yes. I'm not working with HG any more because some drawbacks. Now I'm working on EasyIoT server. See: http://forum.mysensors.org/topic/343/easyiot-server-mysensors-raspberry-pi-controller/4

@legeantvert said: On the same way, i dont understand how and where are stored the values inside the gateway if not used on each reception, are they stored somewhere to be able to answer them when serial request arrive? You could bypass this on some kind of events obviously ! Actually my perl gateway is acting as the server Vera is for the arduino gateway. So from there I can trigger external URL, store data in a sqlite3 database... and so on !

@Stephan-de-Klonia: I see your point of a hardwired network but I personally do not like the fact that I have to run cables. For wired sensors I would first think about 1-wire, that is supported by several home automation suites.

Next version will use the burst mode which result in much better success rate for packages. I hope you won't need to resent same data.