After doinga bit of testing i can confirm it breaks between nodejs-15.0.1-1 and nodejs-15.3.0-1 Ill keep looking and see if I can get a hold of any other versions of node so I can tell you the last version it worked on Narrowing dow the search for what broke it
Posts made by fennectech
-
RE: Suddelny agent wont connect
-
RE: Suddelny agent wont connect
Computer DEFINITLY has network access and its able to connect and stuff for the initial setup. And Iām able to use the internet from the machine. And the issue is still happening.
-
Suddelny agent wont connect
oken saved for next time.
Tokenfile: /home/fennectech/.TRIGGERcmdData/token.tkn
ComputerIDfile: /home/fennectech/.TRIGGERcmdData/computerid.cfg
Logging in with saved token to run foreground tasks.
Computer ID 5fe6b77c5191360019a0b662 saved for next time.
Write backup completed.
Initiated command removals
Initiated command adds
Added volumeSocket is trying to reconnect to https://www.triggercmd.com...
-|>- (attempt #1)
Socket is trying to reconnect to https://www.triggercmd.com...
-|>- (attempt #2)
-
RE: Passing numbers as parameters from alexa
Thats delightfuly simple Ill just toss that in my xboxvol script Thanks
-
Passing numbers as parameters from alexa
{ trigger: 'volume', id: '5fb025388293770019882f6f', params: 'five' } Running trigger: volume Command: xboxvol five Reported: Command Ran { trigger: 'volume', id: '5fb025388293770019882f6f', params: 'twelve' } Running trigger: volume Command: xboxvol twelve Reported: Command Ran { trigger: 'volume', id: '5fb025388293770019882f6f', params: 'twelve' } Running trigger: volume Command: xboxvol twelve Reported: Command Ran { trigger: 'volume', id: '5fb025388293770019882f6f', params: 'eight' } Running trigger: volume Command: xboxvol eight
Ive figured out how to get triggercmd working but the parameters are being sent as words which is not usable for what I'm trying to do