-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Audodiscovery and no Play/Stop #2
Comments
Hello. The fact that your Petoneer SmartDot is not discovered through discover and the subsequent error in sending the command most likely indicates that there are several different firmware modifications for the SmartDot at Petoneer. I was basing this on data from Marco Colombo from the hass-addon-petoneer-smartdot. I actually just had my toy break and I've ordered a new one. I'll pick it up today and check if its firmware is different. If so, I will make changes to the code and at the same time ask you to provide additional data for debugging. I will show you how to scan Bluetooth devices so that you can see the SmartDot identifier and the service it provides. |
Thanks Vadim, no hurry :) |
I received the new Petoneer Smart Dot and unfortunately, the manufacturer has significantly changed the protocol in the new firmware. The previous Petoneer SmartDot was model The previous model had firmware version OldNewThe controller board has also visually changed: OldNewI attempted to debug the new protocol, but unlike the previous version, the packets that the phone app sends to initiate various types of games are no longer static. Each time, the app sends new data when accessing the Smart Dot. When I tried to send a packet with the same content through a Python script, nothing happened. I wrote to Petoneer support, but I'm afraid they won't provide me with the protocol documentation. In my case, I simply swapped the controller board from the old model to the new one. Everything worked, except that the eye's centering was slightly off. It looks a bit to the side from the center in its default position, but I'm willing to live with that. I'll leave the issue open, perhaps Petoneer will respond. For now, I'll add a note in the README about the supported firmware type. I'm very sorry that the manufacturer changed the firmware of the device, thereby complicating the integration of the Smart Dot into Home Assistant. However, they did not add any functionality to their app. |
Thanks a lot Vadim for your time. |
Looking at the components on the board, it resembles my board from the new version of the Smart Dot, but it still differs. Your board has a marking with version I also looked into replacing the Bluetooth chip with an ESP32 and the project at blakadder, but I was lucky with my board. Now that I have a new controller in hand, I might try to replace the chip. If I manage to do it, I will write additional information about it. I will also post in this issue if Petoneer support responds. |
Hi,
First I want to thank you for sharing your work with us.
I've tried to add my cats' Petoneer Dot but unfortunately I didn't succeed.
I'm running HAOS on an Intel NUC machine which has a buildin BT adapter that works fine.
When adding the Integration I'm unable to auto-discover the Dot so I'm adding it by manually entering MAC address, which works, or at least it looks like it's working.
When clicking the Play button I can see in the logs something like this:
2024-04-26 15:48:49.254 DEBUG (MainThread) [custom_components.petoneer_smartdot.button] Current game mode: medium 2024-04-26 15:48:49.254 DEBUG (MainThread) [custom_components.petoneer_smartdot.button] Connecting 2024-04-26 15:48:49.870 DEBUG (MainThread) [custom_components.petoneer_smartdot.button] Sending command 2024-04-26 15:48:49.871 ERROR (MainThread) [custom_components.petoneer_smartdot.button] Connection: BleakError: Characteristic {char_specifier} was not found! 2024-04-26 15:48:49.964 DEBUG (MainThread) [custom_components.petoneer_smartdot.button] Disconnected
I'm doing something wrong or what else should I try?
Thanks
The text was updated successfully, but these errors were encountered: