Troubleshooting

@gohan said in New CHILD ID after reprogramming: #define MY_NODE_ID 5 aha MY_NODE_ID, instead of CHILD_ID :+1:

I tried with two different Dallas Onewire and checked out the library at github. Have build these sensors before but got -127 all the time. Just adding this here if it pops up alof of people having issues...

@juanmrodrigues It's still on the backlog :grin:

It looks like it is rebooting for no reason, try to use latest 2.2.0 library

@mpp ground needs to be connected, otherwise the signal levels for the serial won't match.

@mfalkvidd Oh, cool. I missed that (and I didn't know that, and I learned something today :-)). Yep, in that case it wouldn't help much.

@emme I think you'll find the answer for presentation in https://forum.mysensors.org/topic/6506/how-to-ask-a-node-to-re-send-presentation-info/ Reboot works the same way, except you use I_REBOOT instead. See https://www.mysensors.org/download/serial_api_20#internal

@Cliff-Karlsson Very interested to see what you'll be building with this sensor! (http://www.pureengineering.com/projects/grid-eye-breakout) Maybe this sketch can help? https://github.com/kriswiner/AMG8833

upgrading to the latest build fixed my issues. Thanks guys for the support!

Unfortunatly the sensor stopped working last night. I have ordered a relais board with opto coupler.... I will keep in touch

I did not know about the newPing.h library. (i can not find it when searching for it in the Arduino IDE).. so i googled it. The example (for 15 sensors) confuses me :) Can't you just do something like this? unsigned long pingTimer[SONAR_NUM]; unsigned int cm[SONAR_NUM]; boolean bigChange[SONAR_NUM]; void setup() { pingTimer[0] = millis() + 75; pingTimer[1] = pingTimer[0] + PING_INTERVAL; } void loop() { // your rest code here.. for (uint8_t i = 0; i < SONAR_NUM; i++) if (millis() >= pingTimer[i]) { pingTimer[i] += PING_INTERVAL; cm[i] = sonar.ping_cm(); bigChange[i] = ((doorDistance-(int)cm[i]) > 10)?true:false; } oneSensorCycle; And adjust oneSensorCycle() to use bigChange[0] & bigChange[1] instead of bigChange_0 & bigChange_1

NodeMCU is much bigger. It also costs a lot more. I do not need a USB port or any other features that have these modules.

@Yveaux thanks for you response. I don't this this is the cause though, I have tested these transceivers and they're running perfectly with the Moteino code. @ledfreak3d, did you manage to get it fixed?

done! Thanks @mfalkvidd

Thanks for the quick answer and advices. I understand my mistake: It is not linked to the inclusion, but on the Gateway and Nodes versions: (Gateway was on MySensors 1.4, while Nodes were on MySensors 2). Reconfiguration of the Gateway gives appropriate results and is immediately included in Domoticz !

Have you tried latest 2.2.0 version?

I solved the problem. I have soldered a 1000uf capacitor to the output of the step down modul. Now everything is ok. I will try the beta Version.

It makes sens that the controller should adapt themselves and manage the NODE_ID 0. But i just don't have the skills to adapt Jeedom to do so. I could try to play with MySensors lib, but both solution are a waste of time as I would have to change the code each time the controller or the lib has a new version. I will have an independant node and a gateway and wait lie this for the controller to manage node_id 0 Thank you again for answering me. Matz