go direct to lifesize, they have a module ready. its labelled 'lifesize icon clish SSH v1.0.0' module is made by status controls.

I haven't tried any of these codes yet, but it's worth trying the code sets from the Global Cache - Control Tower IR Database.
They have one of the largest code databases that I've used.
Some of the interesting codes included for the Apple TV Gen 4 are:
"Menu Home", "Menu Main", "Options" (might work), "Diagnostic Logs" (???), "Output Resolution", "Play Forward 10x", "Play Reverse 10x", and "Restart".
Many of these codes, I never knew existed.

Hope this helps!

Not really an answer to Geoff’s question, but we are working on an update for the ATV module.? With tvOS 14 it looks like Apple have gone a bit byte-happy with their message payloads which has given us a load of buffer overflows in the decryption.? At the same time I’m looking to improve feedback and transport control.? Update should be ready soon.

The Bonjour issue remains, but Crestron engineering have been actively working on that - we even had a zoom call to verify the exact symptoms.

Sorry Geoff - I didn’t mean to take your post OT.
Oliver - Ultamation

This is one of those things that is trivial to do in SIMPL# -- and is far more resilient that way -- but if this is all you’re doing (or you don’t already know SIMPL# / have the dev tools) it can be done in SIMPL+ as well (as long as it can be done via HTTP with no or basic authentication, HTTPS, or digest authentication basically forces the hand to SIMPL#.

?

You’ll need to open the connection to the device, send the request headers and body in one string – chances are very good that the server will require additional headers (like content type, connection keep-alive, and possibly language, etc). If you search the group’s acrchive there are plenty of general examples, or it might be most helpful to generate a request with a tool like Postman and see what it’s generating – this also allows you to test various things without having to recompile and reload a program each time.

?

The ”do I have to send the whole thing” is extremely implementation dependent – and since every Tascam I’ve controlled has been via serial – I would try sending only the changed attributes first but be prepared to send the entire object – I’d say a majority of implementations I’ve come across require the entire thing, which seems counter productive and prone to introduce greater levels of error but hey, whaddiknow?

?

--

Lincoln King-Cliby, CTS, DMC-E-4K/T/D
Commercial Market Director
Sr. Systems Architect | Crestron Certified Master Programmer (Diamond)
ControlWorks Consulting, LLC
Direct: (+1)440.771.4807 | Cleveland: (+1)440.449.1100? | Boston: (+1)508.695.0188 | DC: (+1)202.381.9070? | Fax: (+1)440.449.1106
Crestron Services Provider | Biamp Authorized Independent Programmers | Extron Qualified Independent Programmer

?

From: [email protected] <[email protected]> On Behalf Of Dillon Costanza
Sent: Saturday, November 21, 2020 9:51 AM
To: [email protected]
Subject: [crestron] Tascam Rest Api

?

Hi guys,

Don't have much experience with REST API's hoping I can just get a bit of info.

Here is an example command from the API.


I know I will be told to get this done through simpl# however I have never used it so that may be tough.? I was hoping I can write this in SIMPL+.? Just basically looking for a quick rundown, can I use a TCP/IP Client to connect on port 80 or do I need to connect inside the SIMPL+ module?

Also, it has the PUT url, then the header, and then body.? I am not sure how to format this inside simpl+.? Can I simply use a makestring and send the entire thing out at once, or do I need to send the PUT, wait for a response, and then send the rest?? A small breakdown of format would be extremely helpful.

Lastly, does an API typically require commands for every parameter to be sent? Or if I am not adjusting the IP settings can I just leave them out of the code entirely?


Thanks so much in advance.

Update the system-wide settings for the device.

These settings include network settings, name, id and other attributes not related to encode, decode, or media transmission.

Example URI

PUT?

Request

Hide

Headers

Content-Type: application/json

?

Body

{

??? "name": "string",

??? "device_roles": {

??????? "values": [

??????????? "strings"

??????? ]

??? },

??? "ip_scheme": "static",

??? "static_ip_address": "ip_address",

??? "static_netmask": "ip_address",

??? "static_gateway": "ip_address",

??? "static_dns_addresses": [

??????? "ip_addresses"

??? ],

??? "xml_active": {

??????? "value": boolean

??? },

??? "xml_url": "string",

??? "xml_poll_interval": {

??????? "value": integer

??? }

}