Search the Community
Showing results for tags 'login'.
Found 4 results
Hello, It would be nice if we could control the level of access for our Team Members other than just assigning them to specific agents. For example, giving read only access vs. read/write. For example, the Domotz user name is the same as our e-mail (and there currently is no way to have a different e-mail for notifications vs login access) and we use a specific e-mail for all of our notifications so we can scrape them and automate trouble tickets. Thus, we have a Team Member just for our e-mail alerts. It would be nice if we could make this account read only since it's only used for alert generation.
Just installed on Synology DS414Slim Agent is running but when i login with validated Domotz account it just says error. I tried to create a new account, but the Country dropdown doesnt work, so not possible. Tried via Chrome, Edge, Firefox and get same result.
Just a heads up in case someone's having problems logging in to the Domotz Portal, we've updated some things and you might have to do a "hard" refresh of the page, or completely exit your web browser and start it again. Keep in mind that Chrome tends to run in the background even though you've closed all browser windows, which will prevent you from logging in without doing a "hard" refresh of the Portal page.
I know this is a fairly low-priority item but it would be useful for those of us with RasPis (and maybe others in structure). The ability to get the Domotz agent to login without a web browser by allowing a command-line submission of email address and password. We already are doing a number of steps to install (or upgrade) the agent in command line (regardless of whether it is headless or not). This would allow a person to just continue following steps (easily copied from the Domotz Portal's instructions) to complete the entire process. No other windows or browser needed. This would allow the steps to be more easily automated. Related to this, if the Domotz agent can be downloaded the same every time (example, in the future you could always go to: wget https://portal.domotz.com/download/agent_packages/latest/raspi.deb) the entire process could be a single script and would never change IF someone wants the latest. Such a structure works for any of the releases (with different end file names) and could readily be altered for future betas that you might not want accessible to everyone (by making it .../agent_packages/betas/... and having user/password restrictions based on portal access). Then someone could actually LOGIN to get the beta software also easily added to the wget command.