asbril

I don't know anything about "Orchestrated" Mobilinc, but I paid for both Mobilinc Pro and Mobilinc X. The latter (X) is a dud, but Pro is useful. However, UDI will soon come out with its own App that I am already trying out. It is excellent and includes most, if not all, features offered by Mobilinc, and maybe even more features. The only reason that I now keep using Mobilinc Pro is that the "home page" gives me an instant view of which lights are ON in my home. I created ISY scenes for each room and then added these scenes to Mobilinc. It shows percentages, so if room X shows a % higher than 0, I click on the scene and then see what lights are ON, and I can then make a change if I want. The coming ISY App does the same, except that it requires a few more clicks. I also use the nice Home Assistant App, but if you wish to use it outside your home, then it requires a $ 5 monthly fee.

You can but they might come back when you synchronize.

I have some 80 Zwave devices . The ISY Inventory nodeserver shows that I have 324 Zwave nodes and 72 Nodeserver nodes, and a total of 460 nodes. I believe that ISY Pro has a limit of 1000 nodes. As such, in theory you should be able to have your 170 devices, but it may depend on how many additional nodes you create (or are generated by your devices).

The new "Favorites" feature make a nice difference and it makes the App very attractive.

While this article is generally off-topic, it makes the point made by @lilyoyo1on the shortage of chips. Suez Canal Is Blocked by Container Ship Causing Huge Traffic Jam - WSJ.pdf

I understand your point, but it is just my personal experience with the limited longevity of PLM's. Unless I'd go entirely Insteon (which is doubtful with my more than 80 Zwave devices), it would mean adding another controller. I am well aware of the great satisfaction and attachment that many here feel about Insteon, and I also understand that for some aspects Insteon may be the better technology. But right now I stick to my setup, but respect all of you and your choices.

The use of a PLM keeps me away from Insteon, though I am still considering it for motion sensors.

Over the years you have (almost?) convinced me that Insteon is a better technology than Zwave, but a combination of both would seem like a win-win. This being said, that interoperability is what ISY offers us. What is happening now to Insteon, whether shortage of chips or bad management, is part of our debate on Insteon vs Zwave. If you have more than one manufacturer, there is a good chance that one of them either has a different chip supplier, or a larger inventory. Reading what you all write about Insteon, I would believe that its future may depend on either a buy-out or a buy-in (cash and management infusion) from a more experienced operator. Maybe Smartlabs should go on Shark Tank........

Maybe time for you and @lilyoyo1to team up and buy out Insteon ? Then rebuild it with a new chip that includes Zwave ????

5.X is the way to go (in fact. 5.3.3) and get a Polisy. Then choose your favorite nodeservers and you will wonder why you waited so long

Can I sell short ?

That is pretty much where I was a few years ago but, with the superb UDI customer support and the extraordinary help from so many in this forum, I am now an "advanced novice". I am also not a programmer and definitely not a smart techie, but I now know how to manage most of my ISY and Polisy needs.

I don't use Insteon and it does not affect me, but I would like to clarify a few things, based on all that has been written on the topic. Existing Insteon devices will continue to be supported. UDI is more than willing to continue the support of new Insteon devices, as long as Smarthome cooperates with UDI, and that cooperation seems to be deficient. Don't blame UDI. Polisy is the Tesla of home automation, allowing the integration of multiple protocols. If not mistaken, Michel also leaves the door open for a nodeserver to be developed that would work, if possible, with new Insteon products. This being said, my understanding is that Insteon is not exactly an active developer of new devices. I don't think that it is right to blame UDI / Polisy for the Insteon issue.

As I mentioned, there is an polyglot upgrade coming up for Polisy and personally I consider it one of the best things since sliced bread. Maybe there are some initial tweaks needed, but I am very happy with Polisy.

A tip for Inovelli users. From time to time, one or another of my Inovelli switches stops working. Initially I took out the switch, do an exclude and include, and I even replaced a switch all together. However, I now know that in most cases the solution is to turn off-and-on the specific circuit breaker and that will do the job.

I have no suggestion (unfortunately) but I believe that the plan is to include remote access for Polisy, in one of the next upgrades. In the meantime, for your next trip, if you have access to your ISY, you could add a Zwave switch to your Polisy and reboot it that way, though I know that power cycling Polisy is not Michel's preferred cup of tea. But it could be a temporary solution. You could also ask your house sitter to power cycle the Polisy (sorry Michel). In fact I added a Zwave switch to my Home Assistant RPi, for just in case.

Thanks Michel for keeping us informed. I look forward testing the alpha package.

Installed with no issues

I have a similar program in our master bathroom and the fan hardly shows a delay. I have some 80 Zwave devices in our home and the only annoying delay that I have is with the motion sensor programs. In these programs it may indeed take 5 to 10 seconds for lights (or Alexa announcement) to react.

That makes a lot of sense. I have ( I deleted it yesterday) the Time-Date nodeserver, which I was not using. I will also delete one of my two weather nodeservers, which I also don't need, and I noticed last night that the Time-Date and the weather nodeservers have a lot of queries. Another maybe related issue was that last night my wake-up program (set at 6:40 am) and that has been working fine for a long time, suddenly ran at 12:07 am, generating understandable unhappiness of my wife ?. Something may have been reset when I re-installed the Holidays Google nodeserver (which is part of the wake-up program) and hopefully I was able to resolve it. I will send you the error log, Thanks as always

Thanks Michel, I can indeed see Queue Full in the error log, Should I send you a copy of the error log ? Maybe the issue was resolved when I re-installed the nodeserver and rebooted the ISY ?

After re-installing the GH nodeserver, I still had the issue of the Tomorrow Node showing True when it should have been Today. I rebooted the ISY and that resolved the issue. It has now been running ok for 36 hours. If my issues occur again, I will start with a ISY reboot and, if that does not fully resolve the issues, then remove and re-install this great nodeserver.

As I have mentioned before, I love this nodeserver and I have 8 specific calendars for this purpose. It has always worked without failing until a few days ago, when some nodes would show "false" even though there was an all-day event in the calendar. At first I restarted the nodeserver in the Polisy Dashboard and that worked once and then not the next time. And then I restarted Polisy in System. That also worked once and then not again the next time. I now removed the Google Holidays nodeserver and re-installed it and hopefully it will be as reliable as before. p..s. I forgot to mention that, before removing and re-installing the GH nodeserver, in one instance the node showed on "Tomorrow" while the event was clearly "Today". And I had double-checked the calendar.

Last week I got that Quad Wallmote and I found it very complicated to use and returned it to Amazon.

Mobilinc X exists already. However, notwithstanding Wes' good work, I personally have gone back to Mobilinc Pro as it better serves my needs.