#define MY_PARENT_NODE_ID AUTO fails
-
Playing with #define MY_RF24_ENABLE_ENCRYPTION I found a problem with
#define MY_PARENT_NODE_ID AUTO
It doesn't find a parent. (To reproduce, please clear the EEPROM first.)
With
#define MY_PARENT_NODE_ID 0
it is working.It seems to write the parent in the EEPROM and is working after that with the AUTO-setting. If I then clear the EEPROM, it stops working again.
Is this only a problem with encryption or is this a general problem?
-
Encryptions is relatively untested. And you did enable encryption on both gateway and node?
I can probably make some tests after work tonight.
-
@hek said:
Encryptions is relatively untested. And you did enable encryption on both gateway and node?
Yes, I did enable that.
My setup:
- a ) ESP8266 gateway
- b ) Sensebender Micro
- c ) Mega2560
Problem can be reproduced wiith both b and c. It is working with fixed PARENT_NODE_ID.
Suggested Topics
-
Day 1 - Status report
Announcements • 23 Mar 2014, 22:45 • hek 24 Mar 2014, 20:12 -
JSN-SR04T-V3.0 Coax cable extended
Troubleshooting • 27 days ago • bocalexandru 25 days ago -
DHT22 wrong sensor type in Home Assistant
Troubleshooting • 5 days ago • Commodoreuno 2 days ago -
Getting system time from the controller
Troubleshooting • 27 Feb 2025, 01:39 • dpcons 3 Mar 2025, 01:00 -
Compiling Sensor code using BME280 and ESP8266
Troubleshooting • 26 Feb 2025, 00:32 • dpcons 26 Feb 2025, 06:22 -
JSN SR04T - Temperature Influencing Readings
Troubleshooting • 6 Sept 2019, 07:51 • Timbergetter 18 days ago