If you are using a Crestron DM system... I use standard CEC commands and they work great!? Play, pause, FF, Rewind, navigation all work.

Thank You.
That's all I needed to finish this.

Sorry to reply to a dead post. Just trying to add this stuff so if someone looks for it, it's out there!



If you use a 1st gen Insteon hub, you can issue commands thru the network.
If you have a Serial PLM, you can communicate with a Processor's COM port.

I have not done this myself, don't have the patience to set it up!

Sorry to reply to a dead post. Just trying to add this stuff so if someone looks for it, it's out there!


If you use a 1st gen Insteon hub, you can issue commands thru the network.
If you have a Serial PLM, you can communicate with a Processor's COM port.

I have not done this myself, don't have the patience to set it up!

Other things I found I didn't know about! There is AMX code running around to program Insteon:

https://web.archive.org/web/20081012172925/http://www.smarthome.com/321601.html

https://web.archive.org/web/20151204232334/http://www.smarthome.com/artemis-v2-64-device-insteon-controller.html

https://web.archive.org/web/20081026115729/http://www.smarthome.com/321602/Artemis-V2-64-Device-INSTEON-Controller-Software-Only-ASV02064/p.aspx

https://web.archive.org/web/20121110005743/http://www.smarthome.com/manuals/321600.pdf

Has anyone seen this and maybe have a solution? I have a project with RA3 and we are using some keypad buttons to control audio. After uploading the keypads work fine, but after about an hour they start to have lag in the controls. Like pushing the raise button for volume up can take as long as 6 seconds to output the digital signal going high. With debug enabled on the communication module it appears that the Lutron string is coming to the Crestron in its normal timely manner, the Crestron however lags in setting the associated digital output high.

Also interested in this thread. Attempting to Implement NMOS for ST2110 IP switching control.?

开云体育

I've used this? with Home and it work fairly well,

Not sure if they have a version that works with Simpl.

Has there been any updates on a Crestron SIMPL driver being developed to work with the Nvidia Shield Pro?

开云体育

Nobody I know enjoys mowing their lawn or vacuuming their homes.? Robotic mowers and vacuums are, in many ways, similar devices as they both these smart home robots incorporate navigation and locomotion functionality.? However, robotic vacuums have become common smart home accessories while robotic mowers haven't kept up.? Segway is working to change that with their Navimow i Series line of robotic mowers.? While the Navimow i Series mowers are positioned as entry level robotic mowers, with very competitive pricing, they include advanced navigation capabilities and features that set them apart from the competition.? This article provides a first look at the Segway Navimow i108E robotic mower.

You can find the article here:

For those interested in earlier articles that I've written, you can find those here:



For these interested in even earlier content that I wrote, you can find it all here though older content has formatting issues due to a transfer from blogspot to wordpress.



Thanks

You can give it a smart join number and then import the smart object, or you can give it single digital join and it uses the next 4 joins. If you look at the help for it, it explains this.

I'm missing something here.? The dpad is one object that controls 5 functions.? Up. down, left, right and ok.? I'm not seeing how to attach 5 different join numbers to it.

I've used dozens of these and they work fantastic. You can get them slightly cheaper through SnapAV/Volutone. ?

Michael

Thanks Michael,

I agree totally with your assessment.
If we set up a FQDN with DHCP and DNS on a server, everything would just work.

I will say that with Crestron's stack implementation, SSL does work with non-Crestron Home systems.
I have successfully used Crestron's "setcsauthentication" on many statically assigned devices without problems.

My opinion is that Crestron's VLAN "solution" for CH is flawed.
If they would allow us to treat the processor like a trunked device, then everything would work fine.
The Crestron processor would just add the appropriate VLAN flags to any traffic not on its primary VLAN.

The whole point of Crestron Home is that is should be easier to implement.

开云体育

I was using two X300 amps just recently and used the second ethernet port on Amp 1 to feed Amp 2.?
I was was getting the "Connecting" message you were speaking of on Amp 2 trying to stream the AES 67 source from amp 1.?

Flat network with IGMP turned on for the network switch that had the NAX Amp 1 network connection on it.?
Once I stopped using the loop out from Amp 1 to Amp 2 and moved Amp 2 network connection to the network switch, I was able to get AES 67 to work.

I know this isn't the same exact scenario but maybe something to keep in mind.?

I have successfully used the loop out with two 8ZSA amps in the past, but the X300 devices were for sure behaving differently.

We are having all kinds of issues with this at a home right now.
However, ours is actually behaving a bit differently than yours.
For some reason, we can't change the hostname to a static IP address.? The second we try this; the CH processor changes the status to awaiting authentication.
The device says that it is online, but the processor doesn't allow for any config changes or routing.
I have tried manually entering the CS authentication credentials through console, but nothing gets the device to show online in CH setup.
Crestron is confused, and their solution is to suggest that we put everything on the same subnet.
We have VLANs for a reason!!!!

What is even stranger, when you select the "Web Configuration" text in CH setup, it tries to load the NAX AES67 IP address not the management one.

Of course, once I select "Repair Connection" in CH setup, it forces the hostname again.

Oh ... and don't bother trying to put the NAX/NVX back on your control network because it doesn't work.
That's what I tried, with the Management on the clients network for Airplay.
No worky!? That's when Crestron tries to manage the device using the AES67 network!

Crestron ... please learn how to properly implement a VLAN strategy on a processor!
Instead of just giving us a place to input a range of addresses, why not just make the processor VLAN aware?
The processor should have an advanced networking tab that allows for entering the VLANs that should be allowed and the IP address of the processor on that VLAN.
This is the exact implementation in devices like the Josh.AI Core and OvrC Hub.

Or ... better yet Crestron, let us actually set things up in CH!
Stop trying to dumb things down just to get everyone on planet earth to install CH.
Just give classes on VLAN tagging and proper multicast implementation.
It drives me absolutely nuts that their answer is a flat network with everything in DHCP.
And let's not get started on trying to keep organized IP tables and Cresnet address ranges.

If anyone has successfully implemented this with the latest OS4 firmware, please chime in!
Brian

Hello...

Following the recent(ish) upgrade to CH which allows a Home processor to deal with devices across VLANs, we have implemented VLANs on a larger site.
The site was running multiple NVX devices on an already busy network. ?Previously we were seeing some packet loss and lag but the new VLAN arrangement has much improved these symptoms. ?General network performance is improved too (outside of the Crestron stuff).
Aside from having to change the Processor to an IP address (instead of the default hostname) in each NVX/NAX device web GUI, this was a straightforward change and everything came online ok.
However: ?we are now unable to connect to NVX AES67 streams from the NAX. ?On the web GUI of the NAX we just see 'Connecting' under the Stream Status table.
Multicast addresses are all correct. ?System was set up natively in CH (authentication, chdevice etc.) but we have tried a few manual tweaks as well.
Video is working fine, Airplay working fine. ?Multicast / IGMP appears to be right; there's no network flooding or crashing and the NVX is streaming video perfectly happily.

Since the Multicast addresses are populating correctly, perhaps this hanging on 'Connecting' might be an authentication issue... however, the only user in the user table is the system-generated chdevice. ?(I did try adding the chdevice user to the 'connects' group as well, but no avail)

This was working fine before we put the VLANs in. ?

We are using dual ethernet ports on the NAX. ?1=Management, 2=AES67. ?Note the Management VLAN is our General Access network, for Airplay etc, *not* our Control System VLAN which is seperate again. ?So I suppose we could put the NVX/NAX back onto our control system subnet but we'd prefer not to.

Has anyone else seen/overcome this?