-
Notifications
You must be signed in to change notification settings - Fork 12
The maximum baud rate for the device is 115200 error when initializing Hue Plus #42
Comments
If you would like to submit a PR changing the baud to 115.2k, I'll get it merged :) you can find it here |
i tried it but on any other speed i get "write timeout" |
I’ve thought about it, and, to be honest, I don’t know how I would fix this.. any ideas? Also pinging @jonasmalacofilho to see if he might have any ideas. |
I don't understand exactly what's going on here. Is this an API issue (.NET doesn't like that baud rate), or does the device report (somehow) that it wants a lower baud rate? Alternatively, could this be a problem with the virtual COM (the bridge itself or the drivers you have installed)? |
I think it's either device side, or the virtual COM. @TalGruper, what are your Hue+ firmware and HID driver versions? These can both be found in CAM under the hard drive icon on the left, please also include build numbers :) |
Actually, I don't think that's likely: the bridge supports baud rates in the 300-1000k range, and kursti8/hue-plus seems to use 256k without problems. |
I have same error too. Is there any news? |
Maybe we could try initializing at 115k, and if that fails, try 255k, and if that also fails, then throw exception. @stbatuhan would you be interested in testing this out, and if it works for you, making a PR for it? |
I am not able to debug solution :/ I integrated to console app but not stopping on creating device. It is directly throwing exception. Can you provide a test project? |
Today I gave another chance. Download source and integrated new console application. Now changed baudrate to lower value. So I am able to init program but it gaves me error on channels. It seems null :/ Am I able to force it? tried setting channel seperately but on step into part channel still null. |
on this line:
HuePlus h = new HuePlus();
i always get an execption:
ArgumentOutOfRangeException: The maximum baud rate for the device is 115200.
The text was updated successfully, but these errors were encountered: