And here is where I can’t get my head around adding the devices.
As for the blinds, I’ve followed this post to no avail
I’ve rebooted the RPi, pressed the button on the KAKU, powered off/on the KAKU module in many different ways and orders , still nothing shows up in Hass.
Am I missing something obvious here.? I’m going in circles for a while…
Thanks and I have done that but no change.
changing devices in configuration.yaml made no change.
Neither dev/ttyUSB0 nor /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A129KK8X-if00-port0 made any change.
Just so I’m expecting the right behaviour ; if you add
switch:
- platform: rfxtrx
automatic_add: true
(or “Covers”/“Light” in the same format), to your configuration.yaml, do device ID’s auto populate into configuration.yaml.?
btw, There is no way I can trigger the KAKU switches to register, these ACM-2300’s only have a learn button and I don’t use any remote to operate them.
You won’t be seeing any device automatically added to configuration.yaml. But you may see “new devices discovered” or something. However, you need to trigger them in order to be detected. F.e., if it’s a light switch that works on 433, you have to press the button to send a signal.
“dmesg | grep tty” done, restarted , nothing has changed.
triggering KAKU without remote seems to be the issue apparently… ACM-2300H is a switch behind a wall switch , flipping the wall switch changes nothing, pressing learn button , same, power off/on same.
no new devices discovered.
having said that, blinds don’t seem to discovered either, i do have a remote to trigger the blinds…
(Adding blinds ID’s manually to the device list didn’t work)
If you are running in a container (ie Hassio), then don’t you need to give the container access to the serial device? By default, a container is isolated and doesn’t get access to all of the system resources (devices, file systems/directories, etc).
I’m by no way an expert but I wouldn’t think so as hassio reports the connected USB devices per default.
Adding Zwave USB follows the same principal and immediately reports entities after reboot.
Well its still worth correcting. Also it does recommend in the docs only having one component as automatic add at a time as some devices can be registered in the wrong component i.e.switches as sensors.
Also as @Nitram pointed out you have to add each device by pressing the remote to program it. The device id is added as an entity to the component that is set to automatic switch.00472… for example.
It could be part of the problem that you have automatic add for everything. Try setting to false everything but switches and try the plug with the remote. You will need to restart home assistant after changing the automatic add.
zwave works fine although root is not part of audio group;
groups show:
core-ssh:~# groups
root bin daemon sys adm disk wheel floppy dialout tape video
have to admit I have no idea how to add root to the audio group, usermod is unknown command…
I’ve chgrp the USB0 device to take part of dialout goup but that is not persistant across reboots
After chgrp and restarting Hass , no new devices discovered (on the KAKU: flipping switches, power off/on , bind button pressed, again, no remote so no other options to trigger anything)
@EGO01 , I’ll follow up your advice and double-check , thanks
I’ll set up an Ubuntu instance tonight and see if that works as advertised , It has to be something really basic I’m missing in my current setup.
I’ve gave up doing this the easy way…
I’m generating codes through /dev-template and add them manually to configuration.yaml
Good news is I can control them finally, bad news is I need to remove all wall switches to access the bind button.
Blinds is the next challenge, at least I know the communication to the RFXcom is working.
Anyone know how to change group persistently across reboots.?
Not sure if anyone still has a problem with this. I managed to make it work (after plenty of attempts and hours) and thought I’d share what I did to save someone the frustration. I’m running Hassio on Rpi3 with a transmitter connected via USB. These are the steps I did:
First Part: SSH/PUTTY/Dmesg
1.1 Install SSH addon in HA from the addon store.
1.2 Enter a password on SSH addon page in the “Config” section. Set Addon to auto-start and restart HA.
1.3 Install PUTTY on your computer.
1.4 Enter “[email protected]” in host name and keep port at 22 and then press Open.
1.5 Press Yes on the popup and then enter your password in PUTTY.
1.6 Enter “Hassio Hardware Info” (this has changed I found this by trial and error) to see what is connected to your device, we are looking for the USB path to your device. You may see dev/ttyUSB0 or /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A129KK8X-if00-port0. For me it was the long one. Save the path since thats what you will be entering in Configuration file.
1.7 Type the command “dmesg | grep tty”. You can close PUTTY now.
Second Part: Setting Up HA
2.1 Add the following to your Configuration file: (Replace the “-” with spaces or Tab")
rfxtrx:
–device: /dev/YOURPATHHERE
2.2 Depending on if you have a switch or sensor type what you have. I will use switch in this case. Remember these lines are not within the rfxtrx segment above. Your file should look like this now:
rfxtrx:
–device: /dev/YOURPATHHERE
switch:
–platform: rfxtrx
–automatic_add: True
2.3 Check config file and then restart server.
2.4 Press on your remote to trigger the switch. For me there was no popup, I suddenly realized that i had a device called 00100120192something in my entity list and saw it worked.
2.5 Remove automatic_add from your config file and enter your name for that device which is explained on this page: https://www.home-assistant.io/integrations/sensor.rfxtrx/
I’m doing some refactor of the rfxtrx component. Could use some help testing stuff once this goes into standard hass. Are you guys still using the integration?
