I'm having a hell of a time trying to format HTML on a formatted text object.

The text is a set of instructions that the techs need to follow to enable them to set up Sonos systems during build or on-site.
There are a set of bullet points they need to follow to allow them to configure the Line-In & HDMI inputs and assign to Favorites then save this into the program.
Line one of the instructions should be:
* Ensure the Sonos in this zone is named <S$19?player name> - note text inside <> is underlined as normal.
What I get when I close the html dialog is:
* Ensure the Sonos in this zone is named <<S$19?player name>> - note the double <>

Sometimes I can get line one to format properly and it displays the Sonos player name correctly.
However, there are two more instances in the instructions:
Settings > System - Products: <<S$19?player name>>
and
* Select the 3 dots beside Line In: <<S$19?player name>>

Note the extra <> and these always re-appear as soon as I close the dialog.

I've tried using an external HTML editor and pasting the formatted instructions in that way and VTP went mental.

Have to say this is one of the many VTP bugs that seem to have been ignored by Crestron as they have done nothing to improve VTP in the past few years.
While I was dicking about with this yesterday the auto-save dialog kept getting in the way (as usual), then VTP quit on me as I hit save. 'No bother there's a backup as the auto-save has been pissing me right off - eh'
Nope - no vtp.ASV file anywhere - what gives?


Anyone have any VTP HTML gems they wish to share so that I can strike this off my list?
Cheers
s

Thanks Iain. Those commands didn't work for me, but they did nudge me in the right direction.

In case anyone else looks for the answer later, what actually worked was simply entering the strings in the SIO as ASCII characters, without spaces or the \x prefix before each byte.

As an example, the command \x4F\x82\x30\x00 (HDMI 3) would be entered as 4F823000 in an SIO, connected to the Hex_Command input on the "AVProEdge_MXNet_ConfigureRX_CEC_1.6.7" module. That module then generates the command "config set device cec 4F823000 OUTPUT_ALIAS[6];" (this is for output 6) which is sent to the main module's Configure_Rx_Devices input.

Sounds like your client has the Crestron app not mobile, yes the naming is confusing. Unfortunately, you can no longer transfer the license. You can still download the app they have purchased. Go to App Store > Account > Purchased, you can find it and install it from here and mot have to purchase a new license.

I'm potentially OK with that, but it seems inconsistent with the apps themselves. And I'm not able to get the same functionality back by using that logic.?

Crestron Go (light blue icon) looks and behaves the same as the old Crestron Mobile (dark blue icon) on the old iPad.? The system setup is exactly the same.? But I can't use it due to the licensing issue previously mentioned.

The latest Crestron Mobile app?(dark blue icon v2.00.75) has an entirely different UI and setup process than the Crestron Mobile app (a different dark blue icon v105.63.3) that's on the old iPad.? Aside from the different UI it also requires a passcode for set up, but there was never a passcode configured for this system.

As an aside, the old Crestron Mobile app icon and the Crestron Go app icon have the same artwork but slightly different background colors.? The new Crestron Mobile app has different artwork.

I didn't follow the history of these apps very closely, but it appears that Crestron Mobile started as something in 2015 when this system was originally put into service.? And since then Crestron Go was released as it's replacement while a new Crestron Mobile app was built as something entirely different.

That's what I'm seeing but it doesn't make any sense.
?- Dave

You can't transfer purchases between apps.

If you've been using "Crestron Mobile," "Crestron Mobile Pro," "Crestron Mobile G," or "Crestron Mobile Pro G" (purple or dark blue icons) you must continue to use these apps and hope they work on current iOS versions.?

If you've been using "Crestron" (white or light blue icon) you can use Crestron Go or keep using the delisted "Crestron" app available through purchases under the itunes account.

I e-mailed support but figured I might get a quicker and more complete answer here...

A client was running the purchased Crestron Mobile app on an old iPad for many years.? The iPad died so I need to move them to a new one.? It seems that the latest app of choice is Crestron Go. I get it set up, but then it asks to purchase through the app store.? However, they already purchased the Crestron Mobile app.

Is there a way to transfer the Crestron Mobile app license to Crestron Go?? Do I need to continue to use the ancient Crestron Mobile app?? Or is there something else I should be doing?? I have to say, all the similarly named and similarly described Crestron apps make this whole process unnecessarily confusing.

?- Dave

That's currently the expected behavior for ADDUSER cmd on newer products (4-Series, TSx-x70, NVX, etc). After ADDUSER cmd is issued on these devices, you must then log in with the temporary password, and respond to the prompt to create a permanent password. Feature Requests were submitted to these product teams to add an option / flag to the ADDUSER command to make the newly created user's credentials permanent.

Personally I used several Toolbox Scripts that I wrote on the fly during a support call where we were changing previous creds (I think they still had admin:admin) to meet the new 7chr password requirements for newest NVX / DIR FW versions. The first sent the new ADDUSER cmd to all the endpoints. The second logged into all endpoints using the newly created account w/ temporary credentials - at which point many Toolbox popups appeared to Enter+Confirm New Password. I just repeatedly used CTRL+V, TAB, ENTER to assert them. Powershell EDK may be able to assert the new permanent PW (I'm not sure offhand), but to my knowledge Toolbox & Toolbox Scripting will always produce popup prompts to do this (no way to suppress the popups and configure everything from within the script).

开云体育

Lutron lead times are 14-20 weeks, long but reliable

I'm not sure Lutron delivery times, but that would be the best alternative imho.

Cheers!

开云体育

I'm only releasing a driver for Simpl.? I will leave it up to someone else to write one for home.? Shelly has a nicely documented API but supporting their growing product line is quite a bit of work just for SimplWindows.? I'm already on my 21st release of the driver set.

I personally use a bunch of their products in my home and have found them to be very reliable.

Jay

Will check them out right now thanks @jbasen.

Will you be releasing a driver for HOME as well? or only SIMPL??

开云体育

Shelly has a line of PRO relays that are din rail mountable and you can use the Shelly-Crestron drive I wrote that is available for download from my GitHub to integrate them into Simpl.? However, Shelly hasn't yet released a PRO line version of their dimmer yet.

Hope this helps

Jay

With CRESTRON's impossible ETAs for their DIN RAIL lighting units, are there any 3rd party DIN RAIL lighting modules compatible with CRESTRON via SIMPL or HOME?

Thanks.

Easiest way is to import an associated *.vta (if available).

TS Agent followed up with me.
They determined the root cause of the unicode font issue was the version of Java.
"If you want to use unicode fonts, you need to use java 8-251."

?

Interesting, where did you all find some theme to download ?

If you have the compiled theme this needs to go in C:\ProgramData\crestron\Core3\UserThemes

https://support.crestron.com/app/answers/detail/a_id/1000134

Hi guys and gals,

Can't believe i don't know the answer to this, but im trying to add a downloaded theme for use in VTPro, but can't figure out where to load it? I downloaded it but how to import it? Thank you!

On Sat, Nov 19, 2022 at 03:14 AM, Oliver Hall wrote:

Can you link to where the Unicode issue is discussed? ?Is this just a Crestron Studio problem

IIRC this issue was encountered by a user who contacted Crestron's ANZ (Australia/NewZealand) Tech Support team.
The support agent was able to recreate the issue by importing an Int'l Theme archive and recompiling it w/ Studio v1.81.096.
The agent confirmed the theme was able to successfully compile after removing/replacing the unicode fonts.
I don't recall offhand if rolling back to the previous version of Studio is also a viable workaround.

I see Thais temporary password expired nonsense on TSW-xx70 series all the time as well. Thought I was the only one