dbwarner5

@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.

agree with the time stamp. I have added that as well and switched to pushover for the notification, but it still doesn't explain the time stamp of the UD mobile variable. The text messages were coming in regularly every hour as expected and increasing with time as expected. The value of the NS integer was the correct ending day value, but the time showed it changed at 6:59pm, which I know is 100% incorrect.

I have. program that sends me text with certain integer values. The texts are arriving each hour and time stamped when received per the text system. The last one I receive at night is before 11pm and reported a value for one of the variable as 94. See below. Text is at 9:06pmEastern: (the 9:02 in the upper left is 9:02am the next day when I took the screenshot) However at 12:17am (next day), I checked my UD mobile to see what the value was. It had increased as expected, however the time it notes as "last changed" is at 6:59pm, which is BEFORE the above text and is incorrect. Is UD mobile defaulting to west coast time, or other? The time in my ISY is correct. (eastern). See below screen shot.

@SESamuels Question for you. You using the iAqualink NS on PG2 and it is working? mine quit about 2 weeks ago. Error connecting to the server. Maybe I should delete it and re install it. thanks

@SESamuels On the screen you show above, go to System / Polyglot Settings. that will open a page where you need to put in your IoP information: -IP address of the Polisy -Port, 8080 -Username of Isy -Password of Isy. Scroll to bottom, Hit SAVE. For PG3, you need to do the same, however it is under ISY / Add ISY.

Yes.. For PG3, you just have to stop and restart the NS and it automatically gets the latest version upon restart.

@someguy I understand your points above. FYI, I made the switch about a month ago: ISY from 994i hardware to the Polisy hardware. Am running PG2 and PG3 also on the Polisy. I was using Ring on PGC until PGC went down due to the security concerns. I had previously moved everything away from PGC to PG2 and saw an increase in speed and reliability immediately. Maybe my internet isn't as good as yours. Now with PG2 and PG3 on the polisy, I have migrated 7 Nodeservers from PG2 to PG3, rewarding those developers who have worked hard on making my ISY so much more useful and effective. Bottom line is a HUGE improvement in speed, and overall operation of ISY. For example, when I open Admin console, it loads in about 3 seconds. It used to take upwards of several minutes. Same with Mobilinc, and UD mobile. Backups occur in a few minutes vs 10 minutes or more. The biggest conversion for me was the lose of the Elk module and the new user the Elk Nodeserver. Again, the speed seems to have increased in this conversion, probably again due to a 10 yr old hardware device vs a new hardware device (Polisy). No regrets in the work to accomplish. This node server is top notch. Please note though, many of the aspects of PG3 are still in development and sometimes require using Terminal to SSH to the Polisy for things like updates etc. If you are not comfortable with that, you can simply stay on PG2 on polisy, along with Isy on Polisy (IoP) and you will see a performance upgrade and as PG3 gets further along in its development, move from pg2 to pg3. Good luck!

Got it ! thanks.

Am also wondering if in @BobM99 case, if he reversed the two program lines, will the program turn false during the reboot, which would stop the repeat, and then turn true again once on, causing a loop effect less than the 30 minutes. My suggestion would be to have the following, assuming he wants it running all the time: Program 1: IF time is 2am Then run THEN of program 2 Program 2: THEN: repeat every 30min reset zoom. This way, the program will always be running and if it were to stop due to reboot etc, it will start up again every day.

@bpwwer In working through my programs have noticed that Celcius and Farh. are gettin mixed up. I have chosen F in config. In the Device tree in Admin cons, it shows correctly as F. However in programs, when choosing a temp it only appears in C. See screen shots for better explanation. Thanks.

It appears that value 14 for GV13 is creating the UNKNOWN conditions result. I have it in two forecasts. Thanks Jim. worked. Rebooted ISY, resync UDMobile, now conditions show up as names not numbers. T

@bpwwer Thanks Bob! Great NS. One very minor and not important note: on the UD Mobile app, the “Conditions” are reporting as a number vs text. Not really important but just wanted you to know!

UPDATE: The forecast data has now populated. Just took a while. However Forecast conditions for Forecast 1 &2 are both "unknown" . Not sure if this is an error or just an update issue. Cheers and thanks again for all the hard work you are doing on this stuff!!

@JimboAutomates Jim, had success with the above ! yeah! -After taking screen shots of all the configurations in PG2 and noting the slot number, I deleted the NS on PG2. -took a little while for the slot to "free up" -Installed on PG3 choosing same slot that PG2 used, -Added back all the configs manually and by copy/paste of all the User Keys and Application keys from the Pushover website. -Had to restart it a few times for all the settings to take place and show in Admin Console, which I also had to restart a few times. RESULT: All notification s in programs are there w/o errors!! whew.. Only thing that needs fixing is the choice of On or Off message. They all defaulted to on / off. Good job Jim!

@JimboAutomates Hey Jim, Made the conversion tonight from PG2 to PG3. Got it running. Parameter instructions could be improved a bit, or examples given. Had to play a while to get it.But am not getting forecast info. Not sure what I should be putting for the station info for the forecast. I am using a Tempest on site for other data. Any suggestions? Thanks.

@macjeff @asbril see if the first post here helps you

Worked for me. thanks!

As I said above, I did nothing to my Mobilinc geofence during this whole time. It stopped working for several months, and then with 15.2 started working. Now with 15.3 its has been working wonderfully. Better then it ever has.