开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Crestron
  2. Messages
Expanded Topics Messages Polls
Date
Re: Authorization for Connections

 

开云体育

Brian - "Time & Forehead Savior"

Thank you very much ??

Trey

-------- Original message --------
From: Brian Matson <bmatson@...>
Date: 6/14/21 2:35 PM (GMT-06:00)
Subject: [crestron] Authorization for Connections

This is just a heads up to everyone.
I just got off of a 2 hour session with TB regarding secure user connections to the processor.
Here's the rundown:
  • CP4 processor running the latest firmware
  • TSW-1070 running the latest firmware
  • TSR-310s running 2.001.0078.001 firmware
  • Everything setup using SSL and all cloud junk turned off.
  • User setup in the system for local Crestron devices as a "connects" user.
TSW-1070 connects perfectly using setcsauthentication.
TSR -310s can't connect at all and are added to the blocked user list.
CP4 logs the error regarding the remotes.

Added a new user just for the TSRs to connect to and increased the authorization level from connects to user.? Still no connections.
Upgraded the firmware of one TSR to the version released this morning.? Cleared everything out, rebooted, and added it all back in ... still no connection.
TB support told me that mobile device users for projects that are hosted on the processor are now required to be authorization level of operators.
So, he said why not try that "just for kicks", although this shouldn't be the case for "non-hosted" projects.
Added a new user for the TSRs with operator user level, cleared out the remotes and blocked users, rebooted everything, and added csauthentication and IP Table entries.
Woohoo!!!? TSR with the latest firmware (2.001.0095.001) connects!? TSR with the last version fails to connect.

This is all getting quite ridiculous!
TB couldn't explain why the TSW connected fine with a lower user level but the TSRs wouldn't.
Yet another mystery related to new firmware combinations!
So, when in doubt, set the authentication for device connections to an operator.

Good luck!
Brian

Re: Series 3 FW v1.8000.0014

 
Edited

it fixed a Sonos connection issue I had with the 3.1.0 modules in an RMC-3
Re: Authorization for Connections

 

Glad I've already retired!
Re: Authorization for Connections

 

开云体育

This is one example of why I have the utmost respect for members of this group. Taking the time to document this issue and share it with the rest of us is very cool of you Brian!

Ryan Cunningham?

On Jun 14, 2021, at 12:35 PM, Brian Matson <bmatson@...> wrote:

?This is just a heads up to everyone.
I just got off of a 2 hour session with TB regarding secure user connections to the processor.
Here's the rundown:
  • CP4 processor running the latest firmware
  • TSW-1070 running the latest firmware
  • TSR-310s running 2.001.0078.001 firmware
  • Everything setup using SSL and all cloud junk turned off.
  • User setup in the system for local Crestron devices as a "connects" user.
TSW-1070 connects perfectly using setcsauthentication.
TSR -310s can't connect at all and are added to the blocked user list.
CP4 logs the error regarding the remotes.

Added a new user just for the TSRs to connect to and increased the authorization level from connects to user.? Still no connections.
Upgraded the firmware of one TSR to the version released this morning.? Cleared everything out, rebooted, and added it all back in ... still no connection.
TB support told me that mobile device users for projects that are hosted on the processor are now required to be authorization level of operators.
So, he said why not try that "just for kicks", although this shouldn't be the case for "non-hosted" projects.
Added a new user for the TSRs with operator user level, cleared out the remotes and blocked users, rebooted everything, and added csauthentication and IP Table entries.
Woohoo!!!? TSR with the latest firmware (2.001.0095.001) connects!? TSR with the last version fails to connect.

This is all getting quite ridiculous!
TB couldn't explain why the TSW connected fine with a lower user level but the TSRs wouldn't.
Yet another mystery related to new firmware combinations!
So, when in doubt, set the authentication for device connections to an operator.

Good luck!
Brian

Re: Authorization for Connections

 
Edited

"TB couldn't explain why"?
...er, 'cause they didn't test it?...

Seriously though, thanks for the update, Brian!!
Re: Authorization for Connections

 

So glad I'm close to retirement age...
Authorization for Connections

 

This is just a heads up to everyone.
I just got off of a 2 hour session with TB regarding secure user connections to the processor.
Here's the rundown:
  • CP4 processor running the latest firmware
  • TSW-1070 running the latest firmware
  • TSR-310s running 2.001.0078.001 firmware
  • Everything setup using SSL and all cloud junk turned off.
  • User setup in the system for local Crestron devices as a "connects" user.
TSW-1070 connects perfectly using setcsauthentication.
TSR -310s can't connect at all and are added to the blocked user list.
CP4 logs the error regarding the remotes.

Added a new user just for the TSRs to connect to and increased the authorization level from connects to user.? Still no connections.
Upgraded the firmware of one TSR to the version released this morning.? Cleared everything out, rebooted, and added it all back in ... still no connection.
TB support told me that mobile device users for projects that are hosted on the processor are now required to be authorization level of operators.
So, he said why not try that "just for kicks", although this shouldn't be the case for "non-hosted" projects.
Added a new user for the TSRs with operator user level, cleared out the remotes and blocked users, rebooted everything, and added csauthentication and IP Table entries.
Woohoo!!!? TSR with the latest firmware (2.001.0095.001) connects!? TSR with the last version fails to connect.

This is all getting quite ridiculous!
TB couldn't explain why the TSW connected fine with a lower user level but the TSRs wouldn't.
Yet another mystery related to new firmware combinations!
So, when in doubt, set the authentication for device connections to an operator.

Good luck!
Brian
Series 3 FW v1.8000.0014

 

Of those who have updgraded their 3-series procs to v1.8000.0014, Have you seen any issues???
Re: Ubiquiti wifi extender #bestpractices

 

开云体育

So, as an addition to the coax method, you can use DirecTV DECA3 adapters – one on each end – and get 10/100 way beyond 100 meters even over rg-59.? I think you can actually get about 1000 feet over rg-6 if your cable is good with no intermediate splices.? DECA3 are usually available on ebay for under 15 bucks apiece.? Don’t forget to get the 12V power supply also.? https://www.ebay.com/itm/323782964503?epid=20033524024&hash=item4b62f7f517:g:tBkAAOSw73xeaob8

?

From: <[email protected]> on behalf of ckangis <chris@...>
Reply-To: <[email protected]>
Date: Friday, June 11, 2021 at 11:35 AM
To: <[email protected]>
Subject: Re: [crestron] Ubiquiti wifi extender #bestpractices

?

Although I wouldn't design a network around this (hard-wared dedicated CAT lines are always best!) I have used the following in a pinch and they do work well:
1. If you have a COAX cable near where you need to add a switch and/or AP, ActionTEC makes an gigabit Ethernet-over-Coax device:


2. If there's absolutely no infrastructure, I have used various HomePlug Ethernet-over-PowerLine products and they seem to work reliably, though I think you won't get full speeds with this. It's actually amazing that this works and works well!!

Re: Error: CPHProcessor.exe # 2021-06-13 23:55:47 # Failed to allocate memory for response in respond api

 

I'll keep an eye on this over the next couple of weeks.
This is my home system and I get emails whenever the system re-starts so I should know for sure in the next 3-4 days if turning off the cloud bs & fw update made any difference.
CPU load has dropped a couple of percentage points. Used to idle about 25% now 23ish.
Cheers
-s
Re: Error: CPHProcessor.exe # 2021-06-13 23:55:47 # Failed to allocate memory for response in respond api

 

Thanks chaps.
FW: 1.601.3935.28796

No ports forwarded to the internet Lincoln.
I'll turn off all the cloud crap.
I see?1.8000.0014 is now up so I'll try that as well.
From the Release notes:
Updates:
  • Removed erroneous messaging in error log from Hydrogen Manager.
Re: Error: CPHProcessor.exe # 2021-06-13 23:55:47 # Failed to allocate memory for response in respond api

 

开云体育

And do you have any ports forwarded to it from the internet (or if it’s in a place like a University… do ACLs allow traffic from any potentially hostile ranges, e.g. students)?

?

--

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] [mailto:[email protected]] On Behalf Of ckangis
Sent: Monday, June 14, 2021 8:29 AM
To: [email protected]
Subject: Re: [crestron] Error: CPHProcessor.exe # 2021-06-13 23:55:47 # Failed to allocate memory for response in respond api

?

What FW version?
Do you have CloudClient turned off (and the Hydrogen stuff off also, depending on FW)?

Re: Error: CPHProcessor.exe # 2021-06-13 23:55:47 # Failed to allocate memory for response in respond api

 

What FW version?
Do you have CloudClient turned off (and the Hydrogen stuff off also, depending on FW)?
Re: Simpl# Debugging 4-Series

 

Isn't it a so old school for such an advanced tool?
I remember it was running perfectly on 3-Series, I don't understand why we are not able to get the same standard feature!!?
Error: CPHProcessor.exe # 2021-06-13 23:55:47 # Failed to allocate memory for response in respond api

 

Anyone know what these errors mean?
They started appearing a couple of months ago on my lighting DIN-AP3.
This has been running for a couple of years with no significant changes made to programming in that time.
Happens every 4 days or so then the AP3 reboots as it's obviously run out of memory

Error: CPHProcessor.exe # 2021-06-13 23:55:47? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 00:07:08? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 00:18:29? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 00:29:50? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 00:41:10? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 00:52:32? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 01:03:53? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 01:15:14? # Failed to allocate memory for response in respond api
Error: CloudClient.exe # 2021-06-14 01:20:12? # FTCtransPort: failedSystem.OutOfMemoryException: OutOfMemoryException
? ?at System.Threading.Thread..ctor(ThreadStart start, Int32 maxStackSize, Boolean check)
? ?at System.Threading.Thread..ctor(ThreadStart start)
? ?at Crestron.CloudClient.CloudTransError: CloudClient.exe # 2021-06-14 01:20:12? # port.sendViaTransport(CloudResponseManager& session, Stream xml, Int32 status)
? ?at Crestron.CloudClient.CloudDataCollector.CallbackFunction(Int32 stat)
? ?at Crestron.CloudClient.CloudDataCollector.frameIt()
? ?at Crestron.CloudClient.CloudDataCollecError: CloudClient.exe # 2021-06-14 01:20:12? # tor.requestFrame(CloudResponseManager& session, CloudRegisterFrameCallback func)
? ?at Crestron.CloudClient.CloudClient.issueFrameRequest(FRAMETYPE frameType)
? ?at Crestron.CloudClient.CloudClient.OnTimedEvent(Object source)
? ?at System.Threading.TimError: CloudClient.exe # 2021-06-14 01:20:12? # er.ring()
?
?
Error: CPHProcessor.exe # 2021-06-14 01:26:36? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 01:37:57? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 01:49:19? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 02:00:41? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 02:12:01? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 02:23:22? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 02:34:43? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 02:46:05? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 02:57:25? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 03:08:46? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 03:20:08? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 03:31:29? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 03:42:51? # Failed to allocate memory for response in respond api
Error: CPHProcessor.exe # 2021-06-14 03:54:13? # Failed to allocate memory for response in respond api
Cheers
-s
Re: CP4 versiports "locking up"

 

开云体育

Hi,

?

thanks for all the responses.

I?ve opened a ticket with TB, ticket numer

?

To those who also have the same issue: Could you please open a ticket as well if not done already?

I?d prefer to have that fixed rather than swapping out the control processor ?

?

Thanks, Thorsten

?

Von: [email protected] <[email protected]> Im Auftrag von Oliver Pemberton
Gesendet: Sonntag, 13. Juni 2021 23:23
An: [email protected]
Betreff: Re: [crestron] CP4 versiports "locking up"

?

I'm glad it's not just me. I have seen IR just stop working on a CP4 until a reboot.

In fact 2 out of 3 jobs where we replaced a 3 series with a 4 series we've ended up putting the 3 series back in to maintain reliability.

?

OP
Re: Partial substitution question

 

So it's been a while since I've had to create a module with string parameters on a predefined list, but sure enough - this one came up and bit me on the ass tonight!? Thanks everyone for chiming in!!!

? - Chip
Re: Color Picker #smartgraphics

 

开云体育

Use a serial buffer. The analog buffer (assuming those are the “buffers” you’re using) will pass input to output on the rising edge of enable if they are not the same; the serial buffer does nothing on the rising edge but passes values as they change while enable is high.

?

--

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] [mailto:[email protected]] On Behalf Of Gloomy Goose
Sent: Sunday, June 13, 2021 6:20 PM
To: [email protected]
Subject: [crestron] Color Picker #smartgraphics

?

Hello team, question about Color Picker widget.

I have many RGB light zones, I created subpage reference where put Color Chip widget to represent current RGB setup. Idea is to be able to press on Color Chip and open big pop-up with Color Picker widget.

Analog signals from Color Picker then sent via buffer to a controlled device.

Problem is that Color Picker will send RGB values to another devise from its last position. Feeding RGB feedback to Color Picker will actually update visual representation, but not the analog output values.

I don't want to create multiple pages with Color Picker, that's what buffers are for.
Not sure how to approach it. Any ideas?

Thanks.

Re: CP4 versiports "locking up"

 

开云体育

I'm glad it's not just me. I have seen IR just stop working on a CP4 until a reboot.
In fact 2 out of 3 jobs where we replaced a 3 series with a 4 series we've ended up putting the 3 series back in to maintain reliability.

OP
Re: Log Entry, continuous and inexplicable

 

Okay, I will take a stab at your question.

First off, it is just an "info" entry so it doesn't? necessarily mean anything that is important.? Personally, I wish Crestron would give us a way to turn off all these useless messages.? Many devices have a setting were you can set the severity of the messages that get log.? Whether there is some way to set that in Crestron, is anyone's guess.

Second, I am guessing this is either a message generated by C# itself or by the code that Crestron is written.? Not being a C# expert (or even a novice as that goes), that would be way out my realm to to say this is actually the case.

But I did try to implement my own web socket implementation about a year ago (using C programming language).? The protocol is described in RFC6455 and actually is a pretty simple protocol.?? ?


This message is probably referring to using TLS encryption which is not a requirement to use Web Sockets.? I actually was successful in partially implementing my own web socket connection only to find that the web browser then said it was changing the compression method (it didn't give me a choice).? I gave up at that point and started using the websocket functionality built in Node JS instead.

If you look at RFC6455, the word certificate is only mention twice.

Here

If /secure/ is true, the client MUST perform a TLS handshake over
       the connection after opening the connection and before sending
       the handshake data [].  If this fails (e.g., the server's
       certificate could not be verified), then the client MUST _Fail
       the WebSocket Connection_ and abort the connection.  Otherwise,
       all further communication on this channel MUST run through the
       encrypted tunnel [].

And here

      1015 is a reserved value and MUST NOT be set as a status code in a
      Close control frame by an endpoint.  It is designated for use in
      applications expecting a status code to indicate that the
      connection was closed due to a failure to perform a TLS handshake
      (e.g., the server certificate can't be verified).

So my wild guess is the websocket connection using the server certificate failed because it was an unsigned certificate and so the connection reverted to a different method using the client's certificate.? Of course, I am probably totally wrong.

Probably more information then you needed .

Steve
14941 - 14960 of 256486