Michel Kohanim

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

Michael, Precisely. James, Perhaps if you can answer my questions instead of dissertations on the history and future of technology and how it should be implemented in ISY, we might be able to find a solution. Please respond with yes/no: 1. Is the source of events ISY (yes/no)? 2. Is it all the events from ISY (yes/no)? 3. If yes to #2, is it the same format in xml (yes/no)? 4. If no to #2, then what? With kind regards, Michel

I think we are going in circles. WHAT are we notifying and WHAT is the source thereof? If the source is ISY, then the only ways to have ISY notify something is either by subscription or the Network Module. With kind regards, Michel

Dear ISY Portal Subscribers, ISY Portal is scheduled for a minor maintenance release on Sunday 10/09/2016 from 5:00 AM till 6:00 AM PDT. Unless there's a catastrophic incident, the only noticeable impact to end users would be if they have active client subscriptions (such as Admin Console). Active subscriptions will drop. MobiLinc users will not notice this issue as the app will re=subscribe when it sees that the existing subscription is dropped. We do apologize for any inconvenience. With kind regards, Michel

Hi Gary, That does not answer the question of "what" from ISY to ISY Portal. Anything that ISY needs to publish to anything else requires subscription. With kind regards, Michel

Hi James, If no subscription from ISY Portal to ISY, then what is ISY Portal notifying? With kind regards, Michel

Hi James, ISY Portal subscribes to ISY IF AND ONLY IF a client subscribes (such as Agave). There are no mechanisms in ISY Portal to subscribe on its own. Furthermore, with your description, ISY Portal will need to keep checking for subscriptions and make sure they are maintained, re-subscribe if they are severed for any reasons, and finally there's no good method of removing them in case someone decides not to use them any more. We currently have this issue with Echo: dangling accounts which Echo thinks should exist but they that are not tied to any ISYs in the Portal. We had to spend numerous hours of maintenance and development just to clean those up. In short, what you are suggesting will NOT work without massive changes and major overhead both administratively (making sure accounts are still associated with devices) and performance wise. With kind regards, Michel

Michael, James, Thank you. What you are describing will require the portal to have a) an always on subscription to ISY and monitor the events and then based on some filters, send a push notification to another device. In short, there needs to be a mini ISY in the portal which would defeat the purpose not being cloud based. Perhaps a better solution would be to have another construct in ISY Programs that calls an event service (based on some conditions) and passes some relevant information to the portal through the portal socket (not web). The question is what type of parameters do we need in the portal to make it secure, reliable, and extensible. With kind regards, Michel

Hi jam583, The PLM is definitely dead. The first thing to do would be to get a new PLM. With kind regards, Michel

Hi jam583, What's the status of lights on the front of the unit? Anything blinking incessantly? With kind regards, Michel

Hi Alex, We will definitely investigate. With kind regards, Michel

Hello all, The only reason is our aversion to putting too much logic in the cloud. Apart from IFTTT and Geo Fencing/Push Notifications, what other services should we put in the cloud? Of course, with 5.0.x, putting services in the cloud and having them be represented as nodes in ISY is quite easy. With kind regards, Michel

Hi jam583, If you have a blinking error light, please review: http://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs.2FLights With kind regards, Michel