You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I jokingly post this, but iOS's policy of hiding device identifiers makes Summon very difficult to use.
More seriously, what is the workflow supposed to be on iOS? Say I have 10 powerblades. I plug them in. I now want to associate each device with what I plugged into it. I cannot just scan and populate a list, because I have no idea which PowerBlade is which. Is the iOS app supposed to connect to each one and read a characteristic which presumably has been programmed into the device to contain the MAC address? What if my device doesn't (or can't) support connections? If we standardize this service and characteristic so that summon can use it, wouldn't iOS block that too? Taken to the logical end, the OS could block any attempt to subvert the ID hiding mechanism.
Is there some other way to commission devices? Do you have to plug them in one at a time?
The text was updated successfully, but these errors were encountered:
I jokingly post this, but iOS's policy of hiding device identifiers makes Summon very difficult to use.
More seriously, what is the workflow supposed to be on iOS? Say I have 10 powerblades. I plug them in. I now want to associate each device with what I plugged into it. I cannot just scan and populate a list, because I have no idea which PowerBlade is which. Is the iOS app supposed to connect to each one and read a characteristic which presumably has been programmed into the device to contain the MAC address? What if my device doesn't (or can't) support connections? If we standardize this service and characteristic so that summon can use it, wouldn't iOS block that too? Taken to the logical end, the OS could block any attempt to subvert the ID hiding mechanism.
Is there some other way to commission devices? Do you have to plug them in one at a time?
The text was updated successfully, but these errors were encountered: