Keyboard Shortcuts
Likes
- Crestron
- Messages
Search
Re: Blast from the past - Switch Retry!
On Mon, Feb 12, 2024 at 08:55 AM, Lincoln King-Cliby wrote:
almost as annoying as the S+ compiles that lock up SIMPL windows until you figure out which copy threw up the waning message and if you're lucky you can dismiss it.Ooh, that one is also sooooo annoying! ^^^ |
Re: Blast from the past - Switch Retry!
¿ªÔÆÌåÓýIt has been coming and going for me over the last 6 months or so...almost as annoying as the S+ compiles that lock up SIMPL windows until you figure out which copy threw up the waning message and if you're lucky you can dismiss it.
Get From: [email protected] <[email protected]> on behalf of Slip Cougan <gk.otoole@...>
Sent: Monday, February 12, 2024 5:25:07 AM To: [email protected] <[email protected]> Subject: [crestron] Blast from the past - Switch Retry! ?
Started seeing this recently when opening Simpl Windows programs.
Have not seen this since Viewport days! Anyone else seeing this? |
Password reset for DM XIO DIR-80
I know these are not the most respected pieces of hardware. ?I picked one up from surplus and finally got around to playing with it. ?I can access it through toolbox but I don't have the username and password. ?It has the 2.0 firmware. ?The default admin/admin does not work. ?A hard reset only resets the DHCP. ?I have been checking around and there doesn't seem to be a way to do a hard reset. ?The other NVX units have at least a process albeit long one to do a hard reset (11 times ?pressing reset). ?Someone on Reddit says there is a way to through a USB drive. ?I don't have access to that program. ?Any thoughts? ?I know there will be a lot of folks that say it is not worth the trouble. ?
|
Re: ONVIF Camera PTZ Control Protocol
Crestron via RS232 via Rasberry Pi via generated Python script to device ?definitely sounds better than understanding C#/S# and writing/unit testing/documenting ?my own code, and is absolutely something I¡¯ll look forward to implementing in the future, if for no other reason than to give my employer and clients that they¡¯ll be getting the best most robust solution possible.
|
Re: ONVIF Camera PTZ Control Protocol
I like the being able to test on a PC.? Python is very much a "get things done" language, and works identically on PC and Mac (for development and testing's sake).? Good on you for picking the tool that does the job of talking best to the gear you want to use.
My favorite integration I've done is an SMS text messaging bot, to & from Crestron.? The homeowner can open gates, lock/unlock doors, and request a check all of the doors for the whole house (done via the security system), and other things (like fireplaces left on), just by sending a text message (the status comes back as reply).? This works by using Twilio SMS to provide a dedicated phone number for the messenger, and then my Python messenger code is hosted on a dinrail RPi, and talks to Crestron processor via RS232, where I've got logic blocks that forward on the signals the text messenger would care about.? Most of the work of properly communicating with Twilio (including proper authentication) would be cumbersome to do in S# but is comfortable in Python, especially where Twilio themselves gives you sample Python code to utilize their services. The ONVIF test code I did at first "for the glee" but now that I did it, at some point I will likely actually implement it in real life, now that I've gone to the effort of observing that it actually works (and in a vendor-neutral way as a bonus!)? Before it's production ready, it'll need proper error handling (so it doesn't crash with a TCP exception if a camera is offline), support for multiple cameras (why control just one?)... the ability to recall "home position" and other presets (originally set by homeowner via camera web UI) as well as making it so that the "stop" command happens upon a UI button release, rather than having chunky steps of movement per button press. |
Re: ONVIF Camera PTZ Control Protocol
I¡¯ve been playing around with Bitfocus Companion as a ¡°gateway¡± to devices that are a hassle to control from Crestron, or not worth the effort to write my own code from scratch. Similar approach to yours. Send serial strings (that I define) from Crestron over UDP or TCP connection to Bitfocus, which performs desired action based on received string. I¡¯ve been testing with a PC, next step is to install Companion on Pi.? |
Re: Android APP ETA
+100 to all the previous comments...? ?And I only have 1-2 clients that want to use the Android version...its the principle of it...
Also, don't forget that in addition to the $100 jerk tax (x2 for phone and tablet...) they still don't have a proxy service so you have to punch open ports (no longer a real option) or have the client, who paid huge money, to use a VPN when away from their home - totally unacceptable. For this and many other things, George and Fred are rolling in their graves...:( |
Re: Samsung RS232 Direct Volume commands
Rather than "old school", I'd simply call that "the right way to do it" :-)
toggle quoted message
Show quoted text
I checked an old program where I did exactly the same thing, but it used parameter 259 (twos complement) instead of 258 (binary). --- On Friday, February 9, 2024 at 11:33 AM, MSTC wrote: |
Re: Android APP ETA
EXACTLY !!!! Crestron please? give both operating systems? the same attention to detail. Employ someone to oversight crestrons? mobile experience rather than the disjointed lapproach we endure now as integrators trying to promote your product . The stupidy and small mindedness is underwhelming. I am losing projects to? C4 as we can't even download an antiquated app that's demo fails let alone support a mobile intercom experience! How long has crestron been great mates with 2n , rava sip?... pathetic is an under statement. On Sat, 10 Feb 2024, 23:21 Slip Cougan, <gk.otoole@...> wrote: I really don't think Crestron has any interest in serving the Android market. |
Re: Android APP ETA
I really don't think Crestron has any interest in serving the Android market.
I have seen clients ditch Crestron and opt for Control4 because of this. They would not even entertain the idea of Home as the have lost confidence in Crestron. Personally, I'm sick to death with Crestron dragging their feet over this. The last update to the Android app was 20 March 2018. Nearly six fucking years. REALLY! |
Re: ONVIF Camera PTZ Control Protocol
Hi DizzyEgg -- "needs a special Onvif username and password" is a characteristic of the specific Axis camera I tested this on, which uses a separate authentication system for ONVIF?.? My professional accomplishments earning a living solving problems writing code are such, that whether I'm an "actual developer" isn't a serious question for me or anyone who knows me personally.
While HTTP and UDP are something I understand down to the frame level, I am not in the business of developing driver products for cameras -- the point is that I don't WANT to implement Onvif, I want to be able to let my user push a button and move their camera without waiting for 8 more years (this thread started in 2016) for someone to put together a quality S# driver.? This simple Python script does it today.? And I have ChatGPT to thank for putting a script together, which I'm able to follow and tweak, but certainly not compose from scratch in under 30 minutes.? A $350 din-mountable Raspberry Pi from DigiKey (e.g. Iono Pi by Sfera Labs) is robust enough to host it for me looking 100% professional, and then I'm off to solving another problem. I don't think anyone who posted in this thread wants to implement Onvif from scratch either.? I think any of us would gladly use an open-source library from a Python repository to solve a customer's problem.? There's no extra credit for originality, only functionality.? It's open source software running on an isolated device, so, not even intellectual property concerns arise.? I think the point I'm trying to make, is that Python and ChatGPT are tools we can use to solve problems in less than 8 years and that S# isn't the only tool in the toolchain in the world of installing Crestron gear. Also UDP is GREAT for getting signals out of SIMPL and into Raspberry Pi.? Despite being "connectionless" by definition, in my experience running it over Ethernet it's more reliable than IR and is definitely adequate for transporting UI button presses.? You send a string to SIMPL's UDP/IP block, and it shows up intact on the Raspberry Pi that's listening, well over 99.9% of the time, and it's really that simple.? If I go read RFC 768 defining UDP, that knowledge is a bonus, but not necessary for me to solve problems with it! One more benefit using Pi's is there's an HDMI port that can be plugged in for troubleshooting issues with the script (and RPi's also support VNC out of the box).? Any time I dedicate a Pi to something like this, I set it to boot up so the script runs with its output onscreen 24/7, so troubleshooting is as simple as viewing HDMI Out or connecting with VNC.? I'm happy to share the scripts I use to quickly set up Pi's this way from out-of-the-box condition, autobooting to the script(s) of your choice, onscreen. |
Re: ONVIF Camera PTZ Control Protocol
The fact you¡¯re using chatGPT, and that you use phrases like ¡°needs a special Onvif username and password¡±, and that you no doubt don¡¯t a) understand what Onvif is, or how it works and b) have no idea what that code (script!) is actually doing, fills me with dread, and reminds me of one colleague of mine that thinks that getting some resemblance of a working result using chatGPT puts the them in a better place than understanding the the hell is going on.? Do yourself a massive favour, download the Onvif device manager (official), read the Onvif api, learn what UDP and HTTP actually mean, and become an actual developer. |
Re: ONVIF Camera PTZ Control Protocol
Just to see if my word was good, I tried exactly what I proposed, and got results in less than 20 minutes on an Axis PTZ camera.
First minute: I opened ChatGPT and typed "How on a Raspberry Pi in Python can I send PTZ commands to an ONVIF-compliant IP camera?" Second to fifth minute: reviewed the script it gave me, and put my actual camera IP, username, and password in place of its placeholders.? Ran the script.? Got an error. Sixth through tenth minutes: troubleshot "Sender not authorized" error message.? Turns out I have to add a special ONVIF username and password to the camera. Eleventh through fifteen minutes: still got the "sender not authorized" message.? Googled for help, turns out there's also a checkbox I had to click on Axis cameras to unblock something. Sixteenth through seventeenth minute: got an "Unknown Error", turns out the Python script asks the camera for all of its configuration info and never uses it.? Commented that part out, problem went away. Eighteenth minute: ran the script again.? The camera started moving to the right (the sample action that ChatGPT coded) for 10 seconds.? Awesome.? Other than my PTZ cam is now pointed a at wall :) , so, I manually moved the camera back through its web UI. Since I'm done with this script, I need do no further...but to make it talk to Crestron, I would add a UDP listener and add actions for each of the four cardinal directions (or ask ChatGPT how to load a named/numbered preset) and then a SIMPL UDP/IP connection to trigger this from within a project.? I'm too lazy to do this myself, but maybe ChatGPT could do this for me. Working script that simply moves the camera (with no UDP listener)
Not to beat a dead horse, but my next request to ChatGPT was: "Great! Let's modify this script to first 1) remove the request for the configuration information we aren't using, and 2) also listen on UDP port 5555 for packets containing a single string "UP", "DOWN", "LEFT", "RIGHT", and upon receipt, move the camera the named direction." The script it generated did exactly as requested and needed no modifications (beyond re-adding my credentials), and I used a "UDP Packet Sender" app to craft test packets to make it work.? It moves the camera too far per step, but it's easy to see where I can change a number to fix that.? Not pasting it for the sake of brevity unless someone asks (it gets long since ChatGPT made it multi-threaded) I'm into this 30 minutes just for the glee, and have a working solution... that is, if a RasPi is a tolerable addition to the setup. |
SSL errors
system rebooted Jan 25
124. Notice: CIPCommandProcessor.exe # 2024-01-27 09:26:01? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:55575... pending.?
125. Notice: CIPCommandProcessor.exe # 2024-01-27 09:26:11? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:55575... pending.?
126. Error: LogicEngine.exe [App 1] # 2024-01-27 23:13:49? # Did not receive End of Query Acknowledge from device at Slot-05.IP-ID-7C.
127. Notice: CIPCommandProcessor.exe # 2024-01-28 07:53:01? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:56420... pending.?
128. Notice: CIPCommandProcessor.exe # 2024-01-28 07:53:11? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:56420... pending.?
129. Notice: CIPCommandProcessor.exe # 2024-01-28 07:53:21? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:56420... pending.?
130. Notice: CIPCommandProcessor.exe # 2024-01-28 07:53:21? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:56420... closing socket.?
131. Notice: CIPCommandProcessor.exe # 2024-01-28 07:53:31? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:56419... pending.?
132. Notice: CIPCommandProcessor.exe # 2024-01-28 07:53:41? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:56419... pending.?
133. Notice: CIPCommandProcessor.exe # 2024-01-28 07:53:51? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:56419... pending.?
134. Notice: CIPCommandProcessor.exe # 2024-01-28 07:53:51? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:56419... closing socket.?
135. Error: LogicEngine.exe [App 1] # 2024-01-30 11:18:31? # Did not receive End of Query Acknowledge from device at Slot-05.IP-ID-7B.
136. Notice: CIPCommandProcessor.exe # 2024-01-30 16:00:37? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58595... pending.?
137. Notice: CIPCommandProcessor.exe # 2024-01-30 16:00:47? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58595... pending.?
138. Notice: CIPCommandProcessor.exe # 2024-01-30 16:00:57? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58595... pending.?
139. Notice: CIPCommandProcessor.exe # 2024-01-30 16:00:57? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58595... closing socket.?
140. Notice: CIPCommandProcessor.exe # 2024-01-30 16:01:07? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:58594... pending.?
141. Notice: CIPCommandProcessor.exe # 2024-01-30 22:42:03? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58831... pending.?
142. Notice: CIPCommandProcessor.exe # 2024-01-30 22:42:13? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58831... pending.?
143. Notice: CIPCommandProcessor.exe # 2024-01-30 22:42:23? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58831... pending.?
144. Notice: CIPCommandProcessor.exe # 2024-01-30 22:42:23? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58831... closing socket.?
145. Notice: CIPCommandProcessor.exe # 2024-01-30 22:42:33? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:58830... pending.?
146. Notice: CIPCommandProcessor.exe # 2024-01-30 22:42:43? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:58830... pending.?
147. Notice: CIPCommandProcessor.exe # 2024-01-30 22:42:53? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:58830... pending.?
148. Notice: CIPCommandProcessor.exe # 2024-01-30 22:42:53? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:58830... closing socket.?
149. Notice: CIPCommandProcessor.exe # 2024-01-31 08:04:54? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58946... pending.?
150. Notice: CIPCommandProcessor.exe # 2024-01-31 08:05:04? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58946... pending.?
151. Notice: CIPCommandProcessor.exe # 2024-01-31 08:05:14? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58946... pending.?
152. Notice: CIPCommandProcessor.exe # 2024-01-31 08:05:14? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:58946... closing socket.?
153. Notice: CIPCommandProcessor.exe # 2024-01-31 08:05:24? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:58945... pending.?
154. Notice: CIPCommandProcessor.exe # 2024-01-31 08:05:34? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:58945... pending.?
155. Notice: CIPCommandProcessor.exe # 2024-01-31 08:05:44? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:58945... pending.?
156. Notice: CIPCommandProcessor.exe # 2024-01-31 08:05:44? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:58945... closing socket.?
157. Notice: CIPCommandProcessor.exe # 2024-02-01 00:31:51? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.233:59892... pending.?
158. Notice: CIPCommandProcessor.exe # 2024-02-05 21:49:53? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:65342... pending.?
159. Notice: CIPCommandProcessor.exe # 2024-02-05 21:50:03? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:65342... pending.?
160. Notice: CIPCommandProcessor.exe # 2024-02-05 21:50:13? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:65342... pending.?
161. Notice: CIPCommandProcessor.exe # 2024-02-05 21:50:13? # AcceptSecureClient: SSL Negotiation not complete for 192.168.10.1:65342... closing socket.?
hacker? |