Michel Kohanim

Hello eataft, Thanks so very much for the details and thanks to LeeG for a great response. We have dabbled with this situation multiple times and in all cases sending a group command actually made things much worse: not only devices that didn't respond before didn't respond using scene commands but also we ran into major delays causing all sorts of issues with ISY programs such as collisions. The reason the PLM is not as reliable as other devices is because of the location of the PLM. The first thing I suggest is to move the PLM to a different location. In short, commands from the PLM must be as reliable as others. With kind regards, Michel

Hi trainsare, By portal I mean MobiLinc Connect. I strongly recommend upgrading to 4.2.2 OR 4.2.3 to be out by Monday or Tuesday. With kind regards, Michel

Hi Princerichy, You need to put those buttons inside a scene (as responder) and then activate the scene. With kind regards, Michel

Hi trainsare, This basically means that the portal closed the connection without sending a TCP close. What's your firmware version and has anything changed in your network and/or credentials for the portal? With kind regards, Michel

Hello Seb50, If you are still having issues, please do not hesitate to contact our tech support (links below). With kind regards, Michel

Hi fasttimes, Unfortunately I do not know what Misterhouse is or does. ISY can create cross linkages between devices. This said, those cross linkages are part of a scene which can be controlled by ISY and thus there will be links to the PLM for each device in each scene. With kind regards, Michel

Hi jimsearle, If you are trying to have the camera call ISY, the camera will need to include the HTTP Authentication header otherwise ISY will refuse it. The format of the Authorization header is: Authorization: Basic Base64(userid:password) Where, base64 converts the string representation of userid followed by ‘:’ and followed by the password. As an example, the Authorization header for userid=admin , password= admin is: Base64(admin:admin)ïƒ YWRtaW46YWRtaW4= Therefore the Authorization header shall be: Authorization: Basic YWRtaW46YWRtaW4= With kind regards, Michel

Hi Seb50, I am so very sorry to hear. It seems that your new router is not on the same network as the static IP address configured on your ISY. IF AND ONLY IF you have a good backup, factory reset your ISY (http://wiki.universal-devices.com/index ... ur_ISY-99i), restore your backup, and once prompted about the network configuration, please choose DHCP. With kind regards, Michel

Hello ESB, I am so very sorry for the inconvenience. First of all, you will need to use the following URL for your 99: http://isy.universal-devices.com/994i/4.2.2/admin.jnlp .. this will fix the Java issue. As far as certificates, unfortunately the certificates expired for 99 and since 99 has been discontinued, we did not renew them. What you can do is to revert to the default certificate: 1. Telnet to ISY 2. Login 3. Type the following at the prompt RF /CONF/UD.DCF With kind regards, Michel

Hi seendbl, No, not at all. It should work on all. The reason you are getting those warnings is because the certificate's CN (common name) is not the same as the URL for ISY or that the certificate is not signed by a certificate authority. With kind regards, Michel

Hi eyeandy, Precisely and hopefully very soon. With kind regards, Michel

Hi seendbl, It would be very difficult without having a Certificate Authority (such as verisign) signed certificate. In short, you have to install a certificate into ISY: http://www.universal-devices.com/docs/I ... 0Guide.pdf Once that's done, you need to import ISY's certificate into the trusted store for your browser. For instance, for IE: http://wiki.universal-devices.com/index ... te_Install With kind regards, Michel

Hi Jack, We were not/are not included in the partnership. With kind regards, Michel

Hi dano, Never heard back from them. I am sorry. With kind regards, Michel

Hi Jeff, Please clear your Java cache and go to http://isy.universal-devices.com/994i/4.2.2/admin.jnlp . With kind regards, Michel

Hi tim2u, Thanks so very much for the feedback. Unfortunately we do not yet have any plans for supporting Windows 8 mobile above and beyond our default HTML interface which works on all Mobile platforms. With kind regards, Michel

Hi Barry, This is pretty generic since it implies that somehow ISY should be able to parse any feedback/payload from any server. Unfortunately, I am not sure if anything can do such a feat without some type of meta data. With kind regards, Michel

Hi Xathros, Not natively because sessions mean different things to different platforms. This said, once we have variables incorporated into the network module, hopefully you can assign a variable to a session and then use it in other resources. This said, the main problem becomes hydration: who's going to get the first session and would it possible invalidate other sessions? With kind regards, Michel

Hi huffmd1, I am so very sorry but as I indicated on the email: a. Their API requires session tokens which requires conversation for each session. ISY does not currently support this 2. They use XMPP SASL for authentication, this is not what ISY supports With kind regards, Michel

Hi snowtech, We are working on it as we speak. With kind regards, Michel

Hi huffmd1, We are working on it as we speak. So, hopefully we'll have beta in 4.2.3 by end of next week (again, hopefully). With kind regards, Michel

Hi Xathros, Yes, 100% correct. With kind regards, Michel

Hi Guys, If you do know the command set/APIs, then yes of course. All you need is the Network Module and then create your own resources which can then be used in programs. Here are some examples: http://wiki.universal-devices.com/index ... _Resources With kind regards, Michel

Hi jellis, I am so very sorry to hear. Unfortunately this is a known and intermittent issue with 4.2.2 incorrectly caching DNS results. It's already fixed in 4.2.3 which should be out by the weekend. With kind regards, Michel

Hi Leslie, I also got your email and Steve shall be contacting you shortly to help. Thanks everyone! With kind regards, Michel