Feature Requests

In all honesty, I'm not quite convinced you'd need two separate networks. Just provide the security sensors, the repeaters, the gateway and your controller - that form the security system - with some sort of ups and they will keep running until the UPS has no more power left. The none security devices will stop working when the power goes out and, unless I don't really understand your problem well. That does what I think you want to achieve? Unless you have combined a lot of sensors within a repeater it would really be my way to go. It wouldn't mean any modifications to your security hardware, because they need to be battery powered or have some sort of UPS anyway, to keep working when the power goes down. But again it's hard to judge when you don't really understand the problem some one is trying to solve.

Yes, I read it. I started using your approach, gateway sensor ids representing nodes ids, but from the controller point of view this is not straight forward, I think. The 2 problems remain somehow the same. How to get the controllers to understand that gateway sensors are not actually sensors but RSSI value, and repeaters breaks my current algorithm. Thinking more about this, if it is something the library would benefit, lead me to read about the RF24 and NRF5 radios. I only have RFM69 devices (20 nodes) and it offers RSSI out of the box, same as RFM LoRa version and NRF5. But RF24 lacks this feature. So it somewhat depends on how many are using radios with rssi. Library developers included RSSI functionality, so it has to be of interest. The repeater problem is partially solved because RF24 networks need repeaters, but don't have RSSI. RFM networks should do without repeaters for most applications. For NRF5, I lack this info. But as I passed the rssi from transport to gateway transport, same can be done with actual sender from the header. Maybe in version 3.0.0 something like this can be implemented? My understanding is that controllers get link quality data the same way they get all other data from devices, on other platforms. Mabey a I_LINK_QUALITY type can be added especially for this information? for example my zigbee network: zigbee2mqtt/device {"linkquality":5,"state":"ON"}

While it would be possible via request() as @mfalkvidd suggests, I wouldn't recommend to do that in this case. I think it's rather pointless to regularly request variables which only change rarely. It adds a lot of traffic to the network - at least 4 messages (including echos) per request - while the requested values stay unchanged 98% of the time or so. Not to mention that the status LEDs could show a wrong condition for up to 10 minutes if you toggle a light switch right after its state has been requested. I'd suggest to use one of the following alternatives instead: You could have the light nodes send messages to both the gateway and the node with the status LEDs. The status LEDs would update immediately when a light is toggled and there's a lot less unnecessary traffic on the network. Let the controller handle the logic. Whenever a light node sends a state change to the gateway, tell the controller to send a message to the node with the status LEDs. This method has the same benefits as the one before and it's easier maintainable since you don't need to re-upload sketches to multiple nodes if something changes - just reconfigure a script in your controller.

@mfalkvidd not necessary. We already have #define MY_GATEWAY_LINUX, so just #ifdef MY_GATEWAY_LINUX to define those constants in runtime at the init stage. As I see it, only SPI driver needs to be defined at compilation, other options could easily be set via config.

I am not sure how retrying even more times will help anything

I just saw your contribution on Open Hardware, very nice! So, I suppose you are perfectly capable of "reinventing the wheel" :D , however, I cannot help but wonder... y_tho.jpg :D :D :D

Interesting. Thanks for the explanation.

@GertSanders, dxf should be recognized now.

(yeah, this is really old in tech years, but I post in the event someone stumbles upon this.) I actually tried the GPS suggestion. I was wrong about the error between two identical GPS's. It's quite large. Check out the other suggestion first.

@vit1251 your question is not clear. But if you are looking at a dashboard kind of a tablet, then you can do one on a nextion display with mqtt.

@adhishor Hi, can you be more specific about the size you are looking for? Should they be as large as a palm of the hand or smaller?

Now it is on github also : https://github.com/mysensors/MySensors/issues/1403

@mfalkvidd said in idea: allow the present function to indicate if an echo will be sent: To my knowledge, the MySensors library itself will send an echo when requested. There is no need to present if the node supports echo or not, echo is always enabled. Very interesting!

@tbowmo @scalz @mfalkvidd Your patience is amazing... ;)

@skywatch said in Motion sensor increase Time high status via software: ti sei Hello and sorry, if I gave the idea of being courteous !! sorry again I didn't publish the code because I really don't know where to start, but now that I understand WAIT, that in MySensors and a separate thing, I also understand your example, and I thank you for helping me !! But then again I didn't know that this WAIT, was something different from DELAY I answer little, because I'm a little busy these days ..... But anyway for now thanks again for help

@alowhum isn't the existing one sufficient?