I have Hassio installed in a Docker on a Ubuntu host.
I have just discovered that the Discovery dosen’t work.
Have read that you need to use --net=host when you have installed Hassio in a Docker.
But I don’t really understand how to use it and it seems to be some others that have hade problem when they have been using that command.
Maybe someone knows if it should be like this?
Do I need to include the “device”?
If needed, what should the path be?
flaming0e, Okay I have a default setup, Hassio in Docker. Meaning that I don’t have to run the commands that I specify above.
But the question remains why the dicovery dosen’t work.
Can I do test something to see what the problem is?
Then what is the docker run command you provided above? The command you provided above is for running Home Assistant in Docker. Discovery works in that method.
If you are running HassIO, by using the installer script, then host mode is already being used. Discovery works in that method also.
No, the question remains why you think the discovery is broken.
If you’re adding things to configuration yaml, that has nothing to do with discovery. That’s a manual configuration.
Discovery is not where things get automatically added to the frontend.
Discovery is where it scans your network and finds devices and adds them to HA. If it adds to the frontend depends on whether you have automatic lovelace mode or you are manually configuring your Lovelace.
# 433MHz temp and humunity sensor outside & ind
- platform: rfxtrx
automatic_add: True
I know that the devices will not show up automatically in the frontend as flamingm0e wrote but where should it show up?
I thought that it should show up in Developer Tools/States, but it dosen’t.
Yes, all discovered items will show up there. So will all configured items and integrations.
If your device isn’t showing up in the dev tools/states page, then it’s not connecting to the device and seeing it. You probably had an error message in your log on startup if that’s the case, and you should do a little bit of troubleshooting to find the problem.
Not all protocols as advertised are enabled on initial setup of your transceiver. Enabling all protocols is not recommended either. Your 433.92 product not showing in the logs? Visit the RFXtrx website to download RFXmgmr and enable the required protocol.
Have been changing HW from a Raspberry Pi to a Ubuntu machine, Hassio in Docker.
I transfered my configuration from the Pi to the new plattform.
The RFXtrx where working on the Pi, meaning that I have enable the protocal before.
Do I need to that again?
Now when I have a new plattform but the same configuration of Hassio.