Command line tool vs homeassistant about orvibo HOT 4 CLOSED

This is a known issue. The root cause that all requests to Orvibo devices are initially made via broadcast to port 10000 and bind to current interface, thus next module instance can't bind to occupied interface and either discover device or sending request to exact device fails.
This is fixed in keep_connection branch, but hasn't merged yet for some reason. Since someone is care now, I'll merge it as soon as I can. Thank you!

from orvibo.

Fix has just merged to 1.4 module version

from orvibo.

Hi,

great! but... how this works? Because I use to use the command line too. As
i understand the keep_connection would be useful only inside homeassistant,
or not?

On Sat, Jul 2, 2016 at 9:02 AM, Pavel [email protected] wrote:

Fix has just merged to 1.4 module version

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#6 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AEjpGrBsdwYYqRVsxBDHgky2WAgmHDtoks5qRlNlgaJpZM4JAtrk
.

Christian Lyra
PoP-PR/RNP

from orvibo.

Right, keep_connection will be used only if you use the orvibo as python module.
The trick is in the socket creation function, which doesn't occupy broadcast port 10000 now and connects directly to the device if you want to send request.

from orvibo.