Actually makes more sense to do it this way anyway.
Alexa Cloud → Bond Cloud → Bond Local
vs
Alexa Cloud → ST Cloud → ST Local → Bond Local
1 Like
Bond Bridge 2023-09-13.22.39.32.82
- Fixed driver startup bug related to network credentials for the Bond device (prevents finding the bridge)
- Fixed crash related to nil tables from ST
Thanks to @EB_1 for log files on the first issue 
Is anyone else experiencing issues with Bond edge drivers? I can add the devices on the bond device to my smartthings without issue and they work after adding.
However after a few hours, they seem to loose connectivity and show as offline in smartthings, but they do work from bond app.
With Edge drivers, any issues are more likely to be local since there is not a shared cloud component. If you can get logs, it would help indicate why they are offline. You can also tray refreshing your Bond hub or restarting your ST hub.
Thanks - will try. Which logs would you suggest to get? From SmartThings hub?
I turned on the tracing using this post: https://community.smartthings.com/t/how-to-enable-logging-on-the-hub/230465/73?u=paul88
What would be helpful for you - discovery of devices, or just attempts to connect to the driver when it shows off line in smarting’s
I would be looking for logs that show the switch from online to offline. If you can’t get that, I would look for a log of the bond hub refresh
Any quick pointers how to enable and get those logs. Want to make sure I get you the right logs
From your post above, it looks like you already have it enabled. You just need to have it on while you use the driver, and copy and paste the log in a DM
I found I had a loop in my network and that was the reason the Bind Bridge devices were dropping off. With that fixed, moving onto the next step.
I have bond bridge pro which allow partial opens - and this works perfectly on bond bridge app. However in ST, it seems the driver is receiving status info about the blind - as it can see percentage open, however it is not able to control the blind that is configured with partial open “set position” open.
Driver issue or user issue? 
I don’t understand the question. Are you saying it reflects the correct percentage, but you are unable to set a percentage?
Actually - cannot send open/close/percent commands from ST. The device receives updates about its status but cannot be controlled
ST team broke the hub device with their most recent app release. I’ll have to see what they did and if it can be undone. The newest version of the app looks like it is ignoring my custom presentation.
I am addressing it with them via DM and will update the driver when I get a resolution.
1 Like
Finally circling back to resolving this issue - to recap, Bond devices don’t appear on iOS, but do appear without issue on Android devices.
Today I fully removed the hub and all devices and re-discovered. iOS app discovered the Bond Bridge and devices without issue. Went back into the iOS app and they arenot visible, except for a fan, within the iOS app, but are visible in ST Advanced and Android apps. The only thing I can think of is this is some sort of issue with the “Generic” device profile and iOS, as the Fan device is visible in iOS but all Generic devices are not. Automations and such work without issue.
Generic is just a switch profile, but uses the IR blaster icon. Maybe iOS has an issue with that icon. There is nothing custom in that profile. Can you try changing the icon from the Android app?
This is a pretty long thread, and appologies if this was covered. I added the driver and was able to discover bond and devices. At first, devices were not updating in ST until i manually did an action to a device in bond app.
Once updated, i can’t actually control anything. Clicking any action in ST gives me a spinning icon, and log is showing the following:
2023-11-09T23:50:24.002748503+00:00 TRACE Bond Bridge Received event with handler capability
2023-11-09T23:50:24.009259336+00:00 INFO Bond Bridge <Device: 180b3cfe-225f-42a5-a57b-b9a4a6dc0a67 (Office Fan)> received command: {"command":"setFanSpeed","capability":"fanSpeed","component":"main","args":{"speed":2},"positional_args":[2]}
2023-11-09T23:50:24.010132878+00:00 TRACE Bond Bridge Found CapabilityCommandDispatcher handler in Bond
2023-11-09T23:50:24.010807128+00:00 ERROR Bond Bridge Office Fan thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <Device: 180b3cfe-225f-42a5-a57b-b9a4a6dc0a67 (Office Fan)>:
arg1: table: 0xc3f8a0```That error is coming from the firmware on the ST hub. It is indicating that an error occurred while handling the set fan speed event, but is not showing the error. If you have more of the log, that would help.
Based on your description, if nothing was updating, it sounds like you did not get your bond hub linked. I would power cycle your Bond hub, and then try to perform any action on one of your Bond devices within the ST app.
Rebooted bond. Also added a device as new (office fan v2)
2023-11-10T00:37:13.676883142+00:00 WARN Bond Bridge bpup message dispatcher handler on driver thread encountered error: [string "init.lua"]:158: attempt to index a userdata value (field 'token')
2023-11-10T00:37:13.677744850+00:00 DEBUG Bond Bridge <Device: 561d6968-1ab5-4795-a716-342f0f49239b (Bond Bridge)> online
2023-11-10T00:37:13.928549600+00:00 DEBUG Bond Bridge session 16: uptime 60 minutes, memory 614 KB
2023-11-10T00:37:13.930302558+00:00 DEBUG Bond Bridge driver device thread event handled
2023-11-10T00:38:13.515771016+00:00 DEBUG Bond Bridge PING 10.10.11.55 30007 nil
2023-11-10T00:38:13.517753433+00:00 DEBUG Bond Bridge driver device thread event handled
2023-11-10T00:38:13.733482558+00:00 DEBUG Bond Bridge bpup message received 10.10.11.55 30007 {"B":"ZZDI38290","d":0,"v":"v3.17.4"}
2023-11-10T00:38:13.743546350+00:00 WARN Bond Bridge bpup message dispatcher handler on driver thread encountered error: [string "init.lua"]:158: attempt to index a userdata value (field 'token')
2023-11-10T00:38:13.744433975+00:00 DEBUG Bond Bridge <Device: 561d6968-1ab5-4795-a716-342f0f49239b (Bond Bridge)> online
2023-11-10T00:38:13.937757558+00:00 DEBUG Bond Bridge session 16: uptime 61 minutes, memory 614 KB
2023-11-10T00:38:13.939647725+00:00 DEBUG Bond Bridge driver device thread event handled
2023-11-10T00:39:13.526524212+00:00 DEBUG Bond Bridge PING 10.10.11.55 30007 nil
2023-11-10T00:39:13.528515587+00:00 DEBUG Bond Bridge driver device thread event handled
2023-11-10T00:39:13.588619462+00:00 DEBUG Bond Bridge bpup message received 10.10.11.55 30007 {"B":"ZZDI38290","d":0,"v":"v3.17.4"}
2023-11-10T00:39:13.598954628+00:00 DEBUG Bond Bridge <Device: 561d6968-1ab5-4795-a716-342f0f49239b (Bond Bridge)> online
2023-11-10T00:39:13.601658920+00:00 WARN Bond Bridge bpup message dispatcher handler on driver thread encountered error: [string "init.lua"]:158: attempt to index a userdata value (field 'token')
2023-11-10T00:39:13.948513628+00:00 DEBUG Bond Bridge session 16: uptime 62 minutes, memory 614 KB
2023-11-10T00:39:13.950413378+00:00 DEBUG Bond Bridge driver device thread event handled
2023-11-10T00:39:26.422668801+00:00 TRACE Bond Bridge Received event with handler capability
2023-11-10T00:39:26.430277093+00:00 INFO Bond Bridge <Device: 77110700-b7e4-49ee-9147-3fe5ae5f8626 (Office Fan v2)> received command: {"command":"on","capability":"switch","component":"main","args":{},"positional_args":{}}
2023-11-10T00:39:26.432584009+00:00 TRACE Bond Bridge Found CapabilityCommandDispatcher handler in Bond
2023-11-10T00:39:26.436931134+00:00 ERROR Bond Bridge Office Fan v2 thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <Device: 77110700-b7e4-49ee-9147-3fe5ae5f8626 (Office Fan v2)>:
arg1: table: 0xc436b8
[string "init.lua"]:158: attempt to index a userdata value (field 'token')
2023-11-10T00:39:34.852658055+00:00 TRACE Bond Bridge Received event with handler capability
2023-11-10T00:39:34.860399888+00:00 INFO Bond Bridge <Device: 77110700-b7e4-49ee-9147-3fe5ae5f8626 (Office Fan v2)> received command: {"command":"setFanSpeed","capability":"fanSpeed","component":"main","args":{"speed":1},"positional_args":[1]}
2023-11-10T00:39:34.866532805+00:00 TRACE Bond Bridge Found CapabilityCommandDispatcher handler in Bond
2023-11-10T00:39:34.867303055+00:00 ERROR Bond Bridge Office Fan v2 thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <Device: 77110700-b7e4-49ee-9147-3fe5ae5f8626 (Office Fan v2)>:
arg1: table: 0xc2cca8
[string "init.lua"]:158: attempt to index a userdata value (field 'token')
2023-11-10T00:39:40.890312641+00:00 TRACE Bond Bridge Received event with handler capability
2023-11-10T00:39:40.897717558+00:00 INFO Bond Bridge <Device: 77110700-b7e4-49ee-9147-3fe5ae5f8626 (Office Fan v2)> received command: {"command":"on","capability":"switch","component":"light","args":{},"positional_args":{}}
2023-11-10T00:39:40.899926016+00:00 TRACE Bond Bridge Found CapabilityCommandDispatcher handler in Bond
2023-11-10T00:39:40.903752641+00:00 ERROR Bond Bridge Office Fan v2 thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <Device: 77110700-b7e4-49ee-9147-3fe5ae5f8626 (Office Fan v2)>:
arg1: table: 0xc5a650
[string "init.lua"]:158: attempt to index a userdata value (field 'token')```It looks like the driver is having trouble with the preferences for the device. You can no longer access those preferences due to this issue introduced by the ST team in the latest app upgrade.
@AlejandroPadilla Can you verify that this issue with hub devices would also prevent users from accessing the preferences for those devices?
If the profile’s categories is Bridges, replacing that with Others (or maybe other categories) will fix it.
categories:
- name: Others