Yes, regarding the event reportingāwe donāt actually support binding it directly to automations due to logic constraints. However, weāve noticed that many Home Assistant users have impressive manual skills and are able to configure their own automations based on the available data, which effectively allows for separating single-click and long-press functions. Iām genuinely amazed by your capabilitiesāvery impressive!
Iāve already raised this with our R&D team, and we plan to restore the remote control event reporting data in the next version, bringing it back to the same state as in 1.3.0. However, due to the underlying logic constraints, our built-in integration will still not support direct binding channels. You would need to capture the reported values and configure your own automations manually. Would that work for you?
Also, this feature has been requested by only a very small number of users, so if we officially release it, it may not be available until sometime next week. We hope this doesnāt inconvenience you too much. If you need this feature urgently, I can apply to R&D for a grayscale build specifically for you, but that may also take some time to prepare.
We have fixed the issue where the update prompt still appeared even after upgrading to version 1.4.0. We sincerely apologize for this bug and any inconvenience it may have caused. We hope you enjoy using our product going forward!
Yes, itās honestly more convenient to set them up to call a script on my end - that way I can just manage the script if lights or other entities change etc and the remote will still function.
Also I am using my second/other remote in the room where I was using these for now and just have not let it update, so you do not need to rush - please prioritize other features and bug fixes.
Thank you so much for your support and understanding! We hope you enjoy using our product. If you have any other suggestions or needs, please feel free to share them with usāweāre always here to help.
First of all, I sincerely apologize for the confusion and the delay.
I checked our previous records, and it appears this was an error on our side. From the information we have, the missing part should be the small protective cover plate near the charging port, which is fixed with screws ā not the desktop charging base itself.
Could you please double-check and confirm that this is the part you are missing?
Once confirmed, we will arrange the replacement part for you as soon as possible and provide the shipping information.
Thank you for your patience and for helping us improve Astrion.
Thank you again for your patience, and we sincerely apologize for the trouble caused by the V1.4 update issue.
We have identified the root cause and have now fixed it. The issue was related to the server-side update process, not the firmware installed on your remote.
The good news is that if you have already upgraded to V1.4, you do not need to do anything further. After our server-side correction was applied, the repeated update notification issue should no longer occur.
Regarding the update process, we also want to be transparent with our community. Many Astrion users are experienced Home Assistant users, integrators, and developers, and we know many of you enjoy testing new capabilities early. At the same time, our engineering team was eager to deliver the new improvements as quickly as possible.
In this case, we moved faster than we should have and did not complete the level of validation we normally aim for before release. Since this was a minor version update rather than a major platform change, we made the wrong assumption that a full beta testing cycle was unnecessary.
This was our mistake, and we appreciate your understanding.
We will improve our release process going forward, including more extensive testing and better staged validation when introducing future updates.
Thank you again for reporting this issue and helping us improve Astrion.
