I am using the latest version of hassio and samba.
I see everything else (wemo, tasmota devices)
no matter what I try I can’t see the Rpi
Yep. I don’t see it in network places either. HA needs to update it’s samba version. Stopped working about a month ago. I can still map a share though. Try \\hassio
When I have a situation like this I normally take a look at the fing app on my Android phone - I think there’s an iPhone app as well (much easier that getting into the Windows command line stuff).
This shows me not only the IP address of the device I’m looking for, but I can also check ping results and scan for the services running on the Pi. If I don’t see the correct ports (22, 8123) I know it’s the Pi and not a network issue.
E.g. if 22 is there but 8123, isn’t there I know that HomeAssistant didn’t start up.
So I connect to the Pi via SSH and check for any startup/config errors by using the command ‘sudo systemctl status home-assistant@homeassistant -l’ or whatever your configuration requires.
Port 445 is the SMB port.
Thanks all.
Using fing, I see 22.139,445,8123
another thing that happened is that hassio.local:8123 no longer works. I have to use the tcp address.
it comes up fine and config shows no config errors.
also I added configuration to the list on the left (with hassio etc) It worked for a while then quit.
very frustrating .
I just went to ssh and entered
hassio ha restart
and not hassio.local:8123 and configurator work.
I had done reboots from within HA and that did not fix whatever the problem is
look into re-enabling smb 1 on your windows 10 PC. I had a similar problem and this solved my issue.
some info here of what to do
https://social.technet.microsoft.com/Forums/windows/en-US/8160d62b-0f5d-48a3-9fe9-5cd319837917/how-te-reenable-smb1-in-windows1o?forum=win10itprogeneral
SMBv1 was disabled by MS for a reason. Wannacry and Petya anyone?
HA should be updated to stop using the 30 year old incredibly insecure SMBv1 protocol.