You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, core only checks if a button name is compatible with the module type (in CheckButtonName) if the module type in the request is CLIMATE or RADIO.
If the user were to send a ButtonPress request with a different type, core would currently not send the "Request module type and button name mismatch!" response and forward the invalid request to the HMI
Bug Report
Currently, core only checks if a button name is compatible with the module type (in CheckButtonName) if the module type in the request is CLIMATE or RADIO.
If the user were to send a ButtonPress request with a different type, core would currently not send the "Request module type and button name mismatch!" response and forward the invalid request to the HMI
Reproduction Steps
{"moduleType":"HMI_SETTINGS","buttonName":"FAN_UP","buttonPressMode":"LONG"}
Expected Behavior
App receives INVALID_DATA response with info "Request module type and button name mismatch!"
Observed Behavior
App receives SUCCESS response
OS & Version Information
The text was updated successfully, but these errors were encountered: