Hi Simon_Kamboj, welcome to our forum!
Iāve checked and confirmed that the 1.2.0.1 beta version is still available on our cloud server. You can go to the beta version page, enter the passcode 6102, and click confirm to check for and install the update. (For step-by-step instructions, please refer to this guide: https://www.youtube.com/shorts/QLF4nvw1X64)
We look forward to your reply! If you encounter any issues, please donāt hesitate to reach out.
Enjoy your experience!
When selecting configure from the Astrion Home integration. The writing is in Chinese characters, I am not sure what it says. Needs to be translated.
it means IR, I will ask the engineer to fix this bug, thanks for the feedback
Very disappointed the issue with āHarmony config not found for this entityā that has broken the TV card with Shield TV devices is still not resolved.
I have this issue also and yet I donāt have a harmony hub configured or in use, Currently Iām dead in the water with no way to control my TV or Shield.
Unfortunately both original remotes are unusable and had the Astrion configured for both. Is there is any way to get this fixed or do we have an ETA on when it will be fixed?
The ADB debug bridge is glaciallly slow and the lag just makes me not even bother using the remote at the moment.
I would downgrade to the previous firmware version in your case which didnāt have this error.
Very disappointing to see such a major bug get released and remain unfixed for this long. I am surprised they didnāt un-publish this version considering it makes the TV card unusable for anyone with a Shield device.
Good idea and thanks for the suggestiion @stealthwang..
Sorry for the newbish question as I havenāt come across downgrading on the Astrion as yet so how would we go about downgrading the firmware?
Iāll hazard a guess and say change the Roscard version to a lower version possibly or is it published somewhere? or do we keep the previous version cached somewhere?
Iāll take a look and see if I can figure it out but thought it would be worth asking..
Thanks again
I will personally escalate this issue to our R&D team first thing tomorrow morning, and we will push for a high-priority review and a fix as soon as possible. We are also internally discussing why this version remained published despite the critical impact on Shield devices, and we will improve our release validation process going forward.
In the meantime, if downgrading to the previous firmware works as a temporary solution, that is certainly a reasonable step. However, our goal is to resolve this properly in an upcoming update, and we will keep you posted on any progress.
Hello, we sincerely apologize for the inconvenience this has caused you. Regarding the Harmony error issue, we have already reported it to our engineers for further investigation. Additionally, I would like to confirm: regarding the ADB control latency issue, was it working properly before, and did the response become significantly slower only after updating to the new system?
We have received your feedback, and our engineers have confirmed that this issue will be resolved in the next release. A new version will be published soon ā please stay tuned for the update.
Additionally, our engineers have confirmed that the new version did not make any changes to ADB control. Could you please clarify whether the latency you are experiencing occurs with both single-click and long-press operations, or only with long-press?
Anyone else noticed since the 1.2 update that the media card is no longer showing media progress bar?
Ie what time itās at in the media
Yes progress bar no longer showing.
Hi, Iād like to explain the progress bar issue. Some of you may have noticed that the previous media progress bar wasnāt working accurately. When we retrieve progress data through the Home Assistant API, we canāt achieve the same real-time precision as HAās own dashboard. Instead, we can only fetch discrete data points, which donāt update dynamically as the media plays. In practice, the progress bar was more of a decorative element ā it only updated when a user performed an action that triggered a status refresh. This approach is far from ideal.
Our engineers tried to find a way to dynamically fetch accurate progress data, but unfortunately, we havenāt been able to resolve this technically. To ensure a smooth and honest user experience, we decided to remove the progress bar display for now, rather than show inaccurate information.
If we find a better solution in the future, or if anyone in the community has a feasible idea, weāll be happy to bring the progress bar back.
Wishing you all the best!
Hi, Iād like to explain the progress bar issue. Some of you may have noticed that the previous media progress bar wasnāt working accurately. When we retrieve progress data through the Home Assistant API, we canāt achieve the same real-time precision as HAās own dashboard. Instead, we can only fetch discrete data points, which donāt update dynamically as the media plays. In practice, the progress bar was more of a decorative element ā it only updated when a user performed an action that triggered a status refresh. This approach is far from ideal.
Our engineers tried to find a way to dynamically fetch accurate progress data, but unfortunately, we havenāt been able to resolve this technically. To ensure a smooth and honest user experience, we decided to remove the progress bar display for now, rather than show inaccurate information.
If we find a better solution in the future, or if anyone in the community has a feasible idea, weāll be happy to bring the progress bar back.
Wishing you all the best!
The ADB latency issue has always been present and is impacting the long press more than anything, the only way to accurately use the remote is to do one action and movement at a time and wait for the most recent button press to catchup on screen before performing the next action, otherwise you drift into the wrong menu, or activate the wrong menu item unintentionally.
As mention the ADB issue is a separate issue and not related to changes in the latest firmware. I was just stating the frustration at not beinbg able to use the remote with the ADB latency impeding the experience.
So to confirm it seems that the changes in the latest firmware is related to the error message about the harmony controller which breaks the TV card whilst using a configured remote that does not use ADB.
Apologise for any confusion, I should have mentioned the ADB latency separately.
Have you tried
rather than
supposedly there is a difference.
Hi Mr. J, we apologize for the poor experience caused by the ADB latency. I have reported the issue to our R&D team, and they will investigate the possible causes of the high ADB control latency one by one.
According to the R&D teamās analysis, the ADB control latency can be categorized into three situations:
Ā·Situation ā and Situation ā”: Similar latency times, both relatively high. Situation ā uses HA-defined key values, and Situation ā” uses the adb shell input keyevent xx command.
Ā·Situation ā¢: Using the sendevent method, which is closer to the underlying layer and has lower latency.
Therefore, our engineers suggest you try the following two adjustments:
Ā·Solution 1: Paste the Android bridge command into the remote control, or create a script and bind it to the button.
Ā·Solution 2: Use developer tools to learn the ADB keycode values āāof the Android TV, then paste the learned keycode values āāinto the TV card, or set it as a script and bind it to the button. (I can provide a learning document if needed.)
Furthermore, our R&D team would like to know if you can provide more details: When using the Android bridge to achieve latency-free control, are you binding it via entities or scripts? We would also appreciate it if you could provide the relevant control code values āāso we can further analyze the specific causes of the latency.
Additionally, regarding the issue of Harmony configuration errors causing TV cards to malfunction, we plan to fix it in the next version. The testing team is currently verifying this, and an update is expected to be released this week.
If you have any other usage questions or suggestions, please feel free to provide feedback. Thank you!
Android TV Remote is currently broken with āFailed to fetch harmony configā error.
