After the 2023.12 update the ping integration does not detect my motion sensor the way it used to. I even made an automation based on the officail ping documentation but it would not pick up my motion sesnor every time like it used to via yaml code. Anybody got the motion sesnor working right with the new ping integration?
1 Like
I’m experiencing the same issue; the sensors stopped working after the last update.
Right now I moved to Node-RED and it’s ping feature, it works as it should.
Hello @DominikW
Can you please elaborate on this flow?
I found the ping, but which IP do I use, just the local IP?
And I found the switch, but why is the switch there if I may ask?, and why two outputs combined into one? And how do I add a second output?
I can’t find my tuya PIR though, I think I need the HomeAssistant Sensor here, but I it asks me to create a new sensor, but I just want to select my Tuya PIR?
You see, having a very hard time with NR here.
Many thanks in advance
Peter
The IP is the local IP adress of your motion sensor, I have it at 192.168.0.197 as I set it in my DHCP server. The switch I’m not certin is needed, but for some reason without it I would it would not work as I wanted it to.
The new sensor is a binery sensor with device class motion, if you delete the old integration you can probablly use the same name in the new node-red sensor so you don’t have to change anything in automations of frontend.
Thank you for explaining. But it is not for me, Node Red (not you, don’t get me wrong) is super vague and user-like-me unfriendly 
I now use this perfect and easy-peasy workaround:
So I think its working, but it seems sporadic. Or maybe I’m missing the motion event not sure. Can someone help?
Using Ping (ICMP) integration to ping the motion sensor:
binary_sensor.192_168_50_32
Custom Polling of ping binary sensor:
Template Binary Sensor:
Automation (UI was easier to read than YAML code, due to entity IDs being so long):
Is there anything I’m doing wrong or is this sporadic behavior expected?
Also, I am a noob, but am I suppose to see the template sensor anywhere in the UI, because I dont. I’m also not getting any errors either.
Here is the ping sensor history:
Not sure if it is because of the new HAOS version but this guide to use tuya motionsensor by pinging it did not work for me as a HA beginner. Also it shows as “Motion Sensor (unsupported)” in the standard tuya integration.
I got my tuya wifi motion sensor working the following way:
- find the ip of the motion sensor in your router by looking for the mac that is provided in the tuya app (tip: if you can’t find it, give the mac-adress a static ip and reset the motionsensor, the router will now give it your designated ip)
- add this ip with the built-in Ping (ICMP) integration
- under integration-items > configure: change consider home interval to 1 and leave pingcount to 5
- under integration-items system settings (click on 3 dots next to configure) turn off polling for changes.
- Find the (newly added) binary sensor entity and change ‘show as’ to motion.
- make a new automation to ping every second (trigger= time_pattern and seconds = /1), action= homeassistant.update_entity. Add entity id of your new binary sensor.
- Now make sure your log is not spammed every second by the triggering of the automation, exclude it from logbook by adding the following to your configuration.yaml:
logbook:
exclude:
entities:
- automation.(your automation id)`
Done! your binary (motion)sensor should now work.