dbwarner5

Changed the log level one more time, and restarted ecobee.. WORKING.. All back again! yeah! Thanks

@bpwwer @JimboAutomates Good news. got them running: -installed 3.0.5.2 -Front end Version matches Version -ALL node servers were not working : Kasa, ecobee, elk, notifications, time date, Weatherflow -One at time, I am changing the log level, stopping the NS, going back to dashboard, waiting, starting it again.. -So far they all are restarting successfully. Log level chosen does seem to matter, just changing it. Only one that seems to still be struggling is Ecobee. It may just need more time? this line seems to be repeating: Thread-37 udi_interface DEBUG Controller:shortPoll: controller:shortPoll: Skipping since discover is still running Will keep an eye on it. Thanks!!

will load it now and let you know. @JimboAutomates @bpwwer

Will try that and let you know. Thanks Sent from my iPhone using Tapatalk

No change. Here is my Elk Node server log fyi. thanks. Also fyi, noticed the versions aren't matching, but understand if that is just a UI issue. Version 3.0.51Status: ConnectedFrontend Version: 3.0.50 ELK_3-24-2022_50156_PM.zip

Several of my node servers are also not working since 3.0.5... will upgrade to 3.0.51 and see if that corrects them.

Interesting discussion re: Alexa. I too have many "motion sensors" initiating voices and have found the following: -After initial setup, nothing will work for about 12-24 hours (maybe less idk), but so trying to "test" one immediately after set up (and for the next subsequent 1-2 hours of frustration), it wont work. But the next day (because I usually quit after 1-2 hours), it works! -Have not had a problem with ISY reboots as far as I know causing Alexa to stop working. Used to use IFTTT for this and some KASA plugs.. not worth the hassle. Direct Alexa integration and node servers are much easier.

Mike, I was in the same boat. The switch to the Elk Node server wasn't too bad. Key was to do a copy / paste of all your programs into a text editor, then its easy to see what you need to fix. I have not found any shortcomings, but have seen other users comment about the lack of elk keypad feedback to the NS, but I didnt use that feature before so its not a problem. My elk integrates garage doors, sprinklers, motion sensors, voice pages etc and it all works great and at times I think it has a faster response to turning on lights via motions sensors than 994i / ISY/ Elk module, probably due to the speed and power of the Polisy.

Just to echo what @MrBill said above, in slightly more words as it IS confusing if you are just catching up to Polisy: ISY is a software package For the last ~12 years, it has run on a piece of hardware called the 994i The Polisy is a new much much faster (with more memory) piece of hardware. The ISY software can run on the Polisy hardware and hence we now have the Isy on Polisy, or IoP. Additionally, the Polisy can also run other software packages called Polyglots. There are currently two different Polyglots that can run on the Polisy: PG2 and PG3 PG2 is being phased out as PG3 continues to reach stability. Currently PG3 is in Alpha stage, hopefully moving to Beta soon. These Polyglots run additional software packages called node servers. node servers allow other third party products, other than Insteon and zwave, to be incorporated into the ISY as "nodes", ie a new switch in your tree, which then allows for monitoring, control and programming of these third party devices via the ISY software. node servers are currently free on PG2. PG3 will allow developers the option to charge for their Node server work in the future. (Lastly, there is an additional Polyglot package called PG Cloud. This was an initial attempt for running Polyglot w/o a Polisy and the software resided on a UDI server and hence the "cloud". This has been discontinued recently due to unresolvable security issues.) In summary, the Polisy hardware is a far superior hardware device compared to the 994i and with the inclusion of Polyglots, expands the utility of the ISY software dramatically with over 100 different node servers currently on PG2 and >60 on PG3. However, please note, the 994i was and is a FANTASTIC piece of hardware that most users would agree, has been ROCK solid for so long and will continue to be for ISY only, but it does not have the ability to take advantage into the future of the third party home automation proliferation. Hope that helps!

Update.. I changed it to remote, and am still getting 0 and 0 for distanced and strikes, all other data is updating as expected. ill give it some more time to see if it changes.

So if I change it to remote, will all the data be from the server or is it a mix of data from local vs the server? But I guess it will match whatever is in the app so it really doesnt matter as that is what I see now whenever I look? thanks

@bpwwer Thanks Bob for moving the thread and the response. Am not sure what would be the best solution. The goal would be for the isy to alert me if lightning is a) within a certain range, b) it is moving closer (done through calculations and variables from the distance data, as it changes). I didnt realize that the lightning data on the app isn't coming directly from just my tempest, but from the server. Is the configuration for the NS to pull from the server vs the local tempest a user choice or a programming choice you would make / modify in the NS? If its the first, then I can play with it to see what makes sense, just let me know how. If its the latter, then that would probably be a large group discussion / consensus based on what others might be doing with the data. I just have never really seen any data on the NS yet, but its winter so we aren't really having any lightning! Thanks again for all you are doing to move Polisy forward!

Have noticed that the NS brings over two pieces of lightning data.... I think its distance and strikes. The tempest has three pieces of data: Last detected in time, distance and # of strikes in the last three hours. The data doesn't seem to match See screen shots below.

Actually, I was able to "Send Settings" from an iPad that was reasonably up to date with my phone and it loaded all my customizations, as well as the old access settings, which then I redid per the above and all is working and I have saved 90%+ of my customizations!! yeah! (after years of using this product, I have quite a few, not just the dashboard, but custom displays, true vs false --> open and closed etc). Thanks for all the help!

YES!! Succes!!. I had tried that the first day, as that is what is in the WIKI, but realize now, I still had the double https:// so it didnt work. Have lost all of my custom settings now, so will try a sync with an iPad that has them and see what happens.

@DennisC Dennis, this is a known issue by Michel. they are looking into it. @Michel Kohanim

UPDATE: SOLVED. SEE BELOW. @MrBill Created new profile. Same result. Gets hung up on Parsing programs for a long time, and then everything is blank. May go back to my original settings as I also have lost a ton of customizing, which I can port over from an iPad (thankfully!), assuming that even if I get this fixed, I have to redo it all. @InsteonNut Wes, any ideas? thanks

@MrBill sorry, I updated my original post as I caught my error.. duplicate of HTTPS:// in the string I pasted alongside the auto HTTPS:// from mobilinc. BUT>>> now when I "tap to Sync with ISY", two odd things happen: 1) I no longer get the option of update or download all, it immediately goes into syncing with ISY 2) It seems to get stuck on "Parsing Program Status" and after ~5 minutes, it stops, but there is literally NOTHING in Mobilinc.. no programs, no devices, its completely empty.

UPDATE: As I was about to hit save, I realized what I did wrong.. I have https:// twice.. OTHERS: When copying the https:// url from the Portal info, per the above directions, be sure to delete the https:// from the string when pasting into mobilinc as it automatically adds that to the string! Whew... so simple. @MrBill Any suggestions as to what I am doing incorrectly? Historically I have always used a DYN server, with port forwarding to Mobilinc and to access my ISY off Property. Based on the above discussion, I have successfully used the ISY finder with the https://my.isy.io/isy.... route to find my ISY. Worked great. However, I cannot get Mobilinc to connect. Here is a screenshot of my settings. The only setting that may be different per the directions per this link https://wiki.universal-devices.com/index.php?title=ISY_Portal_MobiLinc_Configuration, is the Local Port, but that shouldn't matter? I have tried switching Connect Method to HTTPS. I have tried both URLs, with and without /desc at the end. Any ideas what setting I have wrong? Thanks.

had the same problem.. through Terminal I did the following command and all is back to normal sudo shutdown -r now

@btreinders I have had the same issues: -variable change times incorrect. For me it a 5 hour difference. -one nodeserver put back into the same slot, each program had to resaved by “clicking” update to any line and then save.

Totally agree. I know he works long hours and in the >15 years I have been using UD, he has always been involved at this level. Amazing! and one fo the reasons that I never take advantage of his generosity in refunding $15 for an outdated module I purchased for $45 etc...

I have a separate session planned with Michel later today and will show him live....problem is easily reproduced.

@Javi please look at the screen shots attached. The problem is not with UD Mobile as I originally thought. It appears that the ISY is using GMT time for variable changes, which is the time that UD mobile is picking up as you suggested. Look at the two variables: I_Thermostat_ML_Minutes and I_Thermostat_UP_Minutes. These variables increment by 1 every minute based on two programs: Thermostat ML Monitoring and Thermostat UP monitoring. In the screen shots you will see that the programs are running, their times /status is correct. The variables changed, and the times for them changing did update, but are off by 5 hours (early) which my time zone is GMT+5. Let me know if you need more.

No I cant as it has changed since then. I will watch for any future discrepancies and see what I can come up with for you.