setState() callback broken

[Miq1]

I upgraded to the recent Fauxmo 3.2 version and discovered that the callback signature for the setState() callback seems to have been changed, preventing my application from being compiled.

Where can I find a documentation on how to interpret the additional 3 unsigned int values?

For the time being I added those with a default = 0, but am not sure if the remainder will behave as before?

[sebkouba]

Where do you see the additional unsigned int values? I see and use this onSetState() function. fauxmo.onSetState([](unsigned char device_id, const char * device_name, bool state, unsigned char value)

[Miq1]

Where do you see the additional unsigned int values? I see and use this onSetState() function. fauxmo.onSetState([](unsigned char device_id, const char * device_name, bool state, unsigned char value)

In fauxmoESP.h line 103 we have

 void onSetState(TSetStateCallback fn) { _setCallback = fn; }

TSetStateCallback is typedef'd in line 75:

typedef std::function<void(unsigned char, const char *, bool, unsigned char, unsigned int, unsigned int, unsigned int)> TSetStateCallback;

[pvint]

Are you using the latest master branch in git? If so, that's my fault.

In making changes to add ability to change colours I think there's still an incorrectly overloaded function. I've been thinking that I didn't like the way I implemented the interface for changing colours and will likely roll it back.

For now, if you're using git, try checking out the source at commit 74a69c9

[Miq1]

I think I do use the master branch indeed. I am using Platformio for development and that hinted me to the library update after that I got the error on using the older onSetState function signature.