asbril

@bpwwer The good news is that you were able to replicate my error. The other thing is that when I restarted the Node server on IoP (to get latest version) it did indeed show 1.0.1, but in the dashboard it still showed the message that I needed to restart to get new version. I tried several times, but ended up to delete and re-install the Node server. That worked, but now in the Administrative Console instead of True or False, it shows 1 or 0 :

I had several issues while using Holidays Google of PG3 and went back to PG2. With my Google Calendar sub calendars, the Node server created several nodes, 2 fort each sub calendar and 1 for the controller. Some of these nodes seemed to work properly but show "0" on either the day or year. When I restarted the Node server in PG3 to see if this would be corrected (it did not), none of nodes showed in the Node server "Nodes" and in the Administrative Console, the "Holidays Node server Online" shows " 1 " and I am pretty sure that it showed " True " before. In the log I notice an error " 2022-04-22 11:53:24,892 Thread-2 udi_interface ERROR holidays:parameterHandler: Error getting credentials: (invalid_grant) Bad Request " I deleted and re-installed the Node server a few times, but the same situation happens again (some nodes 'date' or ' year' appearing as ' 0 ' and the nodes disappearing in the PG3 Node server Dashboard. Furthermore, in PG2 on several occasions, if I had an event the following day the Tomorrow node would correctly show True but then at midnight the Today node remained at False, with the Tomorrow node still (incorrectly) at True. Firstone looked several times at my logs and could not find anything wrong and together we concluded that maybe one of my many Holidays Google related programs somehow created a problem. HOWEVER, when I installed HG PG3 on Isy on Polisy, and not having any programs using HG on IoP, I noted that the same happened. My understanding now is that the issue is not because any of my programs (because there none on my IoP). The issue still happens from time to time on the PG2 version and in fact last night when I entered an event today in my Google calendar, the relevant Tomorrow node remained at False until I rebooted Polisy. I am not techie enough to understand whether or not the rebooting of Polisy was the reason of the correct node status. As mentioned above, I have gone back to using the PG2 version of HG. This is one of my favorite node servers and hopefully the cause of the day mis-match can be identified.

The general understanding is that your Zwave mesh network will run at tle lowest common denominator. I have some 80 Zwave devices, a few of which still are of the 300 series, most are 500 and a few are 700. One of the most important benefits of 700 series is longer distance and faster speed. In my specific case the distance is not an issue as I have more than enough Zwave devices to have a well working mesh network. Theoretically the speed of my network should be at the lowest common denominator of 300 series. However I believe that it depends on the route taken by each device. If a device uses a 300 series on the route to the ISY, then that route will be at 300. However if the route only uses 500 series (or 700) then the speed should be of the 500 series. In my case the 300 series are in a specific corner of my home and I don't think that they are used by (m)any other devices, so they should not slow down my network. I am slowly transferring my Zwave devices from my ISY to the ISY on Polisy. The latter has a 700 series USB dongle. I think that it is impossible to keep up with the changing Zwave standards (my name is neither Gates, Bezos or Musk) because by the time I would replace all my 300 and 500 series devices with 700 series, the 800 series comes out etc etc. Generally the speed of my network is fine, except in programs that run on a motion sensor, where there can be a seconds delay.

I have mine setup with 1 click is ON 2 clicks is OFF

I am not sure that this is correct. I have some 65 Zwave devices on my ISY (plus some 15 on IoP). The ST Inventory Node server on my ISY lists 267 Zwave nodes. My interpretation is that Zwave allows for some 232 Zwave devices, with most devices having several nodes.

Yes you can order the Zwave 500 dongle for ISY but a much wiser move is to get Polisy with a Zwave 700 stick. The initial expense is higher, but by far a smarter move. Also, starting a Zwave network on ISY on Polisy is easier than migrating Zwave from ISY to ISY on Polisy.

You are right. The condo came with 4 plain old fan wall switches. As it happened in 3 of the 4 switch boxes I had space to add a switch, and in the other case I was able to cut out in the wall panel to add a box. I was lucky and I understand that this is not always easy.

Of course !!!!!!! I just wanted to share an alternative.

Reading the above posts, I read up about the Bond bridge. It probably (reading the posts) works well but if you already have a Zwave setup, I prefer my solution. I have a dimmer switch for the Fan Lamp and a Fan controller switch for the fan, and no need for an alternative system to make it all work, as it is perfectly integrated in my ISY with both manual control and in ISY programs as well as UD Mobile. No need to spend more than $ 400.

I use one (Zwave) dimmer switch for the light and another (Zwave) fan switch for the fan. I have 4 fans in my home and this works fine.

I understand and yes there are alternatives. For me the Holidays Google is the Node server that I use most. I have 9 sub calendars in my Google calendar with many programs managing my lights, curtains and music.

That would work for holidays that always have the same date (December 25), but not for 'floating' holidays. However you can create a floating calendar "holidays", and then manually create a whole day event in the calendar, using that calendar. I have done that for the coming five years and it took me probably 10 minutes. Then create a program in ISY using the respective node. It sounds more compliacted than it is.

That is what I did with Google Holidays. I created a sub-calendar named Holidays in my Google calendar. On a particular holiday, let's say that I want Cinco de Mayo, I will create a all-day event on May 5 using the Holidays sub-calendar. After that in ISY's Administrative Console on May 4, the Tomorrow node for Holidays will be True and on May 5 the Today node will be True. This allows me to run programs using the relevant Tomorrow and/or Today node. I have some issues with the PG 3 version of Holidays Google, some are the same that I sometimes have with the PG 2 version but I also have some other issues. I have sent a pm to @firstone with the logs.

Michel, if it ever happens again then I will try to remember to get my Son's ISY log, but the reboot resolved the issue.

My Son is very smart in business but I bet that he does not know the difference between a modem and a router, and it is doubtful that he would know anything about a firmware update .

I make extensive use of Holidays Google and in fact I created 9 specific sub calendars that I use in ISY programs. As example, I have specific wake-up ISY programs for the days that my wife works, when I have morning meetings, and other programs such as for when the cleaning lady comes. My Chromecast devices play different radio stations depending on when my wife works or not . This is one of my favorite node servers and indeed yesterday I upgraded to the PG3 version. Regretfully, from time to time, something goes wrong and at midnight the calendar nodes in my ISY do not change to the following day. This happened this morning and the early wake-up program ran because the specific Holidays Google node was stuck on yesterday and therefore it took yesterday's calendar event as being for today. However the ISY Administrative Console itself was on the correct date. In other words, my Administrative Console showed today's date at the top left but yesterday's date in the various calendar nodes of the Holidays Google Node server in ISY. Very weird. The creator of the Node server, @firstone has been very nice and several times has reviewed my Node server logs which basically showed that the Node server was running properly. So clearly it is something in ISY or in the Administrative Console. I believed that maybe the error was that I left the AC open during the night, but that was not the case last night, so I am at a loss. As mentioned, it only happens infrequently and I just live with it. Right now I am only running the Node server on ISY and not yet on IoP. Maybe the issue disappears when I migrate everything to IoP. The issue may be specific to my setup, and I strongly recommend this Node server.

Just for information, this morning I went to my Son's home, connected locally to his ISY and did a reboot. Now the ISY is again accessible remotely, including in ISY Portal. This has never happened before. If it ever happens again, I will just ask my Son or daughter-in-law to power cycle the ISY.

Yes, thanks @brians !

I checked that to make sure and I actually renewed it 2 weeks ago. Maybe the ISY needs a reboot after renewing the Portal account ?

Thanks good ideas. He lives only a few minutes from us and I will go by today or tomorrow.

This morning I wanted to change something on my Son's ISY (5.0.16) using remote login credentials of his ISY Portal account and I was not able to access it. I can enter his ISY Portal account and it shows that he ISY is not connected. The ISY is working normally, executing its programs, and it also sends programmed emails to confirm certain actions. Does anyone hs an idea why this ISY is working normally but showing as not connected in the ISY Portal ?

and not the Sounds of Silence

@lilyoyo1 I am surprised that you did not suggest Lutron to @SSchmidt

Thanks @brians I am following your comments with great interest and trust that, with some time, this will become clear and easy to work with. Thanks again !!!!

When I click on Download in PG 3 "Backup and Restore" nothing happens.....