MWareman

Yes. The portal integration module for ISY. It's $49 for 2 years (a subscription). See: http://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions You've done step 1 of setup before establishing the prerequisites.

Which Portal did you buy? 'Mobilinc' or 'ISY Portal'? If the latter, you need to create an account at my.ISY.io and link your ISY (see http://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions). Then, link your Amazon account. Instructions for this are at the Wiki here: http://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration If you haven't purchased it yet - the ISY Portal is $49 for 2 years. You'll need to purchase that to be able to add an ISY to your portal account.

Put your 'Then' into a separate program (with no 'If' clause), and change the original program to call the new program instead of directly executing the commands.

As soon as the MS changes to not violated, the 'If' changes to false - cancelling your wait and off statement.

Yes. Why would you want to bring a member of a scene such as this to 100%? If a members scene on level is 50% - your intent for that scene is to have that load at 50% - setting it's brightness to a level with relation to other loads in the scene - to create a scene. If you want to set the load to 100% outside of your scene then command the load directly - or a separate scene where the devices scene on level is 100%. Set the scene to 100% - or set it on. For scenes with multiple loads potentially at differing on levels, then what's important to a dimmed scene is that the relationship between the loads is preserved. For instance, if it takes 5 seconds to dim 50%, and your scene members in a scene one scene have on levels of 50% and another 100%, what happens when you hold a scene controller paddle for 5 seconds? You get the first scene member at 25% and the second at 50%. That's the expectation for asking for a scene to be on at 50% - each member at 50% of its default on level.

31% of whatever the scene on level for the device is..... That would be the naturally expected result.

To confirm the network link, directly under the network connection there are two green LEDs. The one to the left is 'Link', the one to the right is 'Activity' (they are not labeled). Are either lit? (Especially link) Also, if you want to get the console connected, you'll need a mini-usb cable. You connect the 'Monitor' connection to your PC and install the serial port driver. Then use a program like PuTTY to connect to the virtual COM port.

French is fine (for Windows Admin). Over the years, I've had to get used to it. This confirms the 00:26:B9 MAC is your PC, and its a DHCP assigned address of 192.168.1.103. Let's try power cycling the ISY and refreshing the 'LAN Computers' screen to see if a device with a MAC starting with 00:21:B9 shows up. If it dosn't, then either the ISY is statically assigned an address that's inconsistent with the 192.168.1.0/24 network your router is on (unlikely, since you said you reset ISY to defaults). Since the ISY is indicating a network link, the only other possibility is a bad network port on your switch. You might have to get a USB cable to connect the ISY console to your windows system. If you do this, we can get details of the network config, as well as confirm the ISY itself is functioning.

Also, as above the Wiki say that UDIs MAC addresses behind 00:21:B9. I don't see that yet in the screenshots provided. If you power cycle ISY then check the routers 'LAN Computers' list see if it shows up. It may only be there for a couple of minutes after rebooting ISY.

So, in one screenshot it's indicated that your Windows machine has 192.168.1.103, in another the MAC address associated with ISY shows with the same IP. It can happen that you have two machines with the same IP - and if that happens generally one will be inaccessible. For instance, if ISY got 192.168.1.103 from DHCP, but you set your Windows PC statically to 192.168.1.103 as well. ISY would be inaccessible in this case. Also, the other way around. Or if both are statically set to the same. I'd like to see the result of 'ipconfig /all' on your Windows PC to see how it's configured - and we can go from there.

Gen5 requires a different Sigma chip, so a dongle replacement. However, most Gen5 devices work just fine - including the Aeon Multisensor..

As above, the PRO upgrade is software only. Add it as a 'module' and its effective immediately you install it.

You could probably put a 1-wire sensor up to a Rpi with a wifi adapter in a nice case for about the same money as the 2441ZTH.

224. Addresses are multicast addresses. Typically not assigned to devices. Does your router have a web page where you can look at the dhcp assignments? Edit: Now I'm at a real keyboard.... 'arp -a' only displays the ARP cache for devices your computer has successfully communicated with. However, this is useful because of your statement that you only have a router, a tablet, your computer and the ISY. Your routers IP address is 192.168.1.1 Your computers address is 192.168.1.103 Chances are your DHCP range starts at 192.168.1.100 and goes up from there. So, try: ping 192.168.1.100 ping 192.168.1.101 ping 192.168.1.102 then arp -a and post the response to all.... one should be the ISY, another your tablet (may be sleeping) - and the third will not respond. The 'arp -a' will then list the mac addresses, and we'll be able to tell which one is your ISY. Michael.

Do that on the router. It won't show up on your PC unless you have successfully communicated with it first. The browser discovery has long since stopped working - browsers simply don't work with Java anymore.

If you end up with power only light, then ISY has successfully got an IP address from your DHCP server. You just need to find out what it is from your DHCP server logs... http://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs When you do - set up a DCHP reservation in your DHCP server so it dosnt change again!

Also check your dhcp logs while rebooting ISY. You should see it request an IP, and the log will tell you the IP to use. Check the link light on the switch the ISY is connected to. Lit? If not, could be the cable. The lights on ISY will also give clues. After powering on, let us know what the ISY lights are doing.

I'm having difficulty getting the etcher to evenly etch. Some areas are deeper than others. I thought this was to do with uneven coating of mask (I was using Liquimask) - but @Xathros sent me some laser tape to try - and I'm having the same problem. (THANK YOU Xathros!! I very much appreciate it). I've been busy with other projects recently, so have not been able to do more burns yet. My feeling now is I need a fan to clear smoke as the burn is happening - I think the smoke is affecting the laser intensity. Not sure yet... I was 'wafting' it for my tests, but I'm not sure it was enough.

Try putting the Fanlink as a responder into 4 seperate scenes - one each for high, medium, low and off. On the portal, set the spoken name on each of the 4 scenes scene respectively.

ISY also does not implement supervising sensors - to ensure they are not being jammed or otherwise disabled. Elk is the way to go if you want to use alarm zones in your automation, since it has a native, supported plugin on the ISY. However, if your willing to run middleware you can also integrate any DSC based system.

Oh, and yes. Turn off 'trigger reverse'. It only reverses a trigger signal - not the value when queried. It will cause you issues! If you need to reverse the signal - rewire your sensor. Switch it from NO to NC (or vice versa)

I just want to clarify... Will not go down - or closes and then reopens... Two different troubleshooting paths. If it's closing then reopening, you almost certainly have a program triggering on the IOLinc input that you are flipping a scene (to light a KPL button) where the IOLinc relay is a member. This will trigger every time the door is closed and reopened the door. To troubleshoot, try disabling these programs and reenabling your IOLinc...

What OS are you accessing your ISY from? There is a transition underway away from ciphers like SSL2 and SSL3 in favor of TLS1.0, 1.1 and 1.2. Some older OSes have challenges accessing secure sites where the older ciphers are not supported.

The network module functionality included with 4.4.6 and the Portal does not show as a purchased module. It should automatically show up. More than likely you have upgraded the ISY, but not cleared your Java cache, so are still using an older GUI. Can you post your versions from the about dialog?

That was about the time that I significantly expanded and reworded the page to add details of network rule substitution and adding details of the device nodes.... It also shows the URL to call to get a specific devices nodes - so you can confirm what nodes are provided by any given device. I suspect that this particular device isn't providing humidity data - causing the substitution to fail.