Development

@strixx yes

@strixx you are welcome. The simple flag is designed to be as simple as can be. So it enables everything. On development it is slightly refactor ed, so it is possible to use simple signing, simple encryption or simple "both" (which if I recall is named SIMPLE_SECURITY_PASSWD or similar.

Signing allow this. Encryption is for everyone. With signing and "weak security" on the GW, you can selectively have nodes that require it. GW will then only require signed messages from the nodes that themsleves require it. Everyone have to have encryption though, or you need to disable encryption.

Hey, Just for information: I solved all my problem ny soldering. Don't know if this is the breadboard or the Dupont wire jumpers, but with wires soldered, everything is working now :)

@gohan I just tried that and answered my own question (it worked). Thanks for the pointer.

@kduino I think you need to define MY_RS485_SWSERIAL as well

Update: LTO is enabled by default for avr core/board version 1.6.12 and newer.

@maghac Im using mastech MY65 and I can measure ~0.1uA minimal current with some error

if you have line of sight to it, you could technically do it.

@benbidouille great. Thanks for reporting back.

Lol. I just forgot to change the topic in my code from "MySensors" to "domoticz/out/MyMQTT" Now working fine

@yveaux thank you!

Hi Yveaux, many thanks for your effort to my case. I didn't knew that after a wakeup, nrf24 is in stby before the next restart loop. Indeed, I tried a new sketch and confirm this particularity. So, a workaround should be to put a "sleep()" at start of the "loop" void loop() { // => At this point NRF is in RX mode sleep(xxx ms); // Put NRF24 in stby // ****** // // All job here without NRF consumption !! // // ***** } // End of loop I will do something like that !! Maybe, a new definition should be interresting, like MY_NRF24_RXMODE_DISABLED I'm sure many nodes never need the RX mode. PS: Hum.. !! I didn't tried if after the send command, NRF24 come back in RX mode or not.

The internal commands can be found at https://github.com/mysensors/MySensors/blob/development/core/MyMessage.h#L165 We should probably update the api page.

Thanks @mfalkvidd Yes, I have been down that route as well - stitching my meter together from other sensors already known by mysensors. I had a look at eg S_WIND, where the sensors can have 3 values, with one of them even in a completely different domain (V_DIRECTION) So ideally mysensors supported my energy meter as a "thing" with the relevant set of parameters. Question is if I should add a custom type to mysensors myself, does it support "local" additions? What would be the "correct" way to do it? Soon I might have all kinds of sensors which has never been in the scope of mysensors, and probably should never be either, like meals served in the canteen, cars in the parking lot and so on. mysensors appears to have some really cool communication implemented, I can just not fit into the types defined. I have found that simply setting type using something like msg.setType(99); give me full control, but it is of-course just another hack.

for a water detect event you can use the motion or door sensor example

As the analog pins share a single A2D, rapid use of it can cause the previous read to impact the next. A common workaround in this situation is to read twice on each input, ignoring the first. try that: // read analog pin (void) analogRead(BATTERY_SENSE_PIN); int sensorValue = analogRead(BATTERY_SENSE_PIN); // calculate battery voltage float vBat = static_cast<float>(sensorValue * (V_MAX/1023));

@scalz You could share your code too :relaxed: