1 Node with 2 Names Resolved !
-
this is the issue as I see it.
I have my sensors up and running and all seems to be ok so far as I know.
I have node 3 which is a temp/hum sensor created off a UNO, called node 3 and two children.
Trying for a while now to get repeater node ready for distance.
After including new repeater, with mini pro, a node 3 repeater is created but children remain labled as original and report back to the vera with correct readings.
Pressing reset on UNO will revert node back to Humidity node and repressing reset on repeater results in repeater node .So two things conflict on one node which I am running out of ideas and probably creation of repeater node (which would happen I think if conflict disappears.)
I am not ready yet I believe to use the new GUI that @tekka has presented.
I have included the code from serial screen when it changes from Hum 3 to Rep3
-
-
I have seen in Development threads @pit007 asked question similar to mine under thread called change node id so I will see if this will help me by trying to manually change the node id number of the repeater node . More on this later.
-
By implementing this eeprom fix my node issues were resolved. : )
Suggested Topics
-
Day 1 - Status report
Announcements • 23 Mar 2014, 22:45 • hek 24 Mar 2014, 20:12 -
JSN SR04T - Temperature Influencing Readings
Troubleshooting • 6 Sept 2019, 07:51 • Timbergetter 28 days ago -
Compiling Sensor code using BME280 and ESP8266
Troubleshooting • 26 Feb 2025, 00:32 • dpcons 26 Feb 2025, 06:22 -
DHT22 wrong sensor type in Home Assistant
Troubleshooting • 16 days ago • Commodoreuno 10 days ago -
Forum Search not working?
Troubleshooting • 4 Oct 2023, 23:33 • Gibber 2 Sept 2024, 20:28 -
Ghost Child
Troubleshooting • 15 Mar 2025, 07:44 • FcNanoLed 18 Mar 2025, 18:36