After almost fifteen years as a Homeseer user, it looks like it's time to "throw in the towel". My primary usage of Homeseer is thru my desktop and HSTouch screens. The new HS4 GUI and grouping strategies are just not working out. I've tried using the workarounds from Jon00 and really appreciate his efforts, but it creates more and more of a " kluge" and is not a real solution. And sorting things on a browser is impossible.
HS4 is being built for an audience which doesn't seem to include me.
Am I the only one who has given up? Hate to throw away years of work (16 plugins, 100 Zwave nodes, 1wire network, multiple screens, lots of scripts and many more) but this is driving me crazy. So the real question is a) different vendor, or b) just freeze my installation ?
Would appreciate other folks views since this forum has been so valuable for a lot of years.
Thanks, Bruce
Okay - seems like I kicked off a lot of discussion. So let me add a few thoughts based on what has come in.
a) My environment is a large single story home with a server room. Custom built water cooled computers, 10G fiber optics, five screens on my desk, mostly Windows with Apple and Echo devices in various locations. Certainly not the most sophisticated setup, but not really a "mobile" orientation. I do come in remotely a lot thru my DNS service. Consider my self an "early adopter" and after 30+ yrs in the IT business - really love technology!
b) Building HSTouch screens is okay for certain rooms, but my desire is for "at a glance" desktop capability. Have been unable to look at things FUNCTIONALLY. And sort all 450+ devices by name within functions. Have tried multiple naming schemes using locations, categories and device names Don't have a need to see ( for instance) the root device, notifications, or battery, etc when I lookdown the list at lock status with controls under the function of security.
c) have had no issues with HS4 from a stability of function standpoint. Cost is not a big concern. Screen sizing is currently not very helpful.
d) have used many of the workarounds for breaking apart parent/child, using old HS3 screens, etc - stiil a mess.
e) it really, really goes against the grain to think about recessing to an older product and being "stuck" in a back dated, non supported version of anything. Hence, my frustration.
Thanks to everyone for their thoughts and ideas.
HS4 is being built for an audience which doesn't seem to include me.
Am I the only one who has given up? Hate to throw away years of work (16 plugins, 100 Zwave nodes, 1wire network, multiple screens, lots of scripts and many more) but this is driving me crazy. So the real question is a) different vendor, or b) just freeze my installation ?
Would appreciate other folks views since this forum has been so valuable for a lot of years.
Thanks, Bruce
Okay - seems like I kicked off a lot of discussion. So let me add a few thoughts based on what has come in.
a) My environment is a large single story home with a server room. Custom built water cooled computers, 10G fiber optics, five screens on my desk, mostly Windows with Apple and Echo devices in various locations. Certainly not the most sophisticated setup, but not really a "mobile" orientation. I do come in remotely a lot thru my DNS service. Consider my self an "early adopter" and after 30+ yrs in the IT business - really love technology!
b) Building HSTouch screens is okay for certain rooms, but my desire is for "at a glance" desktop capability. Have been unable to look at things FUNCTIONALLY. And sort all 450+ devices by name within functions. Have tried multiple naming schemes using locations, categories and device names Don't have a need to see ( for instance) the root device, notifications, or battery, etc when I lookdown the list at lock status with controls under the function of security.
c) have had no issues with HS4 from a stability of function standpoint. Cost is not a big concern. Screen sizing is currently not very helpful.
d) have used many of the workarounds for breaking apart parent/child, using old HS3 screens, etc - stiil a mess.
e) it really, really goes against the grain to think about recessing to an older product and being "stuck" in a back dated, non supported version of anything. Hence, my frustration.
Thanks to everyone for their thoughts and ideas.
Comment