I would expect if you add app 1…4 and then 6, the 6 become 5… but that is my guess… i can try to experiment with this when I arrive at office, have all my awtrixes there… i should probably take one home 
1 Like
Hi @Bckp, is there a limit as to how quickly you can execute flow cards that send commands to the pixel clock?
I have a ‘reset’ flow that removes all custom apps (9) from my pixel clock and then creates them all again. These actions are performed in serial/after each other. So 9 removals and 9 creations. This flow completes in approx. 2 secs.
I noticed when I run this flow in the slower test mode, it works just fine. However if I execute it in normal mode, not all actions seems to actually be processed by the pixel clock: not all apps are created.
And, more problematic, Homey cannot connect to the clock any more: it shows a red triangle with an exclamation mark on the device tile and error message when opening the tile that it cannot connect to the clock. I need to restart the clock and app to get it working again.
Based on this observation I included a 1 sec delay after each app removal and creation action (see screenshot for context; note that the creation action itself is included in a separate flow for each custom app). This seems to work: Homey keeps connected to the clock. The flow now takes approx. 18 secs to execute.
Not sure what is the cause of this behavior.
To be honest, i never tried to push so much informations to the clock, but based from what I spoke with Blueforcer ideal is less then 5 in sec, you can really easily overrun the CPU on clock, it is slow ESP if I remember correctly…
I can create flow card remove all custom apps, that should be possible (i know all apps running on clock and homey one have homey: prefix, and i can stack the delete command, but creation is different story… If you can send me report, i can analyse what happens during the command and why the clock stop responding…
It is also not a flow that I will be using regularly. The 1 sec delay between commands is fine for my purposes.
I created a log after performing the flow without the delays (I hope this is the correct method; I haven’t created logs before 
): ae5cae3c-9925-4df0-96c7-a4d317737bd6
Thanks for looking in to this!
Yep, it is it… but Athom limit amount of data it sends, so i see 3 last apps
Is that enough info for you? Or is there a way to create a better log for you?
I will try to replicate it at work… this Wednesday hopefully… But i belive sending 18 requests in 2 sec is just too much for Awtrix, maybe i will add option to put automatic 200ms delay if you chain commands…
1 Like
Just info for all, Ulanzi offer 33% discount for Awtrix, so if you want some, now is great time to get them 
Affiliate link: PIXEL Smart clock
This affiliate is for Blueforcer, author of amazing Awtrix firmware
1 Like
Just installed test version 1.3.3 because the card ‘Send notification messages with JSON options’ is very useful, thanks!
My current running Flows with ‘Send (sticky) notification’ doesn’t show the icon anymore, just only the message. Workaround is using the new card message with JSON options, with icon option.
Thanks for info, fixed in 1.3.4 (released to test)
Icons are back, thanks!
Hi @Bckp, I am trying tro create a custom app with text in colored fragments as described in this section of the AWTRIX documentation.
If I input the necessary ‘text’ configuration in the JSON part, it seems to be ignored / overwritten by the ‘message’ field in the flowcard. If I don’t provide a message (leave the message field empty), but do include the ‘text’ config in the JSON part, no text is displayed (only the icon).
How can I display test in colored fragments?
Colorized text is not supported yet 
i never thought someone will use it… i will look at this
1 Like
I wanted to change to your app (instead of MQTT JSON stuff), however I do miss as well the colorized text (like @SunBeech )
1 Like
Im slowly working on it 
not much spare time left 
i need to finish setup screen to support authentication too, in next life day should have 36 hours 
1 Like
Text fragments are in latest test version please test them… one change, official documentation have info color need to be in HEX value without #, that is not exactly true, it should be with # for consistency, and homey app expects you to fill # there… i wrote BlueForcer to fix this in documentation.
EDIT: TextFragments for for notification, not for app (i will try to fix this today)
EDIT2: TextFragments now in 1.3.6 works as expected
You can put them into JSON or even in text field
1 Like
Hello, gradient should be array, not string, this could be the reasson why it is not working as expected, validator will remove it as it is not valid, blinkText should be int, so try to put it there without ", but that is guessing, I can look at it later if this will not work…
Yes… I assume you’re right, but somehow the closing bracket got lost… will check tonight…
But “repeat” is also int, and it´s working as expected - unless 1 is also the default, which I have to check…
There will be different issue I guess, because code have normalizers, so they take that string and convert it internally to number, so this must be some sort of bug in app, i will look at it…
