- #Homeseer speaker client for mac android#
- #Homeseer speaker client for mac pro#
- #Homeseer speaker client for mac code#
- #Homeseer speaker client for mac password#
Total tally of remote stuff talking to HS3 is: 16 HSTouch clients + 18 speaker clients + 3 remote plugin clients here with no issues.
#Homeseer speaker client for mac password#
Remote plugins do not require a username and password from what I can tell here. Well Homeseer touch, Homeseer designer and Homeseer speaker all work exactly the same with whatever username and password I configure on them. IE: mono zwaveplugin.exe server=ipofmothership. I am currently running the Z-Wave, X-10 and UPB plugins remotely only using the IP of the mothership. I have disabled the default user name and password on the two machines. Works fine and the 16 clients speak in in a variety of english fonts, portuguese SAPI fonts, French, spanish, italian, german et al with no issues. On the 16 Homeseer touchscreens running in embedded Wintel I do the same with the HSTouch client and HS Speaker application.
#Homeseer speaker client for mac pro#
Each speaker instance is using a unique user name and password on each of the two motherships (HS3 Pro and HS3 ZeeLite). Here run two instances of speaker dot exe on a remote Wintel Server VM for two different SAPI voices coming from two HS3 boxes. I did the doo and it doesn't cripple important capabilities. It doesn't mention that will cripple important capabilities. The very first step in the HS3 Quick Start Guide is to change the default user password. The issue with Speaker stems from the fact it must be used along with the so called user 'default'.
Why not make the other tools do the same? It's not that hard to prompt for that information and ensure a minimum of security. HS Touch uses a stored user/password to access. Everything on my network requires a user/password to connect to it. Apparently not, because I won't bend on this one and lower my network security.
#Homeseer speaker client for mac code#
It just says: "Error GetInterfacesList Response status code does not indicate success: 401()."Īgain, why an external tool forces us to lower our security? I thought I'd found an easier way to manage z-wave devices. The Apple IOS app is not so friendly though.
#Homeseer speaker client for mac android#
When it detects your HomeSeer IP, the message from the Android version is rather clear: "Permission denied at HomeSeer, make sure 'No Password Required for Local Network Login' is checked in HomeSeer setup: Response status code does not indicate success: 401()." Even if you can change the default user password.įor the Z-tool mobile app, it's a different issue. In my book, this is a security flaw that needs to be addressed. The only way to clear the error from the log is to use the default user within HS Touch and the speaker clients. At this point, I'm now getting the default user error twice in the log, 1 for the HS machine and one for the workstation. This time I had to up the speaker user access to admin + local for it to connect and some what work (I have another issue with that I will post in another thread). Moved to configure the Speaker client on another machine on the network. But I was still getting the default user error in the log.
That worked for local speaker Client access. So I created a user specifically for that with normal + local access, set the HS-Touch user properties to that user and then updated the user in the Speaker client config. This is when I started getting the error "Speaker host connection refused from 127.0.0.1 User: default User does not exist, does not have adequate rights, or the password is incorrect."
I initially set it to 'No Access' as I didn't have the need for it. In my systems, such a user, known from the entire planet, normally gets deactivated if not deleted. So why is it that 2 of the most common tools used with HS, namely Speaker and Z-Tool, require you to lower your security settings below an acceptable standard? With this, my guess is developers are somewhat security inclined, which makes sense with an application that controls various functionalities in your house and can possibly be accessible from the net. It also has an option called: "No Password Required for Local/Same Network Login (Web Browser/HSTouch)", along with a few others. HS3Pro has some security related options like building a users list with different accesses like guest, normal and admin. Security is important in network applications. It's more a plea to HomeSeer to adopt better practices.
This is more directed to HomeSeer developers.
0 kommentar(er)
