I think the amazing work you have done needs a new thread. Are you continuing your work on this or have you moved on?
Hello. Could you please elaborate on this? Iâm also trying to play chime.mp3 through BigTalker and I canât figure out the command to use.
I donât beleive this is possible without a modifying BigTalker.
Ok, thank you. I can use WebCoRE instead to send a webhook to a MacroDroid sound trigger. Works just as well.
Sorry, I wasnât watching the Forum with all the fun in the world right now. I am thinking this is more of a webCoRE project and should start a thread there given most of the functionality is accomplished there?
I upgraded to FKB 1.39 and there are a few âbrokesâ that happened and support has now fixed and should be patched in 1.39.3+.
FYI, FKB (1) stopped supporting the âcurrentFragmentâ when in screensaver and (2) the device was sleeping the webview would stop and would delay ActionTile loading. But looks like that should be fixed soon / next release.
The javascript injected triggers are working well and it does function good as a motion sensor in a room during the day, not so much at night, but I also turn off the motion so it doesnât wake people up without touching the pad. The updated DH is here. I did add the Carousel function and looks pretty good for both camera captures and screen grabs. This is on Fire HD 8âs.
It looks like the new ST app is starting to support a lot of functions now so probably look at what I can do later to clean that up - still not a fan of it. It has a ways to go to replace the old one.
Here are some screen shots.
and here is the piston for those into webCoRE. Great software was made there !!!
2 Likes
Amazing. Is it possible to have all these features in 1 DTH? I am confusing myself with FKB controller and device.
1 Like
Yea, FKB is well featured solution. The support has been great for the few questions I tossed at them too. I did add a setting to turn off the image grab back from AWS. I know my security is good around my lamba, api gateway, and S3 bucket. But I have no idea who at ST has access to the storage they use for images in the system. I am sure someone is snooping there - just fun to smash the button and grab an image into application.
Taking a picture with the app is neat, seems very full featured, there isnât a Read Me with all the options available? Like how to get and what is the AWS for? And not able to save the piston, anything over 19 chunks, it freezes! Thereâs too much data in it! Although I see part of piston automates screen brightness at sunset/sunrise.
Unfortunately I havenât done much to document the solution beyond the code. All the AWS gibberish is for an API Gateway solution in front of AWS Lambda that will store things into AWS S3. Then I run AWS Rekognition to attempt facial matching - but the piston should run without it fine. Load the DTH first and get it running, then attempt the piston on the newest v0.3.110.20191009 webCoRE release.
I just initialized the âsm8geâ code and stored without issue (using Chrome). It is a larger piston - but I have seen bigger. Maybe go to the app itself and clear and rebuild the cache?
Also see the note - I am running my own modified version that has $endpoint & $randomUUID that has yet to be pulled into the main release branch. You need to update these by hand according to the notes.
For example:
This conversation started around having real time motion detection with me pointing out you can inject javascript into FKB to real-time event back to a ST application (for example webCoRE). I will start a thread in webCoRE since I donât want to highjack @arnb great work and solution.
1 Like
Updated a webCoRE thread and gave this thread a shout out.
Seems we have lost Chime with custom audio file from the original version of this. Any ideas on how to get that integrated?
It really wasnât a port of this DTH and I just grabbed some of the TTL code. However, if you let me know what you need I can pull in the method(s) since they both functions similar. Will need someone to test since I donât have chime. Can you give me a quick requirement set? and Habitat isnât on my todo list. (yet)
Sent the same note to Fully support, but is anyone experiencing the following with ActionTiles and FKB?
Trying to track down a delay issues that appears to be FKB related. I am running 1.39.3 on Fire HD 8. I have three of the devices.
I have ActionTiles webpages active on the FKB browser. When the device sits for a âperiodâ of time the first time I press an action to execute a light on/off the action does not occur for as long as 30 seconds. After this first delay the action with other items are near instant. If I let the device sit for a âperiodâ of time the delay happens again.
This does not happen with other browsers (Silk, Chrome on MacOS, Safari on iOS).
I have turned off all motion detection, screensaver, any graphic panels and have not been able to isolate.
Q: Is this a known issue with anyone else?
1 Like
Yes but not so bad. My initial delay for a panel to load after the device has been sitting for a period is 5-7 seconds. Subsequent panels load in around 3 seconds.
I have the exact same issue, in Sharptools with FKB.
How did you reach out to them, I think it would be wise for me to reach out too so they know others have the same issue.
My issue is intermittent. Sometimes works just fine and sometimes I need to grab some coffee before it does anything.
1 Like
You can send the Fully Kiosk Browser (FKB) developer an email at:
info@fully-kiosk.com
You might consider linking to this thread in your email and mentioning that itâs happening across different web apps (eg. SharpTools and ActionTiles).
The FKB developer will likely be interested in knowing which FKB version you are running, on what make/model device, and may ask which Webview implementation is being used. You can get all of this information from Fully Kiosk Settings > Other Settings > Device Info.
Yes, exactly how to contact. Good support team tooâŚ
The problem I am reporting is execution of the actual on/off switch tile itself and not panel loading times. The HD Fire 8 does take time loading ActionTiles pages which is expected given the speed of the CPU.
Again what I am seeing: When the ActionTiles webpage is open on FKB and you allow a period of time to elapse (regardless if FKB screensaver is running or not) the first tile press can be delayed. The âperiod of timeâ is around 3-4 minutes. The âdelayâ can be 5-30 seconds. The next action and following are near instant, until you allow the device to rest again for a period of time as described.
There is no delay of visual queues when an action has happen so the websockets are still working - just actions on first keypress.
I am able to reproduce on FKB 1.39.3, ActionTiles FKB 6.1.29h-Fire, Amazon Silk 81.2.16.4044.138.10, and side loaded Chrome version 83.0.4103.101. Which appears this would be WebView problem. The Android version is 7.1.2 (SDK 25) and the WebView version is 70.0.3538.110.
I am NOT able to reproduce on iOS Safari and MacOS Chrome - they work near instant all the time.
When this started, I donât know but the Fire OS 6.3.1.5 shows as installed March 22, 2020 which sounds about right time. The devices are all Fire HD 8 Tablet (Gen 8).
Pinging @625alex for ActionTiles visibility and or comment.
I was referring to switching between panels. However, I just tested it again and the reaction time to a switch press is about 5-7 seconds each time. I am running 1.37-fire on a Fire HD8
Itâs always best to report ActionTiles problems to ActionTiles support.
Iâm doing some analysis, I will comment in a little while.