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

[randy]

Jon,

I just tried this utility for the first time and am seeing unexpected behavior in that devices are shown twice in the device manager after grouping--in the group and separately. See below. On reading (some of) this thread, I see it may not be suitable for devices created by plugins (in this case your Jon00RCCNM). Is that the likely issue here, and should I not attempt to use it for these devices?

Thank you.

It will not work well on devices owned by a plug-in as the plug-in takes care of grouping and will likely overwrite whatever you set.

[Wade]

Jon,

I just tried this utility for the first time and am seeing unexpected behavior in that devices are shown twice in the device manager after grouping--in the group and separately. See below. On reading (some of) this thread, I see it may not be suitable for devices created by plugins (in this case your Jon00RCCNM). Is that the likely issue here, and should I not attempt to use it for these devices?

Thank you.

[windracer]

Yes, first delete the parent association for ref 193. This will clear out all the child associations. Next, select it again as the parent device and select devices 194, 281, 363 & 279 as the children.

Thanks, that worked.

[jon00]

Yes, first delete the parent association for ref 193. This will clear out all the child associations.

Next, select it again as the parent device and select devices 194, 281, 363 & 279 as the children.

[windracer]

Back when I was setting up some groups with this plug-in, I must have messed something up because I'm seeing an error in my log every time HS boots about a missing associated device. Is there a way I can clean this up? I tried the "Fix Device/Feature Relationships" button under Setup > Labs, but that didn't clear it out.

V1.0.5 tested/working.
Thank you Jon 😀

[jon00]

Thanks Jon for another very useful plugin;
Been using it for a while and will probably need it even more as I'll shortly migrate a large number of "orphan" HS3 devices to HS4.
Not sure how this will behave, fingers crossed.

Just wanted to suggest a small improvment : I have quite an extensive list of devices and the plugin doesn't seem to have a working scrollbar when selecting devices.
Not a very big deal but this would save a lot of wear on my mouse wheel 😀.
Thanks for considering it in a next release.

Cheers,

Yann

Actually it's been on the cards for some time but you know how it is!

Please try V1.0.5 on my site.

Thanks Jon for another very useful plugin;
Been using it for a while and will probably need it even more as I'll shortly migrate a large number of "orphan" HS3 devices to HS4.
Not sure how this will behave, fingers crossed.

Just wanted to suggest a small improvment : I have quite an extensive list of devices and the plugin doesn't seem to have a working scrollbar when selecting devices.
Not a very big deal but this would save a lot of wear on my mouse wheel 😀.
Thanks for considering it in a next release.

Cheers,

Yann

[jon00]

I found it. It was happening when 1 particular script was running and that script is updating only the devices that I am using as children!!
I run the script every minute so it was always running almost immediately when I enable the event engine.

I apologize for jumping to conclusions -- just was really frustrating.

jon00
The Jon00RCCNMHS3_A.vben script is somehow updating the relationship status for pinged devices.

Any ideas?

Yes, it groups its own devices. I wrote this many years ago so had forgotten what I had done. That's why there is a big warning in the docs about only grouping your own devices as most plugins will want to control their own.

[jhopple]

I found it. It was happening when 1 particular script was running and that script is updating only the devices that I am using as children!!
I run the script every minute so it was always running almost immediately when I enable the event engine.

I apologize for jumping to conclusions -- just was really frustrating.

jon00
The Jon00RCCNMHS3_A.vben script is somehow updating the relationship status for pinged devices.

Any ideas?

[jhopple]

This is really strange!

The fix relationships option fixes this as long as I have the event engine disabled but as soon as I re-enable the event engine the children devices relationship field is set to Not_Set within 10 seconds.

After event engine disabled and fix relationships invoked:



After the event engine is re-enabled:


This is what happens when I use the grouping utility - the relationships are set then almost immediately reset.

[randy]

My current test is using a V3.2 device as root. I am running the latest HS4 (4.1.17.0) version. What versions are you running? Maybe something changed recently?

Node 1532 Status changed after enabling the event engine.

I’m on 4.1.17 as well. I built and grouped a compound device over last weekend.

[jhopple]

I’ve been using Jon’s utility without problem. Like Steve, I’m creating the devices with the legacy device management page, then grouping them with Jon’s utility. I found the same problem trying to build a multi-feature device with the HS4 device management page.

My current test is using a V3.2 device as root. I am running the latest HS4 (4.1.17.0) version. What versions are you running? Maybe something changed recently?

Node 1532 Status changed after enabling the event engine.

[randy]

I’ve been using Jon’s utility without problem. Like Steve, I’m creating the devices with the legacy device management page, then grouping them with Jon’s utility. I found the same problem trying to build a multi-feature device with the HS4 device management page.

[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