AlienFX error: no controller available.

[jdev-jmyl]

Alienware 15 R2.
Terminal say - "Device found: 187c:0528".
Application error.

[bchretien]

A controller is missing for that specific Alienware, and I do not have the commands mapping yet (cf. this for example).

[jdev-jmyl]

I added code by example M18x R2 controller for my 15 R2. It's working for me.
But some action on profile work not correct area. I will try testing and try commit .
For axample Media Bar changing light for tochpad and speakers.

[bchretien]

You can check this to help you find the correct mappings. You may need to modify the program though.

[JLeliaert]

I tried several controllers for my 15R3 ( 187c:0530) but everytime I get "Error occured while trying to communicate with the AlienFX device: Data length should be 9 but was -9"
How should I interpret this negative length? I don't really see how to solve this

[jakeday]

This is fixed with my pull request

[bchretien]

@JLeliaert can you confirm that the PR from @jakeday solved your issue (merged to master)?

[JLeliaert]

Not yet. I still get the same error.

[bchretien]

Hmmm so you're saying the id for the M15x R2 is 0x0528, yet this is the one now used for the M17x R3. Apparently this was changed in eed65e8. @jakeday where did you get the id for this model?

[jakeday]

@bchretien I got that id from my own M17x R3. That's not the id for the 15 R2. However, form what I've seen the 15 R2's have shown with both 0528 (which is the 17 R3) and 0530 (which is the 17 R4). I'm trying to figure out why they are identifying this way. Note: I have a couple alienware laptops and that's where I'm getting these numbers.

[bchretien]

@jakeday ok, this is weird, but shouldn't be a problem if they are controlled in the same way (only the reported name would be wrong).

[jakeday]

@bchretien unfortunately they are not controlled in the same way, which is odd. I'm working on a fix now.

[bchretien]

@jakeday I see, thanks for the help!