[RELEASE] HubConnect - Share Devices across Multiple Hubs (even SmartThings!)

As per this thread:

It seems the lock codes aren't getting passed or logged or something from Hub to Hub. I can post details of whatever is needed.

I do see in the logs of the hubconnect lock device that it seems the control hub is getting passed to it the lock code as referenced in the link above. However no triggers are hitting RM from that device.

These are the events from the HubConnect lock device:
image

So it seems to be seeing the individual user.

This is the event log from the RM rule:
image

Nothing.

This is the rule:
image

I tested with a RM rule on the hub with the zigbee lock device and was able to toggle a bulb based on a specific user unlocking the lock. So it seems something is amiss in hubconnect?

On my "stub hub" (the hub with a stub driver for the lock vs the hub with the real lock :slight_smile: ) I'm seeing the Event(s):


and the Logs show:

app:33 2019-08-30 10:46:34.067 am debug Sending event to ZeeHomebridge: Yale DoorLock [lock: unlocked null]
app:2 2019-08-30 10:46:34.030 am info  Received event from ZeeRadioLower/Yale DoorLock: [lock, unlocked null]

I'll try creating a similar Rule...

Yes, I'm seeing them there too. But when used in the rule I showed above. Nothing triggers and the rule events show no activity. Curious to see what happens when you create a similar rule.

Duplicated it. Same result as you.

Hi guys.
Just got a second HE hub and using this great app on both hubs.
On my second (slave) hub I have access to my Dimmer switches on my first (master) hub.
With WebCoRe on the slave hub if I use the set level command nothing happens but turn on works OK.
The dimmer on the slave is using the HubConnect dimmer driver.
Is this known issue or am I doing something wrong.
TIA
EDIT. Also seeing this error using RM4.
I'm seeing this in the logs for the dimmer on the master hub.

Tagging @srwhite

In the post above I am getting an error when trying to set the level on a dimmer defined on the master from a rule on the slave/remote.
Is anyone else getting this error when trying to set dimmers?

I don't have that circumstance, personally. All my Rules exist on the hub where the real devices are located.

My 'coordinator' hub gets a ton of event info, largely because I have every real device and many Virtual devices 'mirrored' to 'coordinator.' But all my Rules there are 'coordinator' functions. All my door window sensors are sent to 'coordinator' (for dashboard) and therefore it's the bst place to put a single "perimeter alert" Rule, as one example.

Like a lot of people, I have switches, dimmers and outlets all de/activating from what a Motion Sensor is indicating. Motion = lights on or temp = fan on. Not all Motion Sensors are on the same hub as the switches, dimmers and outlets... but in my case, I always 'mirror' the Motion Sensor, never the switch/dimmer/outlet.

I don't know that it counts BUT the one exception I can find is a Motion Sensor / Hampton Bay Fan Controller Rule. The Rule is on the hub with the Motion sensor and is setting fan Levels on a Fan that has been mirrored from another hub. Thanks for asking, allowing me to find this exception... I'll probably "fix it" so that it follows my pattern. :smiley:

Sorry if I'm being dense here but are you saying there is an issue here and you are going to have a look at it?
What I'm trying to do is run webCoRE exclusively on my remote hub to see how it runs. I have RM4 rules on my server hub that I've disabled and can use but I'm playing I suppose. :smile:

Not exactly.

I'm saying I don't have a match on your question. I'm waiting to see if others respond that they have the same circumstances and it's working OR they do and it's failing for them too.

I'm still chasing @jrfarrar issue. What's that make me? 2 behind? :smiley:

I've probably misunderstood how this set up should work then.
Thanks for the reply.

I don't think so...

A dimmer on one hub should 'mirror' completely to the remote hub.

I'm sure that in the thousands of tests I've done for HubConnect releases, I've done what you're asking. But I can't document it. I know I've done setLevel for fans. I know that setLevel properly mirrors, because of that effort. But Dimmers are one of the very first things I tested and once it worked, and no changes have been made in that area, I've not retested.

I have a dashboard that is on 'coordinator' where there are no "real" devices. Dashboard has a LOT of dimmers. They work.

It's the setLevel command being sent from the remote hub to the server hub where the device is hosted that's not working and throwing the error on the master hub.

yes.

dev:1224 2019-08-31 11:36:39.588 am info Office Ceiling Controller light was set to 20%
app:837 2019-08-31 11:36:39.448 am info Received command from server: ["Office Ceiling Light": setLevel]
dev:1224 2019-08-31 11:36:38.171 am info Office Ceiling Controller light was set to 43%
dev:1224 2019-08-31 11:36:38.168 am info Office Ceiling Controller light was turned on
app:837 2019-08-31 11:36:38.133 am info Received command from server: ["Office Ceiling Light": setLevel]

That's all the logs on my hub with the real device caused by clicking the dimmer on Dashboard (which is NOT on this hub)

Hmm. Not sure what to say.
Rule on remote sets the dimmer on the remote using hubConnect dimmer to 20%.
Logs says its set the dimmer on the remote.
On the server the device does nothing and I see this in the logs on the server.
image
If I use Turn On instead of setLevel then the dimmer turns on OK using the last level that the dimmer was set to.
Looks like I'm not able to use the dimmers this way.

Show me your Rule so I can duplicate the Rule

Very simple rule just to test it.
This throws the error shown above on the server hub.
The rule is on the remote hub against the hubconnect dimmer device.

image

As an aside I'm also seeing this error on the server hub.
image
This is against the remote hub.
image

01%20PM

Rule created on 'coordinator' and the logs show:

app:65  2019-08-31 12:47:09.258 pm debug Sending event to ZeeSmart: MultiSenDomeU (office3) [motion: active null]
app:3   2019-08-31 12:47:09.230 pm info  Received event from ZeeRadioUpper/MultiSenDomeU (office3): [motion, active null]
app:33  2019-08-31 12:46:44.803 pm debug Sending event to ZeeHomebridge: Office Ceiling Light [level: 50 null]
app:3   2019-08-31 12:46:44.770 pm info  Received event from ZeeRadioUpper/Office Ceiling Light: [level, 50 null]
app:33  2019-08-31 12:46:44.000 pm debug Sending event to ZeeHomebridge: Office Ceiling Light [switch: on null]
app:3   2019-08-31 12:46:43.964 pm info  Received event from ZeeRadioUpper/Office Ceiling Light: [switch, on null]
app:33  2019-08-31 12:46:43.821 pm debug Sending event to ZeeHomebridge: Office Ceiling Light [level: 50 null]
app:451 2019-08-31 12:46:43.819 pm info  Action: END-IF
app:3   2019-08-31 12:46:43.784 pm info  Received event from ZeeRadioUpper/Office Ceiling Light: [level, 50 null]
app:451 2019-08-31 12:46:43.783 pm info  Action:     Dim: Office Ceiling Light: 50
app:451 2019-08-31 12:46:43.782 pm info  Action: IF (MultiSensor6A (officeDesk) active(T) [TRUE]) THEN
app:451 2019-08-31 12:46:43.744 pm info  Bobbles Test Triggered
app:451 2019-08-31 12:46:43.734 pm info  Bobbles Test: MultiSensor6A (officeDesk) motion active
app:65  2019-08-31 12:46:43.703 pm debug Sending event to ZeeSmart: MultiSensor6A (officeDesk) [motion: active null]
app:3   2019-08-31 12:46:43.673 pm info  Received event from ZeeRadioUpper/MultiSensor6A (officeDesk): [motion, active null]
app:451 2019-08-31 12:46:43.495 pm info  Action: END-IF
app:451 2019-08-31 12:46:43.431 pm info  Action:     Dim: Office Ceiling Light: 50
app:451 2019-08-31 12:46:43.428 pm info  Action: IF (MultiSensor6A (officeDesk) active(T) [TRUE]) THEN
app:451 2019-08-31 12:46:43.390 pm info  Bobbles Test Triggered
app:451 2019-08-31 12:46:43.383 pm info  Bobbles Test: MultiSensor6A (officeDesk) motion active
app:65  2019-08-31 12:46:43.347 pm debug Sending event to ZeeSmart: MultiSensor6A (officeDesk) [motion: active null]
app:3   2019-08-31 12:46:43.307 pm info  Received event from ZeeRadioUpper/MultiSensor6A (officeDesk): [motion, active null]

The Hub that has the Real Device logs show:

dev:1224 2019-08-31 12:46:41.091 pm info Office Ceiling Controller light was set to 50%
app:837  2019-08-31 12:46:40.245 pm info Received command from server: ["Office Ceiling Light": setLevel]
dev:1224 2019-08-31 12:46:40.110 pm info Office Ceiling Controller light was set to 50%
dev:1224 2019-08-31 12:46:40.109 pm info Office Ceiling Controller light was turned on
dev:845  2019-08-31 12:46:40.008 pm info MultiSensor6A (officeDesk) motion active
app:837  2019-08-31 12:46:39.930 pm info Received command from server: ["Office Ceiling Light": setLevel]
dev:845  2019-08-31 12:46:39.617 pm info MultiSensor6A (officeDesk) motion active
dev:845  2019-08-31 12:46:19.009 pm info MultiSensor6A (officeDesk) motion inactive

The difference includes the real driver we are using.. mine is a Hampton Bay Fan Controller, and I'm dimming the child driver of "Ceiling Light"

You're error is showing Missing Method Exception ... setLevel() from dev:101 which is your Lightwave driver... do you have another dimmer using a different driver?

I changed to a different device/driver and got the same "normal" result:

dev:744 2019-08-31 01:01:26.204 pm info Lutron Dimmer Module was set to 50% [digital]
dev:744 2019-08-31 01:01:26.202 pm info Lutron Dimmer Module was turned on [digital]
app:837 2019-08-31 01:01:25.072 pm info Received command from server: ["Lutron Dimmer Module": setLevel]
dev:845 2019-08-31 01:01:24.831 pm info MultiSensor6A (officeDesk) motion active
app:837 2019-08-31 01:01:24.753 pm info Received command from server: ["Lutron Dimmer Module": setLevel]
dev:845 2019-08-31 01:01:24.439 pm info MultiSensor6A (officeDesk) motion active

Well done.
Just tried it on a Fibaro Dimmer 2 and it worked as expected. Light turned on to 20%. That error has now gone.
I'll have to look at that driver. I ported it over from ST. Going to be a bit cheeky here. :wink:
What should I look for in the driver that could be wrong. Any thoughts?

BTW I am still seeing this error though against the remote hub in the server hub logs.