The only other information I can think to give you is that if I open a terminal on my iMac and run the command nmap -privileged -sP 192.168.0.81 the Raspberry Pi responds perfectly, it also responds perfectly to Ping commands as well as every other network tool I could think of running against it. (homeassistant_venv) ~/.homeassistant $ arp 192.168.0.49Īddress HWtype HWaddress Flags Mask Ifaceġ92.168.0.49 ether b8:27:eb:89:fa:fe C eth0Īnd that's where we stand, I have no idea why it's not showing up as I didn't do anything at all while I was asleep as far as I'm aware to cause any changes to the homeassistant Confederation. I first ran the arp command on the Raspberry Pi I'm having problems with, this machine has an IP address of 192.168.0.81 and this was the output: So I dutifully ran the following commands with the following results. And to be clear again because this seemed to be point of confusion, it's the Raspberry Pi running homeassistant that isn't showing up any more. After much time somebody asked me to run an arp scan from within the virtual environment that hass is running in. So, after much shouting, swearing, googling and I'm not too ashamed to admit there might have been some stomping of wheelchair wheels I decided to ask for help. Screaming every single swearword I know at the machine in question also appeared not to work, not entirely sure why this approach didn't work.Running hassctl error, hassctl debug and simply running tail -f home-assistant.logshowed nothing out of the ordinary whatsoever.I even tried manually adding a declaration to the known_devices.yaml for the Raspberry Pi that wasn't responding, I basically copied one of the existing entries for a Raspberry Pi that was showing up and changed the details to reflect the problem Raspberry Pi's MAC address etc.I've also tried running the nmap component with and without any and all of the configuration options that seem to be possible with this component, in every combination that I can think of. I have tried getting rid of the known_devices.yaml file multiple times and rebooting the Raspberry Pi with the exact same result that every other device but that one shows up, I have tried getting rid of all the other trackers and just having the nmap tracker running but with the same result. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |