Andrey Pokhilko

As you see in dump "The crash happened outside the Java Virtual Machine in native code." and the native lib is "sigar-amd64-winnt.dll", which is part of SIGAR. AFAIK that lib...

SIGAR is the lib that we don't develop. We just used it. I guess it's because of Java 10 having some bug. Can you try with older JAVA?

Guys, here are some points from me: 1. SIGAR is dead as project, as far as I know. There's nobody to go and talk to. 2. I am occupied with...

I believe both `start_power` and `start_speed` methods would allow you to do what you want. You can start motor_AB, and then call individual motors to set different speeds.

Hello, Unfortunately, I don't have access to that set, so I can't contribute such support. Anyone with access to that hub can contribute it. It will be pretty much copying...

Very useful is to collect whatever Hub reports itself. Here's my script to do that: ```python import json import time import unittest from pylgbst.hub import MoveHub from tests import log...

Wow, that's a bit complex for me with the `screen` thing... With PoweredUP hubs, usually you can take the `Hub` class and connect to it either using the device name,...

Looks like no communication comes back from the device. Might be caused by BLE adapter, libraries problem or anything else. Possible way to get more info is to enable DEBUG...

This looks very nice. Couple of comments: 1. It would be great to cover the new class with unit tests. 2. Using this piece of code `print(hub.peripherals[MoveHub.PORT_C].describe_possible_modes())`, you can get...

Blue light can remain on with some BLE libraries, and there's no harm in that AFAIK. You can call `switch_off` to force hub to power off (https://github.com/undera/pylgbst/blob/master/pylgbst/hub.py#L192). Regarding reconnecting issue,...