Topics created by tuicemen

I attempted to load netcore to my Linux machine and discovered it isn't able to run it. 😞
With dimming now possible via Alexa at least, I figured some new code would be required however there is no need to update code for this. (at least not for Alexa)

@russ Ya it is so simple to use. I like the list option for showing trigger names. My memory isn't what it use to be and my spelling never was the greatest!

@Smart-Communities, I know this isn't exactly what you were thinking, but I'm using your IP address placeholder idea in this video as an example of one way to share scripts with placeholders for things like IP address you'd store in config files. You could run a command like this remotely or locally to configure the IP:

roku ip 192.168.1.10

Then a command like this to simulate the down button on your roku remote:

roku keypress down

This article give a list names of other roku buttons.

@rem roku.bat @echo off echo %1 %2 %3 %4 if "%1"=="ip" goto :configip if "%1"=="keypress" goto :keypress if "%1"=="0" goto :findremote if "%1"=="off" goto :findremote goto :done :configip echo|set /p="%2" > c:\tools\rokuip.config goto :done :keypress set /p IP= < c:\tools\rokuip.config curl -XPOST http://%IP%:8060/keypress/%2 goto :done :findremote set /p IP= < c:\tools\rokuip.config curl -XPOST http://%IP%:8060/keypress/FindRemote goto :done :done echo Done.

This video shows that, and shows how to pass a number from 0 to 100 with Alexa using the TRIGGERcmd Smart Home skill by saying:
Alexa, roku on tv zero.

That works because Alexa interprets that as setting the dim level to 0 for the "roku on tv" device because roku is the command's voice word and tv is the computer's voice word.

Be aware if you use Google Assistant, when you say 0 it sends off as the parameter because it figures if you're setting the dim level to 0 percent, that's off. That's why I added this line after I recorded that video:

if "%1"=="off" goto :findremote

In hindsight 0 / off seems pretty arbitrary to assign to the making your Roku remote start beeping.

Also I acknowledge this a script so it's coding, so it doesn't solve the problem in the original post.

@russ said in Interface possibilities:

FYI, the agent does backup your commands.json file to commands.json.backup every time you change it, and it auto-restores the backup if you make a mistake in json formatting.

Awesome, I did see the commands.json.backup file but didn't realize it auto restored.

I don't like to use the cloud for backups, however I do for some things as well as a back up on disks.

Yesterday I did a clean up of my HomeGenie disabling things I thought I no longer needed. After this I tested my Panic Alarm and discovered there were a few things required that I had left out. These may have been set by default with the initial install of HomeGenie.

Besides the Demo-Toggle Door having to be enabled the Virtual Modules Demo program must also be enabled. As well the Automation.Demo 2 "DoorSensor" need to have the options to "Use as security sensor" and "Also trigger when armed Home" checked. The Automation.Demo 2 "DoorSensor" has to be in the closed condition prior to arming the security widget or you will need to send 2 panic calls

Here's the command to arm the HG security system widget to armed home.

curl http://HGAddress/api/HomeAutomation.HomeGenie.Automation/90/Control.ArmHome

If your like me and find the decimal point in the return a bit confusing you can change the line

os.system('~/.TRIGGERcmdData/sendresult.sh ' + 'Temp={0:0.1f} Humidity={1:0.1f}'.format(t,h))

to

os.system('~/.TRIGGERcmdData/sendresult.sh ' + 'Temp={0:0.0f} Humidity={1:0.0f}'.format(t,h))

if you wish the return to send a Fahrenheit value instead of Celsius you can add the line

t = (t* 1.8) + 32

just after the line

#Print Temperature and Humidity on Shell window

@russ Perfect! Thanks.

@tuicemen,

This is actually wrong ^. "deviceType":"light" is not a thing.

If adding that made it work, it's because when you change a command, TRIGGERcmd deletes and re-creates the Alexa smart home device. That needed to happen for the Alexa device associated with your command to have the new brightness feature.

Sorry I didn't tell you that sooner. Any newly created commands will have the new brightness and color features. Old commands just need to be changed so they get re-created. Or you can delete and re-discover them at https://alexa.amazon.com.

Also btw, only Alexa supports brightness and color so far. I'll look into Google Assistant soon.

EDIT 3/21/22: The "TRIGGERcmd Smart Home" action on Google Assistant supports color and brightness now too.

@russ thanks, I removed the deviceType from my json file and had Alexa rediscover and they do still dim. I edited my previous post.
It should be noted that using dim turns the device to that value. So if you turn a light on (100%) then say dim 20% it doesn't set the light level to 80 but instead sets the light level to 20.
At least that's the way it works for HG.

@tuicemen

You can add house code (A-P) and unit codes (1-16) as parameters in your bash scripts.

#!/bin/bash
house_code=$1
unit_code=$2
action=$3
curl "http://url:port/api/HomeAutomation.X10/${house_code}${unit_code}/Control.${action}"
Run it like this:
./control_x10.sh A 4 On

This way, you only need one script.

Thank you
boblewis