-
Notifications
You must be signed in to change notification settings - Fork 12
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
Enhance CC push_image
service with an optional argument (group_topic
)
#84
Comments
Since update on v0.7.0 a few days ago, I haven't experienced a single plate crash. I've still my v0.6.3.0 plate running in parallel next to the 0.7.0. This experienced still the occational crash now and then when images are pushed. |
Has been on latest 0.6.3-dev version on both my test plates for quite some time now. My current service call in HA: - service: openhasp.push_image
data:
obj: p2b40
image: >-
http://xxx.xxx.x.xx:8123{{state_attr(state_attr('group.sonos_all', 'entity_id')[0], 'entity_picture')}}
width: 200
height: 200
target:
entity_id:
- openhasp.wt32_01
- openhasp.wt32_02 Gives this error in HA log at random intervals (4 times in the logs since midnight (16 hours):
For now I'll revert back to patching CC so I only issue one mqtt group topic message and only state one target entity_id |
Update on this topic: Would it be possible to enhance CC with an optional argument ( I was thinking something like this: config #1:
Or config #2:
|
group_topic
)
group_topic
)push_image
service with an optional argument (group_topic
)
Hi' @dgomes Any chance of getting some kind of optional I had to step back from my current config where I iterate through all the connected openHASP devices and So now I'm back to sending one image only (highest resolution needed) and the lower resolution devices uses But in order to do this, I had to hack CC init_py and push all images to the mqtt group topic (hardcoded). |
Will need to investigate into HA groups... unfortunately the options proposed (although they work) are not HA best practices |
openHASP 0.6.3 - HA supervised core-2021.10.5
Configuration
Describe the bug
EDIT: 191221
Added additional combined HA CC debug log / plate serial log entry.
HW:
Both plates are running rock solid without the push image automation.
WiFi connection good/fair (appx. -58dbm)
No mqtt failures, no PSram memory leaks or LVGL memory fragmentation issues when I check plate's info page.
I'm experiencing issues with random plate crashes when pushing media player images to plate/plates.
Crashes seems to be completely random and unrelated to any other mqtt messages processed at plate at same time.
My test scenario is running a repeated non-stop playlist, which will push new images at some 3-5 min. intervals 24/7.
Prior to image push two seperate mqtt messages are sent to plate with artist/title. Last message typically send some 100-300 ms. before image is pushed. To ensure that plates mqtt queue doesn't choke on messages to be processed prior to the image, I'll keep automation delay at min. 1 second as I have now.
Automation has been refined a long the way during my test process.
Pushing images to two plates (in automation as two entities) without my added automation delay, gave numerous random plate crashes. Without added delay, and with two plates in automation, skipping rapidly through playlist will force a plate crash very quickly (often within 10-30 seconds).
With only one plate in automation and no delay, plate will still crash - but with larger intervals.
With one plate in automation and the 1 second delay, plate will crash at large intervals (typically many hours apart)
Latest currently runnning test version is with automation 'as is' in this issue report. Just with the twist that I patched CC init.py with a fixed path
hasp/plates/command/
to update both plates at once with mqtt group commands.This test scenario has now been running for some sixteen hours with only one crash/reboot at some five hours ago. So almost stable, but not completely stable yet.
Seems like the issue lies within files access/availability though on the HA side ? Check my first combined log entry (HA CC debug log and plate serial log). Here I tried to force a crash, rapidly (2-3 seconds interval) flicking back and forth in a playlist and hardly giving HA's entities/file writes any time to 'settle'. On two accounts file apparently can't be opened by cc and no conversion is done according to log. But cc still pushes an image to plate ?? Second time that happens plate crashes and reboots.
Debug log
First log entry is a combined HA CC debug log / plate serial log
Extra two 'plates only' serial logs at the end. Seems to be completely identical.
The text was updated successfully, but these errors were encountered: