Open Wolfskii opened 6 months ago
Hey @Wolfskii Had the same issue and took a look of the code. Seems like HA is not picking it up from BL scanning. Easy fix, just modify the manifest to contain correct BL info. Something like this:
{
"domain": "king_smith",
"name": "King Smith Walking Pad",
"bluetooth": [
{
"local_name": "KS-BL*"
},
{
"local_name": "KS-ST-*"
},
{
"local_name": "WalkingPad"
},
{
"service_uuid": "0000fe00-0000-1000-8000-00805f9b34fb"
}
],
"codeowners": [
"@indiefan"
],
"config_flow": true,
"dependencies": [
"bluetooth"
],
"documentation": "https://github.com/indiefan/king_smith",
"iot_class": "local_polling",
"issue_tracker": "https://github.com/indiefan/king_smith/issues",
"requirements": [
"bleak>=0.18.0",
"ph4-walkingpad>=0.0.7"
],
"version": "0.1.2"
}
My "Kingsmith/Xiaomi/X" Walkingpad is sold under moniker Gymstick and they made the BL device name "RE". This causes problems, because the name should have at least three characters for HA to pick it up. https://developers.home-assistant.io/docs/creating_integration_manifest/#bluetooth I used the service_uuid, which might be something else for your device. Maybe someone with knowledge og BLE GATT could write correct manufacturer ID / data so it could pick up all variants.
Hope this helps!
Adding the name allows the device to connect, though the initial integration setup is strange—it gives a white square with no indication that anything is happening on install. When I reboot home assistant, then the treadmill shows up under "Devices" and I can add it, and everything works as expected—until I click "turn off", at which point there is no getting the treadmill back and I need to remove the integration entirely and re-install it. Not exactly sure why that is, but in any case the fix of adding the proper Bluetooth name (in my case "R1 Pro") seems to get it to connect initially.
@henrikyt , I have a similar issue, I have the P1. but for some reason, it times out:
https://github.com/indiefan/king_smith/assets/10994218/546acfb9-1ebf-4398-a69c-4cb563f2b695
, but I can see that the walkingPad has been discovered by BT integration.
"85:20:00:00:32:04": {
"device": {
"address": "85:20:00:00:32:04",
"name": "WalkingPad",
"rssi": -74,
"details": {
"source": "08:F9:E0:89:37:44",
"address_type": 0
}
},
"advertisement_data": {
"local_name": "WalkingPad",
"manufacturer_data": {
"96": "852000003204"
},
"service_data": {},
"service_uuids": [
"0000fe00-0000-1000-8000-00805f9b34fb"
],
"rssi": -74,
"tx_power": -127,
"platform_data": []
}
what I dont get, where do you make that json config?
hey @nagydavid check the manifest.json file in the dir you need to copy
https://github.com/indiefan/king_smith/blob/main/custom_components/king_smith/manifest.json
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1397 Downloaded Repositories | 25 HACS Data | okHome Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 11.5 -- | -- update_channel | stable supervisor_version | supervisor-2024.01.1 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 116.7 GB disk_used | 7.0 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (17.1.0), FTP (5.0.1), Uptime Kuma (0.12.0), RPC Shutdown (2.4), Mosquitto broker (6.4.0), Plejd (0.11.0), Duck DNS (1.15.0), NGINX Home Assistant SSL proxy (3.8.0), File editor (5.8.0)Dashboards
dashboards | 1 -- | -- resources | 10 views | 1 mode | storageRecorder
oldest_recorder_run | 3 februari 2024 kl. 19:32 -- | -- current_recorder_run | 12 februari 2024 kl. 19:26 estimated_db_size | 556.29 MiB database_engine | sqlite database_version | 3.44.2Checklist
Describe the issue
It seems similar to another issue but this time for the King Smith WalkingPad R1 Pro. If I click Add integration and manually click to configure King Smith Walking Pad it loads till it responds with: 504 Gateway Time-out
Reproduction steps
Debug logs
Diagnostics dump
No response