macjeff

Thanks. Perfect.

Is there release notes on Pg3? Like saw a new version .62 today and curious what was fixed. Would like to bookmark it if there is a forum or wiki on the version history

I had this issue. Assuming you did delete the PG2 stuff before going to pg3 sometimes it did not delete from ISY. Go to ISY and under the Node server menu I think you go down to configure. See if any of those are there and if so delete them from ISY. Then add them in Pg3. This happened twice. Once when doing the original conversion and once when deleting a Node server when I had the admin console open at same time. Both times the delete in the admin console fixed it ** make sure its deleted from both pg2 and pg3 first before deleting from ISY. The only reason you should have to do this is if all else fails.

That did not work for me. I had to manually do each node. The restore did not work but that was several months ago

It’s kind of a headache but worth the effort. You have to delete it from PG2 And then immediately add again to PG3. On most of the node servers everything was fine because the names and everything are exactly the same but in a few of them I had to a tweak some programs.

Update… Just tried to pg2 version and it works fine so my issues are only with the PG 3 version

My token is in there and as soon as I enter it all of my cakendars show up in the gray section so I know it’s talking to it. I listed all of my calendars like you did and waited and nothing happened and then I restarted the node server and now all the calendar names are gone From the gray area. Giving up for now I have to head out for now

That’s probably why it’s not working for me. Is there any chance you could send me an example of exactly how to put it in there under custom configurations. I know my counter names will be different but I wanna make sure I have them today and tomorrow correct. There are no instructions after you get the original authentication done which is working but then it’s stuck

I have the same issue with the new version 1.01 and just tried with 1.02. When I first authenticate I paste the token and choose save. then all my calendars show up in the grey configuration box but never in ISY. If I restart the Node server the calendars never come back in the grey area or the ISY. Do I need to add them as a key field in configuration or something?

It’s already been imported as is to PG3. I think it was just a direct import and not a rewrite with latest api

Although most of my delays are under a minute like you said, I have had a few really weird ones where a few minutes later the program just randomly seems to run where the status was updated instantaneously. I think it’s related though.

TEAMWORK!!! I wish the US Gov could work together so well and get things fixed!!!!

I was using a Variable to make alexa announce and to change the status of a keypadlinc button. To take variables out of the equation I used a Node server Called Virtual Buttons that basically pushes a button to make alexa do something. If I push the button in the Node server its instant. This AM we closed a garage door and also had motion in the driveway. Two separate devices with two separate programs. Both used the new virtual buttons. Both light up a keypad button. With both of them the device was triggered. Alexa said nothing and the keypadlinc button did not light up. About 5 min later Alexa said something and I looked and the keypadlinc was lit up. for the motion it worked once right away but a few min later I see the device trigger again (someone walked past the motion) in the ISY but the program has yet to run at all. So its a delay and sometimes a total ignore for me. Makes me wonder what else is not working. Like I have leak sensors. What if there is a leak. Will it let me know?

If you would update the Node server I would contribute both financially and also testing. I can give you access to my Hue account. I only have a few bulbs and lightstrip so if you accidentally turn one on or off it wont bother anyone. Let me know if you are interested. I think you could charge 20-30 for a pg3 hue Node server.

Its just as easy for me to make variables for the holiday dates which I have a reminder set in the ISY to remind me to do them the first of each year. but with all this said there are lots of US holiday feeds out there. It cant be that hard to have a Node server check the feed and import the name of the holiday can it? Probably dont have the programming knowledge to do it myself though.

Yes tried them both. Neither can give me a field with holiday name Like Holiday today. Holiday name Yes. Christmas No. None

see screenshot under the Sun part of TimeData

The problem is it will identify a holiday or a day off but unless there’s something wrong on my end it doesn’t tell you the actual name of the holiday which is what I want

Is Holidays not possible? Like you have Spring, Fall, etc. How about list the holiday if that day is a holiday. I can config most of them except easter with programs but so much easier to say if Easter then do this

I reported to @bpwwer. Somewhere it must think we are still on older version.

FYI. I updated last night but today it told me I need the update. I already had it. Strange. That message was not there last night. I will send to @bpwwer You can see version number in screenshot already up to date

me too

Same issue here. Restarted and its on 3.3.1 not 3.3.2 but the UPDATE needed notice went away.

I disabled an insteon motion sensor. It kept working. So I had to disable the programs that it uses. I did confirm it has the red circle over the device. Confirmed with another insteon device also.

I had this issue too yesterday. Yale Z-Wave locks also. I did update neighbors to all powered devices in order from the Polisy to the furthest device. It you go to event viewer you should get success on each one. Then do update neighbors on yourr locks last. At that point all locks worked but one. On that one i took out the batteries for 30 seconds (not the z-wave module) and then put back in and then waited a minute for lock to reboot. Then I updated neighbors on that lock and it worked. Now they are all working.