[Javi]

One comment–you are charging way to little for your app. I’m sure I pretty sure I could figure out how to do it myself, but I’m equally sure it would have taken days (if not weeks) to get something working that would just be a tiny subset of what your app provides.

Thank you!

Your Welcome and Thank you!

I am not trying to get rich off of the app it is just a side project I created for my own home, and maybe to pad my resume and ego. The project is in its second iteration on android, last iteration was free and I got too many feature requests and not enough gratitude or help.

[Javi]

location wasn’t needed since there was only one “zone X”

This was mostly in reference to sprinklers using a unique zone name such as “zone 1”, “zone 2” …. as using “zone” as a Location and a number as a device may cause too many errors. There would also be a few other things where a Location is implied or there is only one of Device using a given name (such as Air_Conditioner, Coffee_Maker) which is why it can be optional. There is also the ability to set a Default Location (such as Living_Room) which will automatically be applied to your voice command if no location is given, this will not affect commands where the user specifically omitted a Location. Example: If Living_Room is set as default and I say “turn on the TV and turn off the lights” it will turn on the living room TV and turn off the living room lights.

I think each different Pi (url) should be a “hub”. Is that correct?

That is correct

Once the delay as several seconds. I’m testing by looking out the window at the lights to see if the command was received by OpenSprinkler. Perhaps I was looking away too soon when I testing before lunch and incorrectly concluded things weren’t working.

The delay is one of the downsides to using IFTTT, also the “Show dialog over lock screen” (found in the Bridge screen) may help improve speed especially if using with Google Home.

I use the widget if giving commands from my phone for instantaneous execution, and an old phone running AutoRemote which accepts the IFTTT commands from my Google Homes. I may try to build a direct link to the Google Assistant in the future, but my free time is limited now as we have young children.

Hopefully I will have an update to address a few UI issues, Google Drive backup and android 8.1.0 fixes within the next month. If you have any additional feature request or find any bugs please let me know.

Best,
Javier

[Javi]

But, the voice command wasn’t recognized.

When I say the same thing after clicking the microphone icon in the voiceforiot app, it corrects “turn pathway lights on” to “turn pathway_lights on”. This works.

So, I’m thinking I should just use “pathway” instead of “pathway lights”. Or, maybe figure out how why the same correction isn’t being done when I use Google Assistant and all the stuff in between it and voiceforiot app.

Also the Spoken Location should be “pathway” and the Spoken Device should be “lights”. In this way it will allow for many variations of the command such as “turn on the pathway lights” or “turn on the lights in the pathway”. As long as the app can pickup on both a Location (pathway), a device (light(s)) and an action (on), it will trigger the correct Linked command. This will also allow for commands to be chained with multiple locations (pathway, living_room, pool) or multiple devices (lights, fan, sprinkler).

Example of triggering multiple locations with the same device: Turn on the pathway and living room lights. (This will trigger 2 commands, pathway-lights and living_room-lights. Spoken_Location-Spoken_Device).
Example of triggering multiple devices at the same location: Turn on the dining room fan and lights. (This will trigger 2 commands, dining_room-lights and dining_room-fan).

[Javi]

Should I post any fix (or other issues) I find here, or on your website somehow?

Most of the other people are reporting issues on Google+ or direct email, but I have email alerts setup so any place works for me.

Even though I deleted (and deleted all) linked voice commands, I couldn’t set up a “pathway” instead of “pathway lights”. I kept getting complaints about it already being defined. I tried exiting the app and re-entering, but that didn’t fix it.

Did you “Update Bridge” after changing anything in the app? This is needed as some users may use AutoVoice/AutoRemote to trigger other tasker_tasks/apps so using the “Update Bridge” updates AutoVoice/AutoRemote with acceptable intercept commands.

[Javi]

The IFTTT recipes are setup in the cloud, so they can be setup from a PC. The Voice for IoT app, Voice for IoT Bridge, and AutoRemote must be installed/updated/running on the android device

[Javi]

You are correct, the shortcut method involves using a phrase to trigger the the Voice for IoT app’s get voice dialog.

The IFTTT method has a few advantages:

1) Direct commands
2) If an android device is left at the location with the hub(s) then google assistant commands can be triggered remotely. Such as using an old android device as a server.
3) Works with google home.

Disadvantages:
1) There can be a delay of a few seconds
2) A little more difficult to setup, and must purchase AutoRemote
3) This method may lock out other Google Assistant commands, such as any command starting with “turn”.

[Javi]

Hi,

Thanks for trying the app! First let me mention there are a couple of bugs that should be fixed as soon as I have some time.

1) I updated Google Play services in the last update which broke Google Drive backup, I have a fix but it is taking the app (or Google) takes too long to realize when permission to access Google Drive have been revoked, which causes crashes. I have placed a button in the app to revoke this permission, so users do not have to let the app have permissions when it is not using Google Drive. Hopefully Google resolves this issue soon.

2) Android 8.1.0 broke the ability to read the current network BSSID (SSID of router). I have not had time to look into a fix, but will be doing so soon.

As for OK Google:

There are a few ways this can be done, If using Google Now the app integrates with the AutoVoice Tasker Plugin. If using Google Assistant it can be done using (IFTTT along with AutoRemote) OR (with a google assistant shortcut)

There are links to setup using IFTTT in the app. If using Google Assistant Shortcuts there are 2 launcher apps installed with Voice for IoT, One called “Voice for IoT” and one called “Voice Control for Voice for IoT”. All you would have to do is create a shortcut (for example “talk to my home” which has the Google Assistant “launch Voice Control for Voice for IoT”.

Please let me know if you need any assistance.

Best,
Javier

[Author]

Posts