@yveaux

thx.

would this feature work on a esp32 gw then?

@anticimex
i thought so since using #define MY_ENCRYPTION_SIMPLE_PASSWD does not do any of the signing stuff but still works fine. it seems way simpler. i just hoped that would solve my issue... i tried messing with the bootloader but i did not get anywhere so far.

can someone tell me if
#define MY_ENCRYPTION_SIMPLE_PASSWD "mypassword" would work with mysbootloader?

so if i use an esp8266 as gateway AND i want to use the bufferfeature - to which pin do i have to actually connect the irq on the esp8266? The documentation is not helping me here.

@mfalkvidd said in mysbootloader with MY_SIGINING_SIMPLE_PASSWD:

@zen85 MySensors is open source. Anything is possible, if someone builds it :)

i am thinking about digging into this since this is the only thing missing i would love seeing. i really want the network secured with a password to be safe. i guess the main limitation is the size of the bootloader and therefor it has to be extremly clever... am i right?

or are there other options i am not thinking about to make my network a bit secure?

@tekka
thanks for the answer... is the term 'currently' an indicator that this might change anytime? i would love to be able to do fota and have at least basic security....

@torfinn
i had to set
#define MY_RF24_CE_PIN 10
#define MY_RF24_CS_PIN 9
on mine (definetly not + btw) a while back....

i do not find any information on where and how to set the MY_SIGINING_SIMPLE_PASSWD in the bootloader so i can compile one that works with this feature. the docs just say it is able to do signing since 1.3 - but i guess setting a password would now work for firmware updates for example?

@tekka
EDITED ANSWER*: it worked!

• it did not work because of a typo... sorry for that....

@tekka @mfalkvidd

ok... some success but not really. The bootloader does not seem to work using my custom-boards where the ce and cs pin are switched? where does one have to put something like:

#define RF24_CE_PIN 10
#define RF24_CS_PIN 9
?

should it be in the mysbootloader.c? because this did not work... or somewhere else?

the line "#define SPI_PINS_CE9_CSN10" in the mysbootloader.c also worries me? but just switching the numbers does not work either and throws an error...

ok... i once again report back to my own entry since i became a little smarter.

i found out 2 things:

• in the boards.txt i have to set the right fuse-settings. for the 16mhz nano i used:

MYSBL.menu.frequency.MYSBL16.bootloader.low_fuses=0xFF
MYSBL.menu.frequency.MYSBL16.bootloader.high_fuses=0xDA
MYSBL.menu.frequency.MYSBL16.bootloader.extended_fuses=0xFD

• i used a screw-terminal board where the ce and cs pins are switched. in the usual sketch i define

// Set custom pins for Nano-Radio-Board
#define MY_RF24_CE_PIN 10 
#define MY_RF24_CS_PIN 9

i am sure the mysbootloader needs to know that too... so am i right that i have to compile a new bootloader where i have to put:
#define RF24_CE_PIN 10
#define RF24_CS_PIN 9
?

i am really having a hard time compiling one since i have zero experience with that and eclipse doesn't seem of much help here. so if anybody can confirm this before i go through this fruitless struggle again i would be very glad...

as soon as i burned a new bootloader it worked. watchdog does not like old bootloader and since mysensors is using that for rebooting it fixed my issue.

Hello,

did anybody successfully get mysbootloader for fota get to work on a nano? i burned the bootloader via an uno (arduino as isp)... everything seemed to work fine...

but nothing changes actually - the log on myscontroller says nothing about a new bootloader whenever i try to click the node > settings > Board with mysbootloader i see the functions. when i click anything like "reassign ID" it just reboots with the old ID - when i try to load a new sketch via "assign firmware" it is the same. it just reboots and nothing changed.

i tried different gateways (rpi and nodemcu), i tried different mysbootloaders with different channels from the github repository, ... it seems to be the same everytime...

did anybody run into the same issues or has a hint - i tried now for 2 days without progress...

I just found out that using watchdog do reboot also does the same to the arduino (it is a nano and more people seem to have the problem specifically on nanos) ... so i guess mysensors has nothing to do with my problem. i probably need a new bootloader...

In MYScontroller i can send I_PRESENT and request a heartbeat to a node and i get the expected results... When i send I_REBOOT on the other hand the arduino starts blinking like crazy and the powersource needs to be removed before it works normally again. just pressing the reset button also does not work.

the last serial output before "dying" is:

20518 TSF:MSG:READ,0-0-188,s=0,c=3,t=16,pt=0,l=0,sg=1:
20533 TSF:MSG:SEND,188-188-0-0,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE>
20674 TSF:MSG:READ,0-0-188,s=0,c=3,t=13,pt=0,l=1,sg=1:0

so i also have burned mysbootloader and the following things in the header:

#define MY_RF24_CHANNEL 100     // In EU the default channel 76 overlaps with wifi, so you could try using channel 100. You will have to select the same setting on every device in the network (including the gateway).
#define MY_OTA_FIRMWARE_FEATURE

// Mysensors: security
#define MY_SECURITY_SIMPLE_PASSWD "******"      // Be aware that longer passwords use slightly more memory.
#define MY_SIGNING_SOFT_RANDOMSEED_PIN A7         // Setting a pin to pickup random electromagnetic noise helps make encryption more secure.

#define MY_RF24_PA_LEVEL RF24_PA_MAX              // Offers the most range, but high power can cause issues on cheap Chinese NRF24 radios

the node has no sleep, delay, wait command either...

does anybody have an idea what this could be?

@skywatch

hey. i was having the same problems from time to time - i found out that its mostly wiring - therefor i am a great fan of easypcb and other boards that let one mount the radio directly.
and also mounting a fan on my gateway (rpi3b) helped a lot with that. other than that repeaternodes...

also install myscontroller - makes debugging way nicer and more efficient because you see in realtime whats going on... you might not have just one problem but more at the same time.

@ddevilliers said in Home Assistant MySensors Notify problem:

Note Home Assistant do receive values from the sensors. I just cant get HA to send a text value to the sensors as per the HA example.
Thank you.

did you ever find out? i am having the same issue here.

sorry for spamming my own thread... i just want to keep updates coming in while debugging... i got it to the point where the homeassistant log tells me: "Unable to find service notify/mysensors".

but apparently there is no known solution to do this. i even unplugged and restarted everything. i am hitting a dead end here...

let me ask differently again:

did anybody get this:
https://www.home-assistant.io/components/notify.mysensors/

to work? i find no useful example and have the suspicion that it just doesnt work anymore since all the forumentries seem old and outdated?

@alowhum

good idea. thx.