Good summary Nimestar (although I would expect no less).

I don't use tells any more so I haven't really looked at this script in a while

One thing to check is that you can send commands that work from Telldus Command Center

Hi James

Thanks for this. That all makes sense and looks like its not worth  the effort to go the Scrape route. I've knocked up a VC  friendly version of one of the sample Telldus Live Python apps which seems to be working (well at least the list devices functionality is) - I need to check with Telldus if I can share it.

I will chat with Ian at theDigtalLifestyle about the show and contact you privately - I think there is lots to talk about - all the new plug ins -Arduino etc.

Hi James/Nime5tar

I haven't posted in a while because things have just been working for me. I've recently been given a tellstick.net to work with and this doesn't work with my Tellstick script as it isn't controllable locally but can only be used with the Telldus live service.

There is a pretty full api for this service but they all involve using OAuth to register first. I'm trying to think how I would do this in VC. I could obviously code something but I was thinking there must be some way to do it with the standard plugins.

All the best
Garry

p.s. we ought to do a follow up on TheDigitalLifestyle soon

and it is fabulous - thanks

Hi James

Looks like this new version has solved my crash issue. Many thanks.
Garry

Glad people are enjoying it. Here is the link to the final edited version
http://thedigitallifestyle.com/w/index.php/2014/05/01/the-digital-lifestyle-show-449-voxcommando/

The press release we got sent suggests it does support z-wave

Quote
ZigBee and Z-Wave are two different short range wireless communication standards. The Iris Hub has circuitry that allows it to "talk" in both standards simultaneously. The Iris Hub creates Zigbee and Z-wave networks in your home - similar to your home area WiFi network. As such, these networks will have a certain range unique to your property.

The Iris Range Extender will help make the range of these Zigbee and Z-Wave networks larger.

I'm pleased to say James didn't answer every question about his dog and we had a really good show.  I'll post the link when it is out Thursday.

We are really looking forward to 'grilling' James on Tuesday :-)

If anyone wants to listen we will be broadcasting live at 8pm British Summer Time.


http://thedigitallifestyle.com/w/index.php/tdl-live-stream-and-chat/

You can use the chat room to interact with us during the live broadcast. If you are more patient the edited recording will be out on Thursday,

All the best
Garry

Maybe we should log which devices which approach works with.

Hi

I went with Python as I just couldn't get the tcp approach to work consistently with my Virgin TiVo here in the UK. To be honest I never really got to the bottom of why. Other than the Live TV command the python approach works absolutely rock solidly for me. According to the TiVo spec LiveTV needs you to wait for a response after sending it before trying any other commands. In my setup I'm not using the LiveTV button so I haven't looked at extending the python script - at the moment the Python Script doesn't wait. I think Jason's approach may be better for that if TCP is working for you.

Cheers
Garry

Great reaction. Hope it was a great day

 Thanks James VC.SetSpeechInput working for me as well - you'll be able to take my newly posted piece out of the wiki :-)

Maybe put something in the documentation along the lines of

VC.SetSpeechInput will look for the name you specify in both the 'friendly' name of the sound device and the internal device name. In the sound panel these are shown with the Friendly name above the internal device name for each device. For example if you have an Amulet device this will by default have a friendly name of Microphone and an internal name of Amulet Devices Remote Control and will show as:

Microphone
Amulet Devices Remote Control

VC.SetSpeechInput will switch to the first device in the list that matches the parameter.

In this example doing a VC.SetSpeechInput with a parameter of Amulet will find this device. Equally if the parameter was Microphone, and as long as the amulet was the first device in the list with Microphone in the friendly or device name, then the Amulet device will be switched to. Unfortunately most devices are by default name Microphone so it is probably unwise to rely on this and instead rename your devices to something unique -you cann to this within the properties of the device in the sound control panel.

One thing to note is that renaming a device can sometimes leave internal traces of the original device leading to unexpected results. In the above case it is possible if the device was renamed from Microphone to Amulet then unexpected results might occur. Doing a VC.SetSpeechInput to Amulet might not switch to the device instead the old traces of the Microphone-Amulet Devices Remote Control might be found first instead.

To avoid this we advise only renaming devices to a unique name different to any internal device name. For example changing the name to Amulet1 and doing a VC.SetSpeechInput Amulet1 would work.

before I forget - thank you