Feature Requests

Why don't you just use an existing message type to send the time to the controller? Imo the real challenge would start the moment the GW handles the message over to the controller: has the controller sw the necessary rights to change system time (in my case: no...) how to deal with conflicting info from different sources? Imo, it's already possible for the rare use case there might be left over (but as explained needs some manual configuration). Especially when using a Pi: add a RTC and make some manual updates on that every now and then (if necessary). Just my2ct.

@wofwca but isn't it indeed? ;)

@mfalkvidd that's really great. I'll try. Thank you very much.

@monte Thanks, I know.

This can be achievable by using a TLP5110, this device is only consuming (sipping) 35nA. and then the comment from rozpruwacz is very valid, that you need to be careful of battery self discharging The you can use a switch to wakup the MCU when window is opened, and provide a resister value to TPL5110 to startup MCU once per day, to give a heartbeat signal that sensor is alive http://www.ti.com/lit/ds/symlink/tpl5110.pdf [image: 1542391196498-tpl5110.png]

@rozpruwacz Sorry, it's hard for me to work on this subject during week days. I2C is in the code, I'm just trying to find a generic solution. Currently, my raspberry has only the nrf24, therefore, I'm probably not using I2C. My configure options are: ./configure --soc=BCM2835 --my-gateway=ethernet --my-port=5003 --my-rf24-encryption-enabled --my-rf24-channel={{ rf24_channel }} Note that since my network is only sending information (nothing is controlled), I'm not worried about not using signatures between nodes. I enabled it in the past but then, disabled it.

this is a good place to start and start to understand. I'm not a lot of diggers, however I start reading something, and in case I'll ask for help In a lot of thanks

First off, sorry to revive this. I just discovered the (new?) 8-pin CC1101 modules and thought "hey, it uses the same socket as the NRF24". So I tried comparing the pin positions. And to my surprise they seem very compatible: GND -> GND CE -> GDO0 SCK -> SCK MISO -> MISO 3.3V -> 3.3V CSN -> CSN MOSI ->MOSI IRQ -> GDO2 To me this radio would have a few advantages over the RFM69: Plug and play. I could plug it into the Nano wireless expansion boards. Built in antenna socket. I think it could be advantageous to use a 433 radio that is plug-in compatible with the NRF24 in this way. 3D printable cases and open hardware designs would only need to support one socket design and still support both frequencies. The STM8S103F3P6 (the "1$ arduino") has a version with built in socket, and expressly advertises that it is compatible with both radios. There is an STM32 version with a socket too. As someone who started by using the NRF24, I've long wished I could easily switch to the 433Mhz band instead. Supporting the CC1101 would make that as easy as plugging in a new radio.

@gohan I will use this barebone ESP32S module without LED, USW, Voltage Regulator etc. https://de.aliexpress.com/item/ESP32-ESP32S-WIFI-Bluetooth-Module-240MHz-Dual-Core-CPU-MCU-Wireless-Network-Board-ESP-WROOM-32/32817688406.html?spm=a2g0x.search0104.3.1.3bc34eb5tSg79z&ws_ab_test=searchweb0_0,searchweb201602_5_10152_10151_10065_10344_10068_5722815_10342_10547_10343_10340_5722915_10548_10341_5722615_10696_10084_10083_10618_10304_10307_10820_10821_10302_5722715_10059_100031_10103_10624_10623_10622_5722515_10621_10620,searchweb201603_2,ppcSwitch_3&algo_expid=499485e8-6df0-40d6-8033-c5497748adb9-0&algo_pvid=499485e8-6df0-40d6-8033-c5497748adb9&transAbTest=ae803_1&priceBeautifyAB=0

I'm on the way to implement something similar with e-paper (without touch at the moment) to save battery. However I will use an additional SPI port and require a lot more flash/RAM as ATmegas provide. Also with the STM32 I'm comming to a limit. Thus I'm switching to an ESP32 barebone module for 3,63€ (4,20$) and habe 4 SPI ports, many I2C ports etc. https://www.aliexpress.com/item/ESP32-ESP32S-WIFI-Bluetooth-Module-240MHz-Dual-Core-CPU-MCU-Wireless-Network-Board-ESP-WROOM-32/32817688406.html?spm=a2g0s.8937460.0.0.xvTLd7 The nice thing with the ESP32 is, that it has 10 touch panel ports on-chip and is very engergy efficient (if used with battery). We had this discussion already and if the bare module is used is has on one hand suffient MCU power as wel as very low engery in sleep/deep sleep. IT has WiFi, BlueTooth, no limits with Flash/RAM etc. Think about it. The best thing: There is a brach or event a planned PR which supports ESP32. See here: https://forum.mysensors.org/topic/9167/esp32-support-to-enable-the-powerful-esp32-rfm95-lora-lipo-battery-boards

@sundberg84 said in Visual feedback (leds) @ error: This could btw be used in a tutorial on the website for others... just my thoughts. @sundberg84 @Anticimex Yeah, I know I should, but this alone already burned my spare time for tonight :sweat_smile: Anyway, now I have an extra excuse to meet you guys for a :beers: !

@yveaux clarification: imho, if support for many interrupts is added in a future version of MySensors (which is what we're discussing in this thread), sketch developers should not need to manually call pinMode.

Sorry for my poor english im french. They havent solution for use only the tx/rx pin on both raspberry pi and arduino?

@mfalkvidd OK, the before() works! 0 MCO:BGN:INIT NODE,CP=RSNNA--,VER=2.1.1 3 MCO:BGN:BFR running before() function 2006 TSM:INIT 2011 TSF:WUR:MS=0 2012 TSM:INIT:TSP OK 2014 TSM:INIT:STATID=25 2016 TSF:SID:OK,ID=25 2018 TSM:FPAR 2036 TSF:MSG:SEND,25-25-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 2850 TSF:MSG:READ,0-0-25,s=255,c=3,t=8,pt=1,l=1,sg=0:0 2855 TSF:MSG:FPAR OK,ID=0,D=1 4043 TSM:FPAR:OK thanks for the cooperation mfalkvidd & rejoe2