Jon00 Device Grouping Utility (web page) for Homeseer 3 & Homeseer 4

[geeTee]

i now used SSH terminal and ran your

install -p /usr/bin/vbc /usr/bin/vbnc

it works! THANK YOU

[Guest]

I have to keep in memory that part of command install -p

instead of ‘’cat’’ with >


Thanks again David

[zwolfpack]

I have to keep in memory that part of command install -p

instead of ‘’cat’’ with >


Thanks again David

FYI, the ">" redirection operator is interpreted by the command line shell, before the 'sudo' is invoked. So anything on the right side of the '>' runs non-privileged.

[msinklair]

I am having a problem loading the page after, I believe, updating mono. Other Jon00 pages work like Links Setp, Days Till Setup, Device Viewer, and Event Viewer. When I try to load Grouping, The homeseer title block and menus are present, but the rest of the page is blank. The chrome tab usually displays a title or the url. When this page is used it says Error.

Thank you for your time,

Max


Date/time=3/4/2021 3:57:53 PM EST
Version=HS4 Standard Edition 4.1.11.0 (Linux)
MONO Version=Mono JIT compiler version 6.12.0.122 (tarball Mon Feb 22 17:29:18 UTC 2021)

License=Registered
License ID=679011
MyHS Subscription=Pro
MyHS Subscription Backup Interval=Daily
MyHS Subscription Max Cameras=10
MyHS Subscription Backup Time=12:00 AM
Confguration File=/usr/local/HomeSeer/Data/HomeSeerData.json
Uptime=1 Day 13 Hours 56 Minutes 48 Seconds
User/Access=723flemingkw (Admin)
Lan IP=10.7.29.19 (729hs)
WAN IP=xxx.xxx.xxx.xxx ()
Device Count=494
Event Count=49
Last Event Ran=Lighting Control : Kitchen Stairway Brighten, Ran at 3/4/2021 3:57:34 PM
# of unique event scripts=8
Plugins Enabled=Z-Wave:,Zigbee:,EasyTrigger:,Unifi:
Modules/Threads=125 Modules, 180 Threads
Available Threads=398
HomeSeer Memory Used=338 Mbytes
Plugins Installed=EasyTrigger 3.0.0.73,Unifi 4.0.6.7,Zigbee 4.0.8.0,Z-Wave 3.0.3.1

[jon00]

Rather than using Jon00Grouping.html, try Jon00Grouping.aspx

What do you see on the screen and HS Log?

[msinklair]

Thank you for the prompt response. The aspx gave a 404 error. That caused me to check the html folder and make sure things were where they are supposed to be. That lead to me noticing a capital J at the beginning of the html and aspx. I replaced the lower case j with a captial, and all is well. The pages open just fine and things work as they should. I appologize for missing that and taking up your time.

[jon00]

Thank you for the prompt response. The aspx gave a 404 error. That caused me to check the html folder and make sure things were where they are supposed to be. That lead to me noticing a capital J at the beginning of the html and aspx. I replaced the lower case j with a captial, and all is well. The pages open just fine and things work as they should. I appologize for missing that and taking up your time.

Nothing to apologize for. Whilst Linux is case sensitive, it is not normal for web page URL's to be so. Unfortunately the HS web server appears to be on Linux.

[jhopple]

jon00 This utility doesn't seem to be working correctly any more with the latest HS4 release (4.1.17.0). When I try to move a set of devices under a root it appears that the root device is updated with the list of children/features but the children are not mark as children. So when looking at the device list the features are listed both as stand alone and under the root device. I have used this utility before successfully. Something must have changed in the recent releases that broke it.

Non-Feature device

Child of Root device

Thanks
J.Hopple

[jon00]

I seem to remember there was a change from HS4 creating HS3 devices (V3.2) to HS4 devices (V4). Therefore its possible that you are trying to group 2 different device types together. As my Network monitor works for HS3 & HS4, they would be 3.2 devices.

If you create a device via the old HS3 interface as your root, it may work. Other than that,I'm not sure. Unfortunately, I may have to make this EOL if there are issues between the two device versions.

[jhopple]

You are right the root device is a V4 device and the children are V3.2 and this did work a few months ago.
Hopefully you can make this work as this was really useful for device organization with the new V4 device layout (root/feature).

Thanks
J.Hopple

[jon00]

As I said, you can create V 3.2 devices via the old HS3 interface (/deviceutility rather than /devices.html)

Create your root there and see if that works.

[jhopple]

Sorry, missed that part of your response. Unfortunately the result is the same. The child devices are not marked as children with the root device as parent.

J.Hopple

[jon00]

Have you tried Setup / Labs - Fix Device/Feature Relationships?

[jhopple]

Ok, this getting really weird!!! Something in HS is ACTIVLEY breaking the relationships of these devices as the relationships are made!!

As you suggested I tried the Fix Device/Features Relationships option. The log said it was fixing it. I restarted HS but the devices were still the same. I decided to tried some other experiments.

I noticed after creating the root/children relationships with the grouping utility that the device display was actually correct for 5 to 10 seconds. After continually refreshing the page the child devices were again displayed as standalone a few at a time. I was able to view a child device and it was marked as a child then a few seconds later it updated to Not_Set. Something was changing the relationship status for the children in the background. I figured the only thing that would be doing background processing was the event engine so I went and disabled it. I then used the Fix Relation option again. This time the relationships held and stayed correct. Then I enabled the event engine and the child devices were immediately updated to Not_Set.

So to summarize there is some background process that is actively changing some device relationships for some unknown reason.

rjh


Perhaps some HS guys could chime in here and explain what is happening?
Is this using this utility just a really bad idea?
This used to work and didn't seem to cause any issues.

J.Hopple

[SteveMSJ]

Perhaps some HS guys could chime in here and explain what is happening?
Is this using this utility just a really bad idea?
This used to work and didn't seem to cause any issues.

J.Hopple

I used the utility just the other day to create a virtual device group with a root and several children in HS4 and it worked fine, as it always has. The difference is probably that I created all the devices as HS3 devices using the old web pages. As you have found there is probably an issue with HS4 devices.

In theory with HS4 you don't need the utility. If you create a new Virtual device you get a root and one child/feature. You can then use the copy function on the child/feature to create as many children as you want and they are all grouped with the root. I did this and thought, great something that works better in HS4 than in HS3! I then started configuring the features with status pairs but no matter what I did I couldn't get the Status to show the prefix and post fix despite it all appearing to be configured correctly. There appears to be a bug with HS4 virtual devices configured manually. I gave up and created the devices through the old web pages and they worked fine, albeit requiring Jon00s utility to group them.

Steve