Feature Requests

Oop's! Maybe my own english is not at the right level. I used to read "water leak" as "not enough water" most probably because I did a confusion with "water lack". But according to WordReference, you're right ! So, yes, s_water_leak will do the trick. Thanks for your answer and sorry for the noise in the forum. Regards, Pierre

Yes, agree, Just sending pulses has its advantages.

Inclusive mode need only when configured network. It lasts one minute. No nide listen self pipe. After end inclusive mode, gateway listen self pipe his makes it possible to have a whole range of addresses

Thanks for adding it in version 1.5 :smiley:

Yes, the gateway send this information to the controller.

@ajachierno There's an existing thread discussing this: http://forum.mysensors.org/topic/816/send-color-data-to-sensors. Looks like it's planned for the next release. Cheers Al

@blacey Yup, @hek also pointed me in the directions of those changes. However, while reading up on the communication specs for the ws2812b (as I had in mind using for the GW), I found them to be very timing critical, so I think it would be too much trouble to implement this type of controller for the status LED's, and therefore I have dropped that idea again. :)

Ok, so the following stuff isn't 100% correct anymore I guess.. (it's not Protocol.. and I've wondered for a while why each sensor is reporting the same library version as the rest and the node itself..) https://github.com/mysensors/Arduino/blob/master/NodeJsController/NodeJsController.js#L588 I'm not using this one, but rather a perl controller inspired by this.. Work In Progress..

Never mind, I found it out myself by browsing through MySensor.cpp, apparently nodes are sending in their parentId during startup.

Yes, it is needed. Almost similar request here: http://forum.mysensors.org/topic/1337/request-new-sensor-type-thermostatically-controlled-switch

@X-Ryl669 I'm happy to see what you come up with. @andriej There is a ongoing discussion here about creating a gw-device with a little bit more horsepower: http://forum.mysensors.org/topic/1137/gateway-device There is also the option of using RPi as combined controller/gateway. @celonunes is making an effort to join the current development branch with the separate Raspberry project.

Interesting idea, Maybe you could let gateway unpack the COMBO message before handing it over to controller. This way no additional changes is needed on that side. I would appreciate if you wanted to create a github pull request (on the development branch) with your verified changes.

Hi. That's the same problem I'm facing at my house, multiple levels, also the radios don't have enough coverage to reach the far end of the same floor (PA's radios do, but I only use them on the GW and MQTT GWs, can't use them on battery powered sensors for obvious reasons), so the multiple gw distribution system should be an ideal solution for me and people living in "castles" or "Faraday cages" XD Currently I have moved from a serial gw to Ethernet and MQTT gws (one Ethernet and one or two MQTTs), I find the Ethernet GW to be more stable than the MQTT ones (Client or Broker, same DIY PCB, I just pop out one nano and place the other) , your scenario 1, also some messages get mixed from time to time, even using different channels. Some times the GWs stop looping and I need to restart them, funny thing is that connecting to them in order to debug if they are running seem to jump-start the loop again. So my vote goes for scenario 2 also, plus, it should be interesting for the Ethernet GWs to act also like MQTT Clients and/or Brokers, because the IOT community is clearly taking that approach in their effort to "standardize" all the chaos that exists today. I think we should keep things as simple as possible, I've read this post: http://forum.mysensors.org/topic/887/future-network-topology-for-discussion And I think it's a superb idea, clustering the whole network into more easy to manage subnetworks, each one with a different topology connecting to a Network (TCP) controller through their GWs, all the complicated stuff should be done by the "Controller" the subnetworks should be as dumb as possible, leaving the heavy duty processing to the controller. I know this isn't much, I wish I knew more about all of this, but I hope my experience will be useful. Regards.

Please try again. Lesson learned: Don't answer posts on holiday with a tablet... :+1:

Well, i guess mine's different. :-) It's RGB and the longest leg have to be connected to gnd. Maybe that's why.