Michel Kohanim

Hello apostolakisl, Barometer should be fixed by now. Please check again and let me know. The label was a huge task in and of itself. The problem is that the forecast is not really for today. It's for 7am till 7am next day and updated every hour so there's an overlap with forecast for tomorrow at some point after 12:00am today. This is how meteorologists decided what 24 hour forecast should mean. With kind regards, Michel

wrj0, Please send your station ID along with a link to this topic to support@universal-devices.com. With kind regards, Michel

Hello jmed999, This is basically forecast for today which is updated every hour. It's usually from 7:00 AM for the day. There are there concepts Coverage ... things such as chance of, isolated, etc. Intensity ... the intensity of the next condition such as heavy Condition ... such as rain, snow, etc. You can see a list for all of these under programs. Yes. The available listings is under Coverage in programs Please send your station ID to support@universal-devices.com With kind regards, Michel

Hi jmed999, Unfortunately not. This said, we shall explore some alternatives. With kind regards, Michel

jmed999, Thanks so very much for all the details which were 100% accurate. We still need to update the Wiki. With kind regards, Michel

Hi gviliunas, This is a special PLM firmware and not one sold through SmartHome. If you don't have it, please contact support@universal-devices.com and we'll arrange it for you. With kind regards, Michel

Hello jrd, Please do make sure you have 4.2.3 installed AND that your UI is 4.2.3 (Help | About). Here's the link to 4.2.3: viewtopic.php?f=25&t=14926 With kind regards, Michel

Hello smokegrub, Please submit a ticket (links below) and we would be delighted to remote in and figure it out. With kind regards, Michel

Hello smokegrub, No, the firmware should not matter. As long as you have 3.3.10 and below, we have done everything in our power to make sure the new Admin Console versions are backward compatible. Can you access your remote ISY by typing its URL in a browser? With kind regards, Michel

Hi Rick, If you are still having problems please do not hesitate to contact our tech support team (links below) and we'd be delighted to help you out. With kind regards, Michel

Hi remedy1234, Please contact our support (links below) so that we can hook you up with our SmartHome reps for an updated version of PLM for you which specifically addresses the All on issue. With kind regards, Michel

Hi scottbasilius, Yes, but there's a bug which is fixed in 4.2.4 to be out hopefully by tomorrow. With kind regards, Michel

Hi Apogee50, Not the remotes but I am using an IOLinc: 1. The relay replaces the button on the wall 2. The sensor is attached to the garage door so that you would know when the door is left open Here's a good start: http://wiki.universal-devices.com/index ... e_Door_Kit With kind regards, Michel

Hi johnnyt, The only way we can figure out whether the issue is related to processing power or a simple timeout, it would be best to turn debugging on (telnet, DON) and then look at the error log. This way you can see all the requests that are hitting ISY including their IP addresses. We had a case last night where ISY was quite sluggish. It turned out that IRule was bombarding ISY with /rest/node requests (like 10 every second) but without having the correct credentials. With kind regards, Michel

Hi htjunkie, In order for us to better serve you, please do be kind enough to submit a ticket. With kind regards, Michel

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