rlebel

Sent, thanks

I updated to 3.2.27. This morning I got the same problem again.

At random times I get a sequence of fail/disconnect/connect notifications. Happens roughly once a day. It has been happening for a long time, since it reconnects immediately it is just an annoyance not an operational issue.

_5 and my DST checkbox is still set and grayed out. Sunrise/set displayed correctly.

It would be nice if the About box gave the _x suffix, mine just says 5.0.7.

Today mine are too! They weren't yesterday. But the greyed out DST check is still incorrectly checked.

I think that rebooting (in my case after doing an update packages) has fixed this for most people. The display problem of sunrise/sunset is the remaining bug but that doesn't impact proper program operation since it is only the UI.

I did an update packages and reboot and my programs seem to have been appropriately reenabled. However, sunrise and sunset and the DST checkbox are still wrong.

All of my programs disabled also - and by looking at when variables had last been updated I see it happened exactly at the DST change. I don't have disabled programs labeled in any special way so enabling is going to be a real PITA. I also see that DST is still checked on the configuration screen and sunrise and sunset are an hour earlier than they should be!!!

Thanks. I suspect that my problem was that I forgot to buy a perpetual license!! Purchased now, will see if I have a future problem!

Recently I found that my EISY was not getting any updates from my wireless tags. I checked that the tag manager and polisy were running then I restarted the node server manually and all was well. My question is can I automate this? I could set up a program that would detect if there had been no updates for a while but I don't see that I have the ability to restart the node server. The device shows the ability to reboot the tag manager but not the node server. Ideas? Thanks

I too had a strange result disabling WiFi, your hint saved me a lot of trouble! The eisy is now hard wired in the equipment closet. Enjoy the lake house, I seem to have everything working now.

The loop seems to work, so far I am not using any PIR so a one minute update of sensors is fine. If I went to a hardwire link for my eisy I guess it would work. I have to disable the wifi? When might you get around to fixing this?

Yeah looks like you are right about that. I guess I could set up a program to repeatedly send queries.

So I went to polyglot 2, got a new oauth2_code then cut and pasted that into PG3x and at first no luck but then suddenly I did a discover and all the nodes popped up! Thanks all!

So I am trying to get the tag manager working again with my new eisy (replacing 994). Polyglot 3x seems to be connected to the eisy correctly and I have loaded a trial wireless tag v3 but when I click on the authorize link I first get the permission page from the wireless tag site (although it says V2 not V3) but when I click grant access it attempts to access a bogus IP 172.26.18.2 and eventually times out without getting the oauth2_code. Help?

Thanks for the suggestions, however I used the ISY Portal link for MobiLinc and it seems to work fine. I guess I won't get any push notifications that way but for my use, setting variables based on the location of my and my wife's phones, I don't see any downside.

So sorry if this is addressed elsewhere: I've been using MobiLinc for location services e.g. to turn things on when I come home. It seems MobiLinc doesn't support eisy so what are people using for location services?

So I knew from page 2 that I needed the DB9 to USB adapter - Brian you told me what I needed to know - and being a hoarder I went and opened that 10 year old box and found it! Thanks!

Okay so I have the PLM with the ethernet-like serial connector, not DB9. How do I connect to the eisy?

How do I find out what Z wave board version I have? The About box says Z-Wave (21010), the Z wave dropdown doesn't seem to have anything useful, just the software version 4.55.00

Stuviews thanks for the hints but maybe can clarify so I don't have to experiment: why add both "the device" and a scene to the group? For example if I have a scene that I want to be able to set to a level can I just add the scene to the group? Or do I also have to add a device (perhaps one from the scene) in order to be able to use this workaround?

Set it for fixed for now, will see how that works. http://forum.universal-devices.com/topic/12762-isy994i-compatibility-with-twelve-somfy-motorized-shades/?p=115423

Now that I finally have my Somfy shades linked to my ISY I was wondering how best to automatically lower them based on sun angle? The idea is to have them come down just before the sun starts directly coming in to the room, which of course varies with the time of year, without having a physical sun sensor (yes of course I also need to know if it is cloudy, but the weather station light sensor can tell me that, and besides I'm in Santa Monica it is is always sunny LOL). I don't think a fixed number of hours before/after sunrise or sunset will be correct. Thanks

Okay, for several years I have had my Somfy shades isolated from my ISY due to disgust at the high costs and the kludgey nature of what was needed to make the hook up. I finally gave in and it was a bit easier than I feared, so here are some notes of what I did: I bought the "SOMFY UNIVERSAL RTS INTERFACE 16 channel URTSi II 1810872" from a supplier on EBay for $266 plus tax; the "Global Cache Flex Link Serial Cable (RS232)" for $24 and the "Global Cache iTach Flex Wi-Fi" for $92 from suppliers on Amazon. An RJ45 to DB9 adaptor was included with the RTS Interface; the only additional hardware I needed was a spare RJ45 jumper cable to hook up the RS232 (yes, two cables and one adaptor to hook up the 1960s era RS232 interface). I also purchased the ISY network module for $49. I then linked the iTach Flex to my home wireless network. Note that I used DHCP to assign an address but then set up my router to fix that address for the iTach, because you don't want it to change later, since the ISY needs to find it. I happened to pick 10.0.1.29, your LAN might be set up differently. On an Airport this is called a DHCP Reservation. Then I plugged in the iTach serial cable to the Flex and from my browser at http://10.0.1.29 I set up the iTach serial cable to 9600 baud, no parity, 8 bits and one stop bit. Crossover is set to False. The RTS Interface has a rotary switch to select the address or channel of the box; unless you have multiple RTS Interface boxes I think you should just set this to 1 and forget it. You then can link each of your shades, in sequence, to the Interface by first pressing the program button on an already linked remote, observe that the shade jogs, then press the program button on the Interface box and see the shade jog again. Record the order of programming because the motors will then be numbered 1, 2 etc by the order of programming. All that is left to do now is to go into the ISY admin console and create these strange little “network resouces”. For example I created one called “shades down” that is a TCP resource for host 10.0.1.29, port 4999. The body is 0101D\r\n0102D\r\n which puts down my shades 1 and 2; the \r\n is return, line feed characters. You then use the network resources in your programs to do what ever you like. Hope someone finds this helpful!