feat:Add Honey Play Box Kaipro support

[wwwfeng]

Summary

Adds support for the Honey Play Box Kaipro (HPB-274).

• Adds vibration control with levels from 0 to 100.
• Adds constrict control with four modes.
• Maps constrict level 0 to stop and levels 1–4 to device command values 101–104.
• Keeps the Kaipro-specific command handling isolated from other Honey Play Box devices.

Testing

• Verified formatting and compilation.
• Passed device configuration tests.

[blackspherefollower]

I think a lot of the logic in this change is unnecessary and if there's other suction based toys, will make implementation more than just a config update.

I do wonder if there's a significance to the +100 value for the KiaPro's suction control: do lower numbers trigger patterns, etc? Are there other toys with suction that have the same offset requirement or more importantly different offsets?

[blackspherefollower]

Lets set the range to 100 to 104, then there's no need for the +100 bump in the protocol implementation.

[wwwfeng]

I added a default offset of 100 instead. Not sure if this is the preferred approach, but we need to support 0 and 101–104.

[wwwfeng]

I think a lot of the logic in this change is unnecessary and if there's other suction based toys, will make implementation more than just a config update.

I do wonder if there's a significance to the +100 value for the KiaPro's suction control: do lower numbers trigger patterns, etc? Are there other toys with suction that have the same offset requirement or more importantly different offsets?

For KaiPro, 1‑100 is used for vibration intensity, and 101‑104 correspond to its four suction preset modes. Values above 100 stand for hardware preset modes, and these are not guaranteed to be suction functions on our future devices. That is why I previously added special‑case handling in code.

[blackspherefollower]

I think a lot of the logic in this change is unnecessary and if there's other suction based toys, will make implementation more than just a config update.

I do wonder if there's a significance to the +100 value for the KiaPro's suction control: do lower numbers trigger patterns, etc? Are there other toys with suction that have the same offset requirement or more importantly different offsets?

For KaiPro, 1‑100 is used for vibration intensity, and 101‑104 correspond to its four suction preset modes. Values above 100 stand for hardware preset modes, and these are not guaranteed to be suction functions on our future devices. That is why I previously added special‑case handling in code.

Does that mean you need to OR the vibration speed and the suction mode? Or are they on different indexes?

[wwwfeng]

To add further clarification about our command‑set definition: • 0 generally stands for stop. • Values 1‑100 are normally used for vibration intensity. • 101‑109 are hardware preset modes, applicable to all of our current toys. Every value from 1‑109 has a defined meaning. That is why the +100 offset is necessary: 1‑100 covers regular vibration levels, and values above 100 represent our special preset play‑modes. For KaiPro, only 101‑104 are valid suction preset modes within this preset range. Other devices may utilize different slots inside 101‑109 for their own hardware presets. Vibration and preset modes are independent logical channels. We do not combine values by bit‑wise OR operations.

…

------------------ Original ------------------ From: blackspherefollower ***@***.***> Date: Wed, Aug 19, 2026 8:41 PM To: buttplugio/buttplug ***@***.***> Cc: wwwfeng ***@***.***>, Author ***@***.***> Subject: Re: [buttplugio/buttplug] feat:Add Honey Play Box Kaipro support (PR #940) blackspherefollower left a comment (buttplugio/buttplug#940) I think a lot of the logic in this change is unnecessary and if there's other suction based toys, will make implementation more than just a config update. I do wonder if there's a significance to the +100 value for the KiaPro's suction control: do lower numbers trigger patterns, etc? Are there other toys with suction that have the same offset requirement or more importantly different offsets? For KaiPro, 1‑100 is used for vibration intensity, and 101‑104 correspond to its four suction preset modes. Values above 100 stand for hardware preset modes, and these are not guaranteed to be suction functions on our future devices. That is why I previously added special‑case handling in code. Does that mean you need to OR the vibration speed and the suction mode? Or are they on different indexes? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[blackspherefollower]

To add further clarification about our command‑set definition:
• 0 generally stands for stop.
• Values 1‑100 are normally used for vibration intensity.
• 101‑109 are hardware preset modes, applicable to all of our current toys.
Every value from 1‑109 has a defined meaning.
That is why the +100 offset is necessary: 1‑100 covers regular vibration levels, and values above 100 represent our special preset play‑modes.
For KaiPro, only 101‑104 are valid suction preset modes within this preset range. Other devices may utilize different slots inside 101‑109 for their own hardware presets.

Vibration and preset modes are independent logical channels. We do not combine values by bit‑wise OR operations.

Ok, so feature 0 is vibration (0-100) and feature 1 is suction (0, 101-104). Does suction 0-100 do anything?

Since this is the first suction device, and the modes are always valid, should we just make constrict always +100?

[wwwfeng]

Sending 1‑100 to the suction feature has no effect; only 0 and 101‑104 are valid. This is our first suction‑capable device, with 101‑104 actions predefined in‑firmware. Since slots in the 101‑109 preset pool may be assigned to other modes for future devices, a universal framework‑level +100 offset for all constrict features may not be safe.

…

------------------ Original ------------------ From: blackspherefollower ***@***.***> Date: Wed, Aug 19, 2026 10:37 PM To: buttplugio/buttplug ***@***.***> Cc: wwwfeng ***@***.***>, Author ***@***.***> Subject: Re: [buttplugio/buttplug] feat:Add Honey Play Box Kaipro support (PR #940) blackspherefollower left a comment (buttplugio/buttplug#940) To add further clarification about our command‑set definition: • 0 generally stands for stop. • Values 1‑100 are normally used for vibration intensity. • 101‑109 are hardware preset modes, applicable to all of our current toys. Every value from 1‑109 has a defined meaning. That is why the +100 offset is necessary: 1‑100 covers regular vibration levels, and values above 100 represent our special preset play‑modes. For KaiPro, only 101‑104 are valid suction preset modes within this preset range. Other devices may utilize different slots inside 101‑109 for their own hardware presets. Vibration and preset modes are independent logical channels. We do not combine values by bit‑wise OR operations. Ok, so feature 0 is vibration (0-100) and feature 1 is suction (0, 101-104). Does suction 0-100 do anything? Since this is the first suction device, and the modes are always valid, should we just make constrict always +100? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>