Can some one point me to right direction please? I am trying to figure out best way to set up HS system so I have full system access and customer has limited access needed for using HS touch and mobile app. I am struggling to get it done.
Here is scenario:
HS3 Setup installed. That includes HS3 Server, wall mounted iPad. UI designed with HS Touch deployed to iPad(s). Mobile app used on phones.
I want to have one login for user (homeowner) that can be used with HS Touch client, Homeseer Mobile and MyHS service without having them having access to web interface so they can't make changes.
Also when they install Homeseer mobile I don't want them to see all event and devices. I can have hundreds of status devices that are used internally only to change graphic on iPad (motion, lights etc.) and same goes for events.
It makes mobile app really very difficult to use for regular customer if suddenly there are hundreds of useless devices they can't control. That's one reason I am staying away from Homeseer mobile for now.
I understand I can hide devices from Homeseer Mobile but guess what? You hide status device that is useless for customer but important for HS touch project to show status of motion in the room on iPad for example. It will hide it form Homeseer mobile which is great but it will also hide it from HS Touch so icon that was supposed to change based on status device on iPad controller is now gone as well. Not so cool anymore.
What do I do about events?
In other words, PLEASE, tell me how do I setup HomeSeer system so customer can fully enjoy and use all HS Touch, HomeSeer Mobile app with devices and events that I want them to see and at the same time restrict the access to settings (adding and removing devices, creating, changing and running event from HS3 web interface)?
When I sell the system, I want to make sure customer can't make changes to the system, run events that they are not supposed to run but still enjoy all benefits of custom system. Isn't that what they pay for?
There has to be way to set it up like that or it can be nightmare for installers to offer and sell it due to customer's full system access.
Thanks in advance for your tips. Charles
Here is scenario:
HS3 Setup installed. That includes HS3 Server, wall mounted iPad. UI designed with HS Touch deployed to iPad(s). Mobile app used on phones.
I want to have one login for user (homeowner) that can be used with HS Touch client, Homeseer Mobile and MyHS service without having them having access to web interface so they can't make changes.
Also when they install Homeseer mobile I don't want them to see all event and devices. I can have hundreds of status devices that are used internally only to change graphic on iPad (motion, lights etc.) and same goes for events.
It makes mobile app really very difficult to use for regular customer if suddenly there are hundreds of useless devices they can't control. That's one reason I am staying away from Homeseer mobile for now.
I understand I can hide devices from Homeseer Mobile but guess what? You hide status device that is useless for customer but important for HS touch project to show status of motion in the room on iPad for example. It will hide it form Homeseer mobile which is great but it will also hide it from HS Touch so icon that was supposed to change based on status device on iPad controller is now gone as well. Not so cool anymore.
What do I do about events?
In other words, PLEASE, tell me how do I setup HomeSeer system so customer can fully enjoy and use all HS Touch, HomeSeer Mobile app with devices and events that I want them to see and at the same time restrict the access to settings (adding and removing devices, creating, changing and running event from HS3 web interface)?
When I sell the system, I want to make sure customer can't make changes to the system, run events that they are not supposed to run but still enjoy all benefits of custom system. Isn't that what they pay for?
There has to be way to set it up like that or it can be nightmare for installers to offer and sell it due to customer's full system access.
Thanks in advance for your tips. Charles
Comment