Hello,
I’m new to home automation with Gladys.
I installed the Gladys container on a VM running Debian12.
I can’t list LAN devices with lan manager.
Here is the log report:
From the report I deduce that nmap is used to list devices.
So I decide to run nmap directly via ssh from the container.
Failure.
I decide to run nmap from the VM.
Failure. nmap not installed.
I install nmap on the VM.
I run nmap again from the VM.
Success.
I run nmap again from the Gladys container.
Success.
I restart the scan with Gladys.
Failure.
If anyone has any idea, it would help me because I just bought a few Shelly 1PM.
Your container must be in network mode = host (as in the command)
Your VM must have proper access to all devices on your network (maybe it’s on an isolated network?)
Have you correctly defined your CIDRs?
Out of curiosity, why do you need the LAN Manager integration?
I don’t know why, but I have the impression that everyone tests Gladys by trying this integration first, and often gets very bad results (which is normal — to me, presence detection via Wi-Fi scanning is a bad idea), and I don’t understand why everyone insists on this integration
LAN Manager won’t let you use your Shelly 1PM.
To control your Shelly, you can do it via MQTT, or via HTTP in scenes
Edit: There’s a feature request for a native Shelly integration, but so far few requests; you can vote for this request here :
Hi @pierre-gilles,
Thanks for taking care of my case.
I used the docker-compose provided on your site.
I set the CIDR to 10.42.0.1/24 (by default the CIDR was 10.42.0.94/24).
The IP of my VM is 10.42.0.94.
What strikes me is that now nmap works fine from the command line both in the VM and in the container.
I wanted to use lan manager to detect my Shelly modules which are marked as wifi but there may be another technique less costly in bandwidth than scanning the LAN every two minutes (if I understood correctly).
.
