Andrei Litvin
Andrei Litvin
Unassigning this to give priority to cert blockers for now.
V1 review: fixes in master for this are bug fixes and would be acceptable, however this is not a V1 blocker.
Failed to create python controller, Missing vendor ID and Failed to bringup CHIPDeviceController CLI
I do not think chip-device-ctrl is a supported interface anymore. We are looking to support chip-repl along side chip-tool.
Failed to create python controller, Missing vendor ID and Failed to bringup CHIPDeviceController CLI
Accepting patches in case of life support because this will not change core functionality, only python.
V1 review: @mrjerryjohns and @tehampson to review and provide justification if this needs to be a v1.0 blocker.
Decreased blocking status based on comment from @mrjerryjohns above (Jerry added the p1 flag oringally)
is chip-tool running avahi or all-clusters or both?
I am reading through the issue, am still unclear how to reproduce. I see the comment was "I can reproduce the issue by starting the lighting-app without even invoking chip-tool"....
`NodeLookupHandle` is supposed to represent an active lookup. While it is active, the lookup is expected to processed and once inactive (removed from internal lists) the dnssd lookups are not...
Needs more debugging I guess - have to figure out: - does the device receive the ANY/UNICAST query? - does the device respond to the ANY/UNICAST query? - does the...