Categories

• Announcements

  Announcements regarding TRIGGERcmd

  45
  Topics
  92
  Posts

  

  @Viktor-Kanev, I had my friend with an iPhone try it. It worked for him. I suspect maybe you installed the Google Home app but maybe not the Google Assistant app yet?
• General Discussion

  A place to talk about TRIGGERcmd

  249
  Topics
  1197
  Posts

  

  @rktdno, the agent keeps a backup of the commands.json file, and whenever it finds invalid json in the commands.json file, it restores the backup. You could copy/paste your json into an online json parser like this one to check your syntax: https://jsonformatter.org/json-parser Sometimes it's just a comma at the end of the last entry, or maybe you're not escaping some quotes in a command.
• Example Commands

  A place to share commands you like to trigger remotely.

  53
  Topics
  141
  Posts

  N

  @Russ said in Hear stock quotes from Google Assistant or Alexa: stocks. Have you done it for the Mac version? I want to understand first the competitive space around alphavantage.co APIs. What's so special about alpha? Aren't there others in the stock API space like the one here https://financialmodelingprep.com/developer/docs/ Why are pharma majors not in this game? Why are Chinese API suppliers not able to match up??
• Instructions

  Instructions for each operating system, and various scenarios.

  77
  Topics
  276
  Posts

  

  @Tiago-Mártires, I think I see the problem. It's trying to write triggers to a computer with ID 5e54ffba256e4d0019bbcef2, but that computer doesn't exist anymore. I suspect you deleted it. I suggest you try this: Login as root (sudo su -) Backup your /root/.TRIGGERcmdData/commands.json file Delete your /root/.TRIGGERcmdData folder /home/tiago/Modelos/TRIGGERcmd-Agent/src/agent.js --console Enter your token Restart your triggercmdagent daemon Test again Now you'll have a new computer in your account that will match the ID in your /root/.TRIGGERcmdData/computerid.cfg file.
• Blog
  7
  Topics
  8
  Posts
  No new posts.