Jump to content
View in the app

A better way to browse. Learn more.
Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Programs not running as expected

asbril
in ISY994

Featured Replies

Posted

This morning I noticed that several nodes of my Holidays Google nodeserver that were supposed to run Today were scheduled to run Tomorrow. Another program, not based on that nodeserver, also did not run.

The same happened yesterday and last night before going to sleep I checked that the  "Holiday Google" programs were properly "True" for  Tomorrow ("today" based on last night). But it was wrong again this morning. Somehow the nodeserver and/or ISY believed that it was still yesterday.

I restarted the Nodeserver in the Polisy Dashboard and then the nodes changed to the correct status.

The first suspicion was that something  was (is) wrong with the nodeserver or Polisy, but the non-nodeserver program, just based on ISY (mo-tu-we-th-fr) also did not run.

To be safe, I rebooted both Polisy and ISY and will see tomorrow what happens. Does anyone has an idea ?

 

1 hour ago, asbril said:

but the non-nodeserver program, just based on ISY (mo-tu-we-th-fr) also did not run.

Does right click Run Then and/or Run Else work correctly for that program?

  • Author
5 minutes ago, MrBill said:

Does right click Run Then and/or Run Else work correctly for that program?

Yes they all do. Thanks to your help, I actually created buttons in Home Assistant that allow to run "Then" of these programs. I did that last night before going to bed, but something seemed to have happened at (or after) midnight whereby either ISY and/or Polisy decided that Today is Tomorrow.

12 minutes ago, asbril said:

Yes they all do. Thanks to your help, I actually created buttons in Home Assistant that allow to run "Then" of these programs. I did that last night before going to bed, but something seemed to have happened at (or after) midnight whereby either ISY and/or Polisy decided that Today is Tomorrow.

I really have no comment about how the Google Calendar nodeserver works or doesn't work, It hasn't been modified by the developer in 3 years (I looked), and I don't think many people use it.  On the other hand the google Calendar API may have changed in the past 3 years.

The only comment that I have, which was the basis of the question above is that folder conditions will also prevent manual Run Then's from working. So that was what I was fishing for when I asked the question.   I don't know if you ever used any, I don't remember mentions but folder conditions could prevent the (mo-tu-we-th-fr) program from working.  

Another place to look for clues is the ISY Error log.

  • Author
52 minutes ago, MrBill said:

I really have no comment about how the Google Calendar nodeserver works or doesn't work, It hasn't been modified by the developer in 3 years (I looked), and I don't think many people use it.  On the other hand the google Calendar API may have changed in the past 3 years.

The only comment that I have, which was the basis of the question above is that folder conditions will also prevent manual Run Then's from working. So that was what I was fishing for when I asked the question.   I don't know if you ever used any, I don't remember mentions but folder conditions could prevent the (mo-tu-we-th-fr) program from working.  

Another place to look for clues is the ISY Error log.

Thanks @MrBill. For the time being, I'll wait to see of the issue occurs again tomorrow, after I restarted  the nodeserver,  and rebooted both Polisy and ISY.

BTW Holidays Google is a fantastic nodeserver and should be considered by many. By adding a whole-day event in a Google Calendar, you can trigger a program.  These are some examples of how I use it :

. Days that my wife works : wake-up program with lights and curtains

. Days that I have meetings : also wake-up program at different time(s)

. Days that our cleaning lady comes : light programs and disabling of alarms at specific times

. Holiday lighting

This nodeserver is one of my favorites.

5 hours ago, asbril said:

This morning I noticed that several nodes of my Holidays Google nodeserver that were supposed to run Today were scheduled to run Tomorrow. Another program, not based on that nodeserver, also did not run.

The same happened yesterday and last night before going to sleep I checked that the  "Holiday Google" programs were properly "True" for  Tomorrow ("today" based on last night). But it was wrong again this morning. Somehow the nodeserver and/or ISY believed that it was still yesterday.

I restarted the Nodeserver in the Polisy Dashboard and then the nodes changed to the correct status.

The first suspicion was that something  was (is) wrong with the nodeserver or Polisy, but the non-nodeserver program, just based on ISY (mo-tu-we-th-fr) also did not run.

To be safe, I rebooted both Polisy and ISY and will see tomorrow what happens. Does anyone has an idea ?

 

@asbril I still use the Holidays Google Nodeserver for a few of my programs. I had a similar experience to you last week. I found a lot of errors in the Nodeserver log in the dashboard. Restarting the Nodeserver and watching that it cleared up worked for me.

Edited by DaveStLou

    • Like 1

    @asbril,

    Please check our error log and see whether or not ISY's time changed (say by a few hours/days).

    With kind regards,
    Michel

    • Author
    4 hours ago, Michel Kohanim said:

    @asbril,

    Please check our error log and see whether or not ISY's time changed (say by a few hours/days).

    With kind regards,
    Michel 

    Hi Michel

I am not very good at "reading" the error log and hereunder I post the log as of Sunday afternoon. 
I checked the Program  early Sunday evening when it correctly showed the Node as Tomorrow = True. 
Some time between Sunday evening and Monday morning (when Tomorrow became Today) it went to False, 
and I am not sure to see that in the error log :

Sun 2021/11/14 07:23:35 PM	System	-100	[DHCP] state=RENEW	

Sun 2021/11/14 09:35:59 PM	System	-5012	77	

Sun 2021/11/14 09:50:15 PM	System	-5012	81	

Sun 2021/11/14 09:51:24 PM	System	-170001	[UDSockets] HTTP:22 error:6	

Sun 2021/11/14 09:51:29 PM	System	-170001	[UDSockets] HTTP:22 error:6	

Sun 2021/11/14 09:51:34 PM	System	-170001	[UDSockets] HTTP:22 error:6	

Sun 2021/11/14 09:56:47 PM	System	-5012	82	

Sun 2021/11/14 09:56:47 PM	System	-170001	[UDSockets] HTTP:26 error:6	

Sun 2021/11/14 09:56:52 PM	System	-170001	[UDSockets] HTTP:26 error:6	

Sun 2021/11/14 10:09:38 PM	System	-5012	83	

Sun 2021/11/14 10:10:46 PM	System	-170001	[UDSockets] HTTP:29 error:6	

Sun 2021/11/14 10:10:51 PM	System	-170001	[UDSockets] HTTP:29 error:6	

Sun 2021/11/14 10:10:56 PM	System	-170001	[UDSockets] HTTP:29 error:6	

Mon 2021/11/15 06:11:45 AM	System	-100	[DHCP] state=RENEW	

Mon 2021/11/15 07:05:30 AM	System	-5	Start	

Mon 2021/11/15 07:05:54 AM	System	-110022	/DEF/F6/I1/NLS/EN_US.TXT	

Mon 2021/11/15 07:06:08 AM	System	-7115	ID 0066 :err=0, tag='cmd', num=4, nest=4, offse	

Mon 2021/11/15 07:06:10 AM	System	-7115	ID 00A8 :err=0, tag='cmd', num=4, nest=4, offse	

Mon 2021/11/15 07:07:06 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:07:16 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:07:17 AM	System	-170001	UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25	

Mon 2021/11/15 07:07:26 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:07:28 AM	System	-170001	UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25	

Mon 2021/11/15 07:07:29 AM	System	-170001	UDQ:Queue Full: PDM : Task[11] HTTP_1 HTTP-Get pty=19	

Mon 2021/11/15 07:07:36 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:07:36 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:07:39 AM	System	-170001	UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25	

Mon 2021/11/15 07:07:46 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:07:57 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:07:57 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:07:57 AM	System	-170001	UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25	

Mon 2021/11/15 07:08:07 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:08:07 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:08:17 AM	System	-170001	UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25	

Mon 2021/11/15 07:08:18 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:08:25 AM	System	-170001	UDQ:Queue Full: PDM : Task[11] HTTP_1 HTTP-Get pty=19	

Mon 2021/11/15 07:08:27 AM	System	-170001	UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25	

Mon 2021/11/15 07:08:28 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:08:37 AM	System	-170001	UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25	

Mon 2021/11/15 07:08:38 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:08:38 AM	System	-170001	UDQ: Queue(s) Full, message ignored	

Mon 2021/11/15 07:06:17 AM	System	-7115	ID 0143 :err=0, tag='cmd', num=4, nest=4, offse	

Mon 2021/11/15 07:06:27 AM	System	-170001	[Network] Established	

Mon 2021/11/15 07:06:30 AM	System	-5011	uuid:0	

Mon 2021/11/15 08:37:50 AM	System	-5012	27	

Mon 2021/11/15 03:18:59 PM	System	-5012	29	

Mon 2021/11/15 03:25:31 PM	System	-5012	0	

Mon 2021/11/15 03:25:35 PM	System	-140000	sub.isy.io	

Mon 2021/11/15 03:25:35 PM	System	-5013	0	

Mon 2021/11/15 03:25:45 PM	System	-140000	my.isy.io	

Mon 2021/11/15 03:26:19 PM	System	-140000	my.isy.io	

Mon 2021/11/15 03:26:49 PM	System	-140000	my.isy.io	

Mon 2021/11/15 03:27:19 PM	System	-140000	my.isy.io	

Mon 2021/11/15 03:27:49 PM	System	-140000	my.isy.io	

Mon 2021/11/15 03:28:19 PM	System	-140000	my.isy.io	

Mon 2021/11/15 03:28:49 PM	System	-140000	my.isy.io	

Mon 2021/11/15 06:12:38 PM	System	-50001	-12	

Mon 2021/11/15 06:49:23 PM	System	-5012	32	

Mon 2021/11/15 07:05:26 PM	System	-100	[DHCP] state=RENEW	

Mon 2021/11/15 07:54:08 PM	System	-50001	-7	

Mon 2021/11/15 09:07:00 PM	System	-5012	0	

Tue 2021/11/16 06:10:16 AM	System	-100	[DHCP] state=RENEW	

Tue 2021/11/16 07:03:04 AM	System	-5012	33
    • Author

    I just noticed that another Nodeserver "ISY Inventory"  needed to be restarted in the Polisy Dashboard. As restarting the "Holidays Google"  resolved my other issue as well, I wonder whether it is possible to program / schedule an automatic restart of nodeservers.

    @asbril,

    You mentioned other programs that were not node server dependent also stopped. What's the snippet of error log for those?

    Also the error log for both of those node servers.

    With kind regards,

    Michel

    • Author
    6 minutes ago, Michel Kohanim said:

    @asbril,

    You mentioned other programs that were not node server dependent also stopped. What's the snippet of error log for those?

    Also the error log for both of those node servers.

    With kind regards,

    Michel

    Hi Michel

    As I restarted both Nodeservers as well rebooted Polisy, the logs only show info thereafter. Next time it happens (thankfully not often), I will try remember to first download the logs.

    • Like 1
    Guest
    This topic is now closed to further replies.
    Go to topic listing

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.