Miniserver locked out user for too many failed login attempts.Too many failed login attempts - stopped trying. Binding will make another attempt to connect after some time. Invalid user name or password or user not authorized to connect to the Miniserver.Miniserver host/ip address can't be resolved.There can be following reasons why Miniserver status is OFFLINE: Loxone :miniserver : 504F 2414780F # Thing Offline Reasons are optional advanced parameters - please refer to Advanced parameters section at the end of this instruction for a list of available optionsĮxample 1 - minimal required configuration: is a port of web services on the Miniserver (please notice that port, as a number, is not surrounded by quotation marks, while the other values described above are).is a host name or IP of the Miniserver.and are the credentials used to log into the Miniserver.is a unique ID for your Miniserver (you can but do not have to use Miniserver's MAC address here).The entry should have the following syntax: # Manual configurationĪs an alternative to the automatic discovery process, Miniservers can be configured manually, through an entry in. Please set them manually in Thing configuration after you add a new Miniserver Thing from your Inbox. Discovery (opens new window) is performed using UPnP (opens new window) protocol.īefore a Miniserver Thing can go online, it must be configured with a user name and a password of an account available on the Miniserver. Loxone Miniservers (opens new window) are automatically discovered by the binding and put in the Inbox. The Thing UID of automatically discovered Miniservers is: loxone:miniserver:, where is a serial number of the Miniserver (effectively this is the MAC address of its network interface). This binding supports Loxone Miniservers (opens new window) for accessing controls that are configured in their UI. Hash-based and token-based authentication methodsĬommand encryption and response decryption Passing channel commands to the Miniserver's controls Updates of openHAB channel's state in runtime according to control's state changes on the Miniserver Management of a Websocket connection to the Miniserver and updating Thing status accordingly Tagging of channels and items (opens new window) with tags that can be recognized by Alexa (opens new window) openHAB skill (opens new window), so voice can be used to command Loxone controls The following features are currently supported:ĭiscovery (opens new window) of Miniservers available on the local networkĬreation of channels for Loxone controls that are exposed in the Loxone UI (opens new window) Miniserver controls, that are visible in the Loxone UI (opens new window), are exposed as openHAB channels. Miniserver is represented as a Thing (opens new window). This binding integrates Loxone Miniserver (opens new window) with openHAB (opens new window).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |