Rexabyte

It should run on 2.6.0 without any problems.

We don't offer a driver that controls that model as it's not SmartCast.

Even if you wanted to have it so you could update the URL through a property:

<property>
  <name>Webview URL</name>
  <type>STRING</type>
  <readonly>false</readonly>
  <default/>
</property>

-- Define the property name
local URL = "Webview URL"

-- Update the URL when the property changes
function OnPropertyChanged(strProperty)
	if (strProperty == URL) then
		-- In thise case the 'uibutton' proxy is defined as 5001
		C4:SendToProxy(5001, "URL_CHANGED", {url=Properties[URL]})
	end
end

@turls The driver has been updated with two new commands to achieve what you need (version 2.9.190): https://annex4.link/drivers/udp-203?changelog=latest

@rolldog Yes, the input issue was fixed with the new proxy.

@turls I'll set a bit of time aside later in the week to get the required commands into the driver as programming commands.

The Dimmer key is under the button mappings, do you need it as a programming command?

I've replaced one of the proxies in the driver (the Virtual Switch) and will be phasing out the previous version of the driver. Auto-updating the old drivers would cause problems as the proxy type has changed. As such the file has been renamed so people don't try and update over the previous version, this version requires a fresh install.

https://annex4.link/drivers/udp-203

I've added the advanced commands in the protocol as device specific commands for this release as well.

Changes:

• Added discrete mute commands.
• Added 'Set Output Resolution' command.
• Added 'Set Zoom Ratio' command.
• Added 'Repeat' command.
• Added 'Set Subtitle Shift' command.
• Added 'Set OSD Position' command.
• Added 'Set Time Information Display' command.
• Added 'Set HDR Mode' command.

@turls

You'll need to go to the virtual switch portion to send the mute command.

The driver generally creates the polly announcement from Amazon Polly once the driver is added to the project. The only reason I could think of that it wouldn't would be if you didn't have a  connection to the internet at the time the driver was added.

If you did feel free to PM me some more info and I can take a further look.

The TTS is calculated realtime from Amazon Polly so you need an active internet connection. The announcement is downloaded to the controller and saved as a wav file during the synthesize process.

I could add a setting to play the latest downloaded file, but this may end up being confusing and not aligned if you're using variables. As above if you were using temperature and having it read it out on some event, you'd potentially get an incorrect reading as it would be whatever was the last downloaded.

If you just want to use the TTS to synthesize static speech you can copy the announcement file created and play it as a normal announcement.

I put together a little album as to how you would go about the whole process: https://imgur.com/a/lwfxc

1. You inject %TIME or %DATE into the string to get the current time and or date.

2. The current temperature is variable id 1018 on a thermostat if I recall correctly. So it would be %{deviceId,1018} to get temperature. Where device ID is the id of the thermostat.

Full example: The time is %TIME and the current temperature is %{2380,1018}
 

If you want to send me the .zip without the script portion I can take a further look.

I'm currently running a wired connection in my house with the latest updates and WOL continues to work. Send us an email (annex4) and we can take a further look into it.

3 minutes ago, msgreenf said:

Why so you have them 2x? They should only be once

Sent from my Pixel XL using Tapatalk
 

What should only be once? I'm not sure what you're referring to.

Everything looks correct in terms of file locations and names. I wonder if it's the lack of the "qty" attribute in the <proxies> element, see below from the Getting Started Guide:

<proxies qty="1">
       <proxy proxybindingid="5003" name="KEYPAD" small_image="devices_sm/keypad_16.gif" large_image="devices_lg/keypad_32.gif">light_v2</proxy>
</proxies>

Maybe try adding the "qty" attribute and seeing if that works?

You can find the driver here: https://annex4.link/drivers/vizio-smartcast-tv

The driver is an open beta now. It currently comes with a 60 day trial to give you ample time to beta it and provide feedback.

I've just uploaded a new version of the driver 0.2.75 for everyone beta testing.

Changes:

• Added support for entering the PIN by a Control4 interface.
• Added support for HDMI 5.
• Fixed an issue when issuing the smartcast action (it wouldn't swap inputs).
• Fixed an issue when issuing input selection button.
• Fixed an issue where the off command was not turning the TV off.
• Fixed an issue where the power commands were not notifying the proxy.

I've improved the installation process. When entering the PIN while pairing you can do it from a Control4 interface rather than having to enter the PIN in the Pairing Code property of the driver. You would just select the TV to watch and then hit the number buttons to enter the PIN displayed on screen.

The beta driver is now available. Everyone that has commented previously please PM me and I'll provide you with driver.

Both features have been added to the pipeline.

Yes, I have, it will be in the next version. As will dynamic button bindings in the properties.

There is a way to launch a browser to a specific URI, I'll look into adding a programming command for it.

I just want to make sure we're on the same page. Even if you set the port in the properties to what it initially is, it can change if your router were to reboot or you decide to move the WeMo to another outlet. You need to be able to detect that change.

For example, I just pulled my WeMo out of the wall when it was port 49154. When I plugged it back in it had a new port of 49153.

if you're doing this I apologize, but I'd rather save you the hassle of people complaining it doesn't work after a while.

Glad you could make some use out of the code I had posted, however, I just wanted to mention something that could lead to some issues. The WeMo port can change from time to time, it isn't only 49153, it can change freely.