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!

For me adding commands to the commands.json file was where I usually (like most newbies) messed up.
Today I decided to create a little tool to help me with that.
It is a netcoreapp3.1 Windows tool created with Visual Studio in #C and adds the new command line to the first part of the json file.
Although I use TRIGGERcmd on a Raspberry pi I still am more comfortable in Windows.
Command Writer.png

@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.

@russ Thanks, I found my error, the line in the commands.json file was correct.
I was putting in the wrong X10 address for my test thus it was turning on/off a light in the basement not my test light.