Ghost Child

[FcNanoLed]

Hello,
It's a Nano that is connected to my rasberry pi3 by usb key, declared in domotcz 2024.7, I see somes Child Ghost appearing, below only child 0, 1 and 2 are declared, so where do the others come from.

An idea? thanks in advance.

[OldSurferDude]

@FcNanoLed I'm a Home Assistant (HA) user so I don't know if this is applicable to you.

I am assuming here, because your nano is connected to your RPi through a USB port that your nano is running MySensors Gateway code. I believe that both gateway and node code has to have a radio connected to start. So I assume this, too.

The source could be an errant RF signal caused this, though unlikely.

Ghost devices in HA also show up when a device gets assigned a new node on a reboot, or were deleted improperly, eg. not deleted using the controller environment.

In either case, what has to be done in HA is basically remove all vestiges of the MySensors environment best you can.

• Ensure that the code on the device(s) that has the sensors (child) is(are) working properly
• Power down this(these) device(s)
• if you have a gateway, stop or power it down
• Delete this(these) device(s) from the host program
• Delete the integration (this is what the code running in the Controller is called in HA)
• If you use MQTT, use a program like MQTT Explorer to remove all vestiges of MySensors.
• reboot the Controller (HA in my case)
• reinstall the integration
• restart the gateway
• At this point you may still see the ghost!
  ** list itemFor each ghost, create a device that looks like the ghost then delete it using the controller interface.
  ** Then reboot the host again.
• finally reconnect all of your valid devices.

Yes, it is a pain in the ***! Has a lot to do with recoving after a power failure, backups and trying to accomodate all possible scenarios.

Hope this helps

-OSD

[FcNanoLed]

Hello, Thank you for your OSD answer, I tried to remove them from restarting but they come back! I don't have a declared radio node, the nano program only concerns the three childs 0, 1 and 2 all the others 24, 41, 249, 253 and 255 are parasites.
I noticed that the 249 and 255 were time-stamped and that corresponds to the activation of my alarm. Does this mean that my script is badly constructed?

To read you.

[MasMat]

Isn't 255 the child id for default battery level?
The code after is per log parser "!MCO:PRO:RC=1 Recursive call detected in _process(), call level=1"

I'd look in your code.
Also I can't figure out your setup from what you describe (rpi + nano via usb?)

[FcNanoLed]

Hello,
First of all thank you for your help. Yesterday I installed everything again after deleting everything in Domoticz. The result of ghost child. It's not blocking for domoticz but still I would have liked to understand. Some photos:

The parasites have returned 25, 249 and 255

Cordially.

[OldSurferDude]

@FcNanoLed
I have not used a configuration where a Nano is connected directly to the controller. I assume your program has
#define MY_GATEWAY_SERIAL
because I when I compiled a sample program without it and without a radio I got the error:
#error No forward link or gateway feature activated. This means nowhere to send messages! Pretty pointless.

Your code is probably right, but if you posted the entirety we may be able to find the error. Are CHILD_ID_ARMED, and the IDX_xxxx variables? If this is the case, something could be changing them, which could create the ghosts. Typically, compiler directives are used, eg.

#define CHILD_ID_ARMED 0
#define IDX_PORTAIL2 123

I can't think of anything else right now

-OSD