Michel Kohanim

@wharris, Thank you! With kind regards, Michel

@Blackbird, Definitely coming and we are working on it. This said, production ready fully loaded ISYs will not be ready for quite a while. With kind regards, Michel

@johnnyt, 1. Probably 5-10 programs (not percentage) that use old method of invoking commands. But, ALL your nodelink variables must be replaced with the actual nodes 2. Adjust scene 3. Yes, you will see it in Yellow in program summary tab. Then, when you edit, ISY will give you hints in the comment section With kind regards, Michel

@fahrer16, Thank you. @bmercier has already developed a node.js based Polyglot. We are making sure that it will also work in Polyglot cloud. With kind regards, Michel

@johnnyt, Since you have no Z-Wave, the only manual intervention is to go to your Programs tab and make sure everything is migrated to the new structure. Those with issues, are marked with 'not saved' or 'not loaded' in yellow. Fix those, and you'll be done. With regards to performance, not sure things will be better but with 5.0.x, DSC and Ven link devices can be ported to node servers and thus they won't need to keep polling to or posting variables to ISY. They become like first class citizens nodes in ISY. You might want to verify with @io_guy. With kind regards, Michel

@mwester, We are working on something that, although not full editor, will make all these types of activities a lot easier and will not require firmware changes. With kind regards, Michel

@TexMike, Yes, I have. I'll keep you posted as soon as I hear back. With kind regards, Michel

@ixlr8, Yes. Put the button as a responder in a scene and then turn on/off the scene. With kind regards, Michel

@Blackbird, Please take a look at https://www.universal-devices.com/resources/ With kind regards, Michel

@sakiman, The reason is that your router is no longer port forwarding to your ISY. Instead, it's just presenting the router login which is NOT good. Furthermore, I suspect the router will not allow you to use the default 443 port. You will need to forward to a different port. Here are some instructions. With kind regards, Michel

Hello all, Just for the sake of transparency, during this beta cycle we were overwhelmed with many Z-Wave devices with customized features, devices that did not follow the spec, and association groups that were mismanaged by the manufacturer (thus scenes would not automatically work). In short, for every reported device/issue combination, we had to make modifications for that specific device in the firmware (and thus another firmware release). The list is just too long. So, since 5.0.14 seems to be very stable, we started working on a dynamic configuration feature for some of these issues so that we won't need a firmware update for every permutation of device/feature nonsense. Very much like node servers. This has taken longer than expected but, if it works, then it'll make things much easier for us all. In short, that's where we are right now and I do appreciate your patience. For those on the fence, if you do not need 5.0.x features, you don't have to migrate. If you do, then you MUST go through the migration process REGARDLESS of official vs. beta. With kind regards, Michel

@apostolakisl, Can you please send your UUID to support@universal-devices.com and include this link ? With kind regards, Michel

@apostolakisl, Thanks so very much for the update. We have submitted a ticket to Google. Haven't heard back. With kind regards, Michel

@apostolakisl, Do you get Permission Denied errors? We have already opened a support ticket with Google. Something quite screwy is going on there. With kind regards, Michel

@hbskisurf, Please submit a ticket and include your error log. With kind regards, Michel

@KSchex, Thank you. Is it correct to say that the issue is communications related? If so, perhaps adding a range extender is a good idea followed by a heal (especially since the issue seems to revolve around battery operated devices). @rccoleman, unlike INSTEON, Z-Wave commands are short but numerous. So, there will be cases when the queue is large enough so that ISY will have to throttle everything. It's 100% normal as long as the commands in the queue are eventually processed. With kind regards, Michel

Hi Sakiman, What do you get if you use a regular browser and go to https://97.102.166.197? With kind regards, Michel

@carealtor, If Control 'button x' is switched on Then Run whatever program With kind regards, Michel

@hbskisurf, Are you sure you don't have MobiLinc Connect Module (Help | About)? With kind regards, Michel

@buzzhazzard, Please submit a ticket with your UUID. With kind regards, Michel

@KSchex, Please be more specific on the "hung". Error log would be great. With kind regards, Michel

@simplextech, Thank you for asking. We currently don't have any requirements except for energy saving/management/charging vs. discharging. A few folks started working on Tesla Cockpit integration but I am not sure where that is at the moment either. With kind regards, Michel

@buzzhazzard, In 99.9% of the cases, this error indicates that the Google account you are using (linked to ISY) does not have permission to access the Google Home device. The first thing you should do is to use this Google account and see whether or not you can control your Google Home device through the Google Home app. With kind regards, Michel

@bdw72, This is mostly firewall related. With kind regards, Michel

@simplextech, Thanks so very much for the explanation. Two questions: 1. By hardware, what do you mean? Where does the hardware go? How much is it? 2. Do you have anything for Tesla? Such as state of charge, when to charge, nearest charging station, etc.? With kind regards, Michel