Oleg Kurbatov

Okay, I figured out the cause of this behavior: a test method I wanted to debug inherited `dependsOnGroups` property from the class-level `@Test` annotation. I have set up a sample...

firmata4j currently does not support that part of the protocol. The missing piece is implementation of several protocol messages as described [here](https://github.com/firmata/protocol/blob/master/serial-1.0.md). In order for the board to support these...

We can make all the serial libraries optional and provide transport implementation for all of them. I would highly appreciate your contribution.

I have doubts on whether it is feasible to support Onewire in firmata4j level at all. Onwire's timings are too short for serial communication. Maybe newest Firmata offers something to...

I'll take a look at this when I have some spare time for firmata4j. If you want this feature rather sooner, you can try implementing it on your own. Firmata...

Hi Mario, I have read the [documentation on OneWire](https://github.com/firmata/protocol/blob/master/onewire.md) and it sais that [ConfigurableFirmata](https://github.com/firmata/ConfigurableFirmata/blob/master/examples/ConfigurableFirmata/ConfigurableFirmata.ino) got OneWire enabled by default. So it may be worth trying it with ConfigurableFirmata. As for...

Hi @dougmeredith, Thank you for reporting that. I will take a look at the issue.

Hi Balázs, The only advice for a quick solution I have is try and see if code from this branch works for you: https://github.com/kurbatov/firmata4j/tree/fix/37-digital-pin-value-message I didn't have a chance to...

Support of that message was added in v2.5 of the protocol. Currently **firmata4j** targets 2.3. We should add support of 2.4 features of the protocol before switching to that message...

It seems that `jssc` crashes. If jSerialComm that you propose in #41 doesn't fail on Graal, this issue get solved by implementing a `Transport` interface using working library. I didn't...