Goose66

No times because the ISY only supports integer state values - no strings or timestamps. So just door state: Open, Closed, Closing, Opening, Stopped, or Unknown. I am hoping that a future version of the ISY firmware will allow timestamps.

Don’t know about Google Home but Alexa generally won‘t let you open doors for security reasons and you can’t “close” devices on ISY because they don’t show as doors in Alexa app (you get a “(devicename) doesn’t support that” error). You can, however, turn on (open) and turn off (close) garage doors. I have a program that specifically closes all the garage doors and that’s all i expose to Alexa.

The 5.0.X firmware branch supports external nodeservers that provide interfaces to devices outside of the Insteon and Zwave devices natively supported by the ISY. Polyglot is a runtime environment developed by community members and installed on an RPi running on your LAN (or could be compiled for other platforms) that allows you to install third-party developed nodeservers (also referred to as "polys") to support various types of devices. There is a Polyglot nodeserver (developed by me) that supports MyQ compatible door openers. More information on Polyglot: https://forum.universal-devices.com/forum/111-polyglot/ More information on the MyQ Nodeserver:

That's right - it had a patch for the weather data or something like that.

Firmware 4.7?!?

In my setup, the MyQ nodeserver polls for status every 20 seconds when there is door activity (a door opening or closing), or on initial startup, and then drops back to a polling interval of every minute when the doors have been idle for 5 minutes or longer. However, I have a program that is triggered by an On command from the motion sensor in the garage and, when motion is detected, forces a query of the node for the corresponding garage bay door from the MyQ nodeserver. That way, if the motion is due to, e.g., the door opening, it will perform a query and return the "opening" status for the door right away instead of waiting for the poll. If someone walks into the garage is and is walking around, it will query the door status every time an On command is sent from the motion sensor (about every 10 seconds).

+1 for MyQ Polyglot Nodeserver. The status of the door is through polling, which can be like every 3 to 5 minutes, so the status is not real time. But the opening and closing are real time, and you can use a motion detector in your garage (or your window/door contact sensor) to force the nodeserver to poll for door status from the MyQ service via a program.

Does your new router have a firewall? What DNS server is setup in the new router (it will be delivered to the ISY in the DHCP network configuration)? Check your system configuration page to ensure "Automatic (DHCP)" is selected and also your "About" dialog box to ensure that your administrative console version matches your firmware version. Also look at the TCP/IP configuration on your computer to see if maybe the DNS server is overridden for it. This would also point to DNS in your new router not being setup properly.

As to static IP addresses, I tend to prefer DHCP with specific IP address assignments in the router/DHCP server. Most modern routers support DHCP IP address assignment. This gives you the same advantages as fixed IP without the configuration having to be maintained at each device. In addition, the router can show the status of the device in its administrative console, where there may not be status available for devices with static IP addresses if there has been no outside routed traffic. An additional advantage is that most modern routers also provide a DNS server, which acts mostly as a DNS forwarder but will cache names and keep device names and their corresponding DHCP provided IP addresses from the LAN side in the DNS cache, whereas devices with static IP addresses generally will not report their device names to the DNS server.

Those are the same adresses for the two computers on the other router. Are you sure your computer is setup for DHCP and what are the DHCP settings on the old router?

Assuming something has not gone awry with the network configuration in the ISY, then yes. But it also should have worked with the other router, unless it is actually a different subnet (e.g., you were thinking it was 192.168.1.161 but it is really 192.168.7.161). If the settings in the old router haven't changed, then your computer should pull an IP address from DHCP on the same subnet as the ISY.

I agree that this all new. That's why I am kicking myself for not looking into it more before replacing the AVR in my theater. Oh well, I am only in for $400 and am have been waiting to do a 4K setup and projector in the theater anyway. If I could just win that lottery!

I don't think so I have blue, yellow, grey, black, and white straight cables in my setup. The only crossover cables I have are red and yellow and have a sticker on them that say "crossover cable". Without the sticker, I imagine the only way to tell is to look at the wiring of the ends. Of course, as paulbates said, with a fairly modern adapter, it may not even be necessary.

It's not the color of the cable but the way the ends are wired. Look at the colors of the little wires inside the clear plastic RJ-45 connectors. If the two ends are wired the same, it is a straight cable. If the green/white and white/green pair is swapped with the orange/white and white/orange pair, it is a crossover cable.

The Denon AVRs listed have 9 and 11 discrete amps so they can drive Atmos 7.1.2 and 7.1.4 directly. With Atmos, none of it is "upmixing" - it's taking the sound objects and outputting them from the speakers in the setup that give them the most accurate placement. That's the difference between Atmos and Dolby Digital. You have to stop thinking of channels of recorded audio and start thinking of sound objects. Of course, you have to have at least some overhead speakers to get any realistic Atmos playback. My Denon X1200W just died and I just bought a cheap Denon 7 channel with Atmos to replace it like a month ago. I wish I had researched this more before because I would definitely sprung for at least a 9 channel amp and added two overhead speakers.

At least high-end 9 and 11 channel Denon AVRs, like the AVR-X4400H and AVR-X6400H, support Atmos 7.1.2 and 7.1.4 respectively. My 7 channel Denon AVR supports Atmos 5.1.2, and I am wondering if I would be better off with that (requiring new ceiling speakers and wiring) or just sticking with my current 7.1 setup and letting Atmos remix everything.

Assuming that something hasn't gone wrong in the ISY. It seems as if the ISY was still configured with a static IP of 192.168.1.161, it would be showing up in your current router. However, if something has been corrupted on your ISY and the static IP setting has changed, it is going to be hard to access it on any router without factory resetting it. That said, anything is worth a try. That said, you could even hook your computer up to a crossover cable directly to the ISY and set your computer to have a static IP address (192.168.1.x) and see if you can access the ISY that way.

Actually, Atmos is different from Dolby Digital and DTS in that it doesn't have a inidividual track per speaker. I.e, in Dolby 7.1, you had 8 tracks of audio, and the processor could mix certain tracks and/or adjusting the timings to match your speaker placement. In Atmos, the movie maker can assign a source location for different sounds, and the Atmos processor decides which speakers to use to create the sound based on your speaker placement and type.

I love the picture with the micrometer in the foreground. I am certain that was a handy tool in your floor replacement project!

Do you have a recent backup? Looks like you are going to need to factory reset your ISY to return it to DHCP. Also, are you saying the ISY shows up in the portal as connected?

I believe you are saying your computer (SNAPWERXEDIT) is 192.168.1.4 (as seen in the ipconfig output) and the ISY is supposed to be at 192.168.1.161. So your setup should work fine EXCEPT your ping was routed to 192.168.1.4 so your local interface is a level above that. Make sure you don't have any VPN connection active (and kill off any VPN software). What about SNAPWERXLAPTOP? Is that a different computer?

What is snapwerx? Try an ipconfig /all and post the results.

Can you ping it?

A NAT router can use any subnet. The private subnets available include all the subnets 192.168.X.X which is 256 class C subnets (subnet mask 255.255.255.0), and 10.X.X.X which is a single class A subnet (subnet mask 255.0.0.0).

I think there is also the question of program model consistency. If all the elements of a scene were in the prescribed state (which the ISY could certainly track), does that mean the scene is "On" according to the programming model. In my mind, the answer is no. The scene is On when the scene is switched On, and the scene is Off when the scene is switched Off. An interim status of the Scene just doesn't really make any sense. But approximating the status of the scene, i.e. having a program that has an if statement that checks the state of each of the devices as paulbates suggest, makes the most sense here to me, from a programming model standpoint. Putting an actual state or trigger even in when the devices come in line with the scene configuration may be convenient, but it breaks the programming model, IMO.