Bond Integration built-in app. How to remove device?

I successfully installed the Bond Integration built-in app and connected it to my Bond Bridge. I created a test device on the Bond Bridge using the Bond Home app and the test device successfully showed up as a child to my Bond Bridge device on HE. I then removed the test device from the Bond Bridge using the Bond Home app and went over to my HE Bond Bridge device to remove the child device. I couldn't remove it though because the "Remove Device" button in the lower right corner of the device page was greyed out.

Ok, I thought, I'll show you. Surely it will be removed if I refresh the parent Bond Bridge device. So I hit the Refresh button on the parent device, but nothing happened. So I hit the Configure button instead. This time I got error messages in the logs. A 404 trying to connect to the test device. I'm not surprised, I thought, seeing that I removed it from Bond Home. But the child device remained on HE.

So I left it for a day to let it think about things and I checked back in today to see what the status was. The child test device is still there, and no further messages in the log file at all, even though debug logging was still enabled. I tried hitting Configure on the parent device "Bond Bridge" (device ID 1 btw), but this time got a few 408 errors. I tried it again, but still got the 408 errors. Log file below.

[dev:1]2022-06-13 23:09:02.826 [error]gotDevices - resp: 408

[dev:1]2022-06-13 23:09:02.824 [error]gotVersion - resp: 408 - null

[dev:1]2022-06-13 23:09:02.824 [error]gotBpup - resp: 408

[dev:1]2022-06-13 23:08:45.444 [debug]configure()

[dev:1]2022-06-13 23:07:07.689 [error]gotVersion - resp: 408 - null

[dev:1]2022-06-13 23:07:07.689 [error]gotDevices - resp: 408

[dev:1]2022-06-13 23:07:07.689 [error]gotBpup - resp: 408

[dev:1]2022-06-13 23:06:49.728 [debug]configure()

[dev:1]2022-06-12 17:51:37.198 [error]gotDeviceState - resp: 404 - [deviceId:675a4a36]

[dev:1]2022-06-12 17:51:37.196 [debug]gotDeviceState [deviceId:675a4a36]

[dev:1]2022-06-12 17:50:37.580 [debug][_:5aa87d64]

[dev:1]2022-06-12 17:50:37.512 [debug][target:zermatt, fw_ver:v2.28.0, fw_date:Tue Nov 2 19:07:06 UTC 2021, uptime_s:1224, boot_patch:not first boot, make:Olibra, model:BD-1000, branding_profile:OLIBRA_BD1000, bondid:REDACTED, upgrade_http:true, api:2, _:REDACTED] - null

[dev:1]2022-06-12 17:50:37.442 [debug][broadcast:true, _:216bcfd0]

[dev:1]2022-06-12 17:50:32.249 [debug]configure()

deviceId:675a4a36 that it keeps referring to is the test device that I have removed from Bond Home.

How do I remove Bond Home child devices from HE? I realise that I can probably just delete the parent device and remove the bridge from the Bond Integration app, or even remove the whole app as well, but I'd like to know what procedure I should take to remove a device for the future as I wouldn't want to do that once I have added all my Bond devices to it.

Tagging @bcopeland from Hubitat.

1 Like

Ah… This likely needs to get fixed.. Chacking

3 Likes

Also, if the device name (ceiling fan) is changed on the Bond hub, the child device doesn't track the change and can't be updated manually.

Hey @bcopeland. Would this be fixed with a hotfix in this release or will it be fixed in future releases?

Most likely coming in Hub FW 2.3.3 release, which is WIP at the moment.

1 Like

I have the same two issues

  1. Can't delete a device added in Bond from Hubitat, either before or after it is deleted in Bond. So basically, once a device is added in Bond to a Bond linked to HE, it is in Hubitat forever...
  2. If I edit the name in Bond, HE does not update the name.

Looking forward to a fix....

I see this hasn't been fixed in 2.3.3 and isn't listed on the "Known Issues in 2.3.3.122" thread. Is a fix still planned?

1 Like

Bryan has stated a fix will for removing devices will be included in an updated release of the Bond integration, timing still TBD. Unless and until he reverses that statement we can expect that fix (and other updates) is coming.

Bond integration updates did not make the 2.3.3 release, except for one key tweak to fix a couple of typos w/the fan light "on/off" reporting.

https://community.hubitat.com/t/2-3-3-116-solved-bond-off-fan-light-state-not-correctly-handled-in-if-then-logic-in-button-controller-and-rule-machine-apps/101075/1

Hopefully the other (bigger/more complex) updates/fixes will be coming in 2.3.4, but we'll have to wait to see about the timing - HE doesn't like to pre-announce things.

1 Like

I have a workaround to get rid of any extra child devices.
You will need this custom driver (just for the delete child command): [RELEASE] Z-Wave Universal Device Scanner

Remove the device from the Bond App FIRST.
Go to the child you wish to remove and copy the DNI into a notepad or something handy.
Change the parent Bond Bridge device to this custom driver.
Fill in the child DNI to the box below the Delete Child command, and press the button.
Switch the driver back to "Bond Bridge"

If the device is still setup in the Bond mobile app, I believe it will eventually get added back automatically or if you press configure on the Bond Bridge device (once set back to the Bond Bridge driver).

As for the names not updating as stated above by someone else, just put your desired "friendly" name in the "Label" box in the child. The "Name" is locked because the childs are created as component device.

Nice! Will try tomorrow. Dealing with kitchen reno today.

Worked as advertised.

I'm ignoring my the Bond children I want to remove for now, holding back so I can help test when the Bond Integration w/child removal is available.

Basically following the same process I did w/my own children when they were teenagers and I could not remove them. I just ignored them. :wink:

2 Likes

Download the Hubitat app