Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Firmware version confusion #3738
    JP
    Participant

    Very cool, will be playing with the exposed Command functions – thanks for all the info, much appreciated!

    in reply to: Firmware version confusion #3727
    JP
    Participant

    Thanks!

    For now, HTTP direct to the GameFrame IP is most efficient – but I am quite curious about the post/javascript options (although these are still going to dependent on the webserver right?)

    I do realize I can accomplish the below via particle.exe command line tool (but again that requires my Internet connection and particle.io servers to be up, just to control something already inside my LAN) so, I do really wish…
    – there was a /set?off option instead of just power toggle, because as part of my “leave the house” script I’d like to ensure GameFrame gets turned off (as I do with lights and the TV and whatnot) whereas if I send /set?power and it was already off, now I’ve only turned it on 🙁
    – there was a /set?[filename] where it would automatically turn on and play that animation, for example when my kid mario logs that he’s home off the bus, show the mario graphic for fun. I could also get crazy & appreciate other “digital signage” style options to this, for example /set?[filename]&play?20&next?off for play that animation for 20 seconds then go off, or &next?random might mean leave it on and proceed through the list randomly.
    – there was an option to have animations present in memory (for calling direct per the above example) but excluded from the normal random display, or when someone advances with /set?next

    Optionally, if the webserver stable/un-stable-ness proves to be an issue, then I can always control power to the GameFrame via my own relay/controllable power socket feeding the AC adapter (this would let me reboot it if crashed, or ensure it’s off) but in this case I would appreciate a baked in option like you alluded to, something like “power applied state” and/or “auto-reboot state” with choices being a) turn-on b) stay-off c) last-state

    in reply to: Firmware version confusion #3722
    JP
    Participant

    Hey thanks for all the info, so I did get it to Game Frame Firmware: 20161211 successfully.

    As far as the random turn on issue, I never use the IR remote, only the web interface (cause I link to it from my other home automation controls which all run from my own webserver inside the house)

    Why does it randomly turn on, I’m not sure. I have a suspicion it has to do with WiFi disconnects, as a few other LED controllers and Aurdino WiFi shield based things in my house also get disconnected on occasion. I think I might have discovered the reason why last night, apparently my AP was trying to use a defunct NTP server, thus never adjusting it’s time skew properly, which can cause issues with the key refresh interval, or so I believe, but this is unproven/could be totally off base.

    In any case I am pleased to know it’s not so dependent on particle.io, because honestly I feel that’s just another a) single point of failure b) planed obsolescence when the dot-com bubble bursts (again?) and particle.io goes belly up and c) IoT hacking is a thing and really getting out of hand.

    After looking at the source of the /help page I determined I can send it HTTP commands for directly, which is cool, cause I can send /set?power /set?menu /set?next from the back-end from my own webpages and that’s all I really need.

    I do notice when loading the root / (pretty menu) it takes awhile and sometimes crashes, requiring a power cycle.

Viewing 3 posts - 1 through 3 (of 3 total)