Quote from: nime5ter on March 05, 2015, 04:21:41 PMCode Select"value":"(.*?)."
Thats fantastic, thanks alot.
You are great!

Once I have the thermostat and have it working with Voxcommando I will upload a clean group of Fibaro xmls.
Cheers
Steve
HOT TIP! Enable the History Window in the main UI when trying to problem solve. It provides a handy log of what is happening. Roll over lines in the History to get more details.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: nime5ter on March 05, 2015, 04:21:41 PM"value":"(.*?)."

Quote from: nime5ter on March 05, 2015, 03:33:10 PM
I would just
1. Clone your "Get status of {1}" command (right-click on the command in your tree and click "clone"),
2. Edit the name of the cloned command to "Get temperature" or whatever you like
3. Delete the logic block
4. Add the TTS action
"value":"(\w.*?)" that was used when checking if a node was on but I don't know where I can find any help documents on this. Unfortunately videos didn't help me either. Forgive me if I'm totally off the mark with this.Quote from: nime5ter on February 20, 2015, 02:32:44 PM
I don't really know what you mean by "ported for the Fibaro", or why you need VC to "support both devices", which implies you're still using the Vera as well as the Fibaro (??). If so, you can simply use your Vera commands to do those things.
Quote from: nime5ter on February 19, 2015, 04:33:28 PM
You have been using the "hard-coded" command macro that I asked you to test. It was just a test command for a known device ID.
In order for your command to make use of the 2 types of payloads that you have in your voice command (i.e. the payload XML file that contains all your device ID values, and the payload range of 1,100 %), you need to tell the command macro where those values go:http://192.168.0.155/api/callAction?deviceID={1}&name=setValue&arg1={2}
That is what allows the command to use *any* device ID, and *any* brightness level between 1 and 100 (in this case).
Quote
Anyhow, here is your command group cleaned up, including the one revised command that *may*(?) solve the problem with your garage light not turning on and off.
Quote from: nime5ter on February 05, 2015, 09:33:14 AM
Just as an aside: I did happen to see that you're trying to use the Our Groceries commands. Those won't work until you've entered your Our Groceries login info where indicated in the "update payload XML master list" command -- your email address and password need to replace the RoboB.SetText placeholders [[your login email address]] etc. You should enter that data without any square brackets (assuming you have an OurGroceries account already set up).