Michel Kohanim

Hi branko, If you are familiar with Raspberry Pi development, then all you need is a client that subscribes to ISY and then the rest you can do in RPi. Alternatively, you can have a program that polls ISY frequently and then logs the status of devices. Here's the link to our WSDK: https://www.universal-devices.com/isy-developers/ With kind regards, Michel

Hi elvisimprsntr, We have not tested either of these bridges, but from taking a guess at the command classes it uses, it is likely that we do support it . With kind regards, Michel

Hi javic, Thanks so very much for the details. Please note that ISY will retry incessantly ... so, the question is whether or not the router provided the correct DNS server once ISY booted up. If not, you might want to consider a static address configuration BUT note that if you ever change your router, you might have to factory reset your ISY and restore from your backup. With kind regards, Michel

Hello all, Just to close the loop, I spoke with Branko and it's all setup. I simply converted network module to ISY Portal module and everything else worked. With kind regards, Michel

Hi Larry, Please send your UUID, time of occurrence, and the link to this post to support@universal-devices.com. With kind regards, Michel

Hi Mitch, Please use the icon on your desktop. Here are the instructions for doing so: http://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Icon_on_Your_Desktop With kind regards, Michel

Hi andrew77, Yes, and you can ignore it. With kind regards, Michel

Hi andrew77, NO, please do NOT restore PLM. It seems that your PLM has died. With kind regards, Michel

Hi Scottmichaelj I am not sure what I'll be posting to the Wiki and where to put it. I can certainly put a link in the Wiki to point back to this post. With kind regards, Michel

Hello all, This is the link for security configuration for the dashboard: http://wiki.universal-devices.com/index.php?title=Main_Page#Network_Security The best place to start is error log. In 99.9% of the cases, the issue is either DNS (not finding my.isy.io) or router configuration not letting ISY get out to the Internet. If you wish, you can send your error log to support@universal-devices.com and we can take a look. With kind regards, Michel

Hi starmanj, Http://isy.universal-devices.com/5.0.6/dashboard.jnlp With kind regards, Michel

Hi Stu, Thanks so very much for the feedback. Would it be possible to send your UUID and the time of the occurrence the next time around? We'll definitely look at the logs to see what's going on since it should NOT happen unless the actual device is not responding. As part of the last maintenance release, Benoit added a sophisticated logging mechanism to query all the logs (from proxy, dispatcher, web, subscription server) so we'll be in a much better position to track any bugs. With kind regards, Michel

Hi robin71, Not responding means that ISY cannot communicate with that device. Before doing anything else, please check your ISY logs and make sure you do not see ERR 1 for that device. Rediscovery is not necessary as long as your device names have not changed. With kind regards, Michel

Hi steve9f, Can you please let me know your ISY's firmware version? With kind regards, Michel

Dear ISY Portal Subscribers, ISY Portal is scheduled for a minor maintenance release on Sunday 10/16/2016 from 5:00 AM till 6:00 AM PDT. We are adding a load balancer for the web servers and, unless there's a catastrophic incident, there should either be very minimal interruption on the access to the Portal/Echo and most probably none at all. We do apologize for any inconvenience. With kind regards, Michel

Hello everyone, Thanks for all the feedback and heated discussions. From UDI perspective: 1. Having a filter on ISY Portal is not a good idea because a) we will need more subscription servers inefficient use of bandwidth for things that are meaningless (such as those send on Event Viewer Level 3 - debugging information) and c) events will be portal dependent 2. Changing the packets to use binary is not a good idea since it does not follow any standards (either internally or externally) and it's not backward compatible. We will then have to have glue code that decides to interpret things based on the URL. Either using XML or transforming to JSON is a much better approach We do know that we can use programs do send notifications (including push). The question is if we can make this process (having programs that send push notification) easier with some APIs, would that suffice? With kind regards, Michel

Hi smokegrub, What I am trying to say is this: If you do NOT use the Add button to add your local ISYs, then ISY Finder will try to find them by searching the network. This means that the top entries are ALWAYS those that ISY finds automatically on the network. This also means that when you are NOT local, those will NOT show up (only the remote ones that you created using the Add button show up). Does this make sense? With kind regards, Michel

Hi smokegrub, Sincere apologies for not comprehending your question. I think I now understand and please correct me if I am wrong: In ISY Finder, for each ISY, you have two entries: 1. Local IP address 2. Away IP address Since both point to the same ISY, they are named the same and thus you would not know which one is local and which one is remote (away). Is this correct? If so, can you please let me know whether or not you actually added an entry for your local ISYs (when you are local) or is that that the ISY Finder automatically finds them when you are local? With kind regards, Michel

Hi jtara92101, Stopped using = threw away and went with another service provider and/or phone. Hi mwester, I totally agree with you. It makes no sense to send all the messages and events through push notification. We need to figure out a way to filter things on ISY WHILE not making it too cumbersome. Hi James, Do you happen to have a set of use cases that require push notification? May be something like: 1. A checkbox next to a device so that change of status for the device is published 2. A checkbox next to variables so that the change of status for the variable is published - What else? With kind regards, Michel

Hi jam583, Just to be clear: you could login to the Admin Console BEFORE doing a Restore Modem but you can no longer access it after? If you are still having issues, it would be best to submit a ticket (links below). With kind regards, Michel

Hi smokegrub, The name comes from the top most node below the Network (in the Admin Console device tree). The default is ISY. So, you can definitely rename that node, remove that entry from ISY Finder, and then add it back in. ISY Finder will take the new name and includes it in the list. With kind regards, Michel

Hi rafarataneneces, Please send your error log to support@universal-devices.com. We have recently added more servers to the portal and, if you have configured your ISY with a static IP address, it might be related to DNS queries. With kind regards, Michel

Hi James, Thank you. In this case we have to figure out a way to have the ISY Portal subscribe to ISY. The only remaining question is whether or not there are any services that we can use to figure out whether or not someone has stopped using a phone or service. Is there such a service? With kind regards, Michel

Gary, Of course, you can use the Network Module to send data to ISY Portal. That's what we do with IFTTT. What's not being answered is WHAT is being sent to ISY Portal and what's being sent to FCM. With kind regards, Michel

Hi arzoo, Please send your error log to support@universal-devices.com. With kind regards, Michel