![]() ![]() If you have exchanged GPG public keys, in your local keyring, then this works without manually entering remote passwords. Here’s the whole command that I use successfully, and have embedded in shell scripts. This means it needs to be explicitly closed by the ssh command that is issued, or control is not returned to a prompt by your local shell. mca-cli doesn’t exit when invoked by name, but stays open as a shell for further commands. ![]() There’s one other thing that needs to be done for a command one liner, with ssh. ![]() The SNMPv3 access mode may be different than the CLI and web access mode. If the value is set to ReadOnly, the SNMPv3 user is only able to retrieve parameter information. Therefore a single, ssh command must invoke mca-cli with set-inform as an argument. If the value is set to ReadWrite, the SNMPv3 user is able to set and retrieve parameters on the system. Passing a single command from ssh won’t invoke a full shell environment, and expect to find set-inform on a path, which of course doesn’t exist. mci-cli is multi-entry, like busybox, with multiple internal commands, including set-inform, that may be invoked. Instead, the actual executable is “ mci-cli”. To set the inform URL ourselves required to connect over SSH to the Unifi access point. This doesn’t immersive function, so we need to tell the access point of correct address of the Unifi Controls. The trick is “ set-inform” is NOT a binary executable on the path. Via custom, the access point will search the network for the controller, using the default DNS name unifi. I KNOW this is an old thread, but I figured this out. So, how can I make a simple one-liner that has the logon and the set-inform command in one line I do believe I have tried all combinations of ‘ “ \” … If I run the first one, and just get a consol, I can fine type the set-inform and it accepts it. Gives the error, that ‘set-inform’ is not a know command. And I guess a script can do this, but my first step is to make a single ‘one liner’ per device, and here I have som trouble to pass the set-inform cammand. But I would like to somehow make this as simple as possible. Now, my work-a-round is from a linux box, to ssh into all my unifi devises and run the set-inform. So – which bagic button have I missed that makes all these values persistant in the unifi devices ? I just updated to the latest version (0.23.2) of ‘Home Assistant Community Add-on: UniFi Controller’, which resulted in all going into ‘adopt’ mode (can see that would be normal) and eventurally they all automatically got adopted – but one AP… which is still trying to adopt. My problem is, that when either my ‘USG-3P’ or any of my AP (‘UAP-AC-Pro’ or ‘UAP-AC-Lite’) looses power, then they end in ‘adopt’ state and I can not work with them from the controller before I manuelly SSH into the device and run the set-inform command (pointing to the controller), and then the components are back online. Now I’m asking for help to ease my ‘work-a-round’ - if some one can see the reason for my problem, then I would also be interested in that fix I need a bit of help with my Unifi setup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |