BamBamF16

Every night my NS fails, then disconnects, then reconnects. It happens at midnight and takes less than a minute. This just started after upgrade to PG3x. Additionally the NS functionally is very spotty. Plugs won't always be connected or function. Thoughts? Thanks , Jeff

All, Just to circle back on this and give the solution that worked. Based on a suggestion from @bpwwer I reinstalled my NS's in the same slots. That was what ended up actually getting everything working again. PG3x thought the NS's were started and running, but they actually weren't. This was post upgrade from PG3 to PG3x. Thanks for the help Bob! Jeff

They were all started, but a restart didn't do anything new. Ill PM you the log package. Thanks. Jeff

I did all that. Still nothing. All NS showing disconnected and no data in IoX. Thanks.

Yes. Restarted each NS and PG3x. Nothing is working.

I thought upgrade went OK. This was my first upgrade on PG3x. It looks OK, but all 3 node servers are showing disconnected and will not show up in AC. Thoughts?

Create a program that runs Dec 31 at 2355 and adds year total to variable.

Follow up to my issue earlier. UDI had to remote in and run some uodat/upgrade code. Everything is back up and running. As always great customer support from UDI.

Upgraded from 5.5.5 to 5.5.9. PG3 should have upgraded from 3.17 to 3.18 but I don't know if it did. PG3 has not come back since. Used AC to update. Got all the beeps. Have not been able to log in since. Can't even find PG3. I can SSH to policy just fine. Any thoughts?

The issue I have isn't in ISY, its in HA with the double devices for each power port. Trying to eliminate from ISY, since I don't use the strips there at all, so that I only have one of each switch in HA. I suppose as a work-around I could disable the ISY imported ones in HA.

I have a couple of power strips that work fine in NS but are better served with HA as the primary controller. i would like to prevent the strips from being imported in the NS and only use the HA integration. Is this possible? Will this work if I check the delete button?

Had a power surge/off-on event last night. Everything rebooted fine. But my Kasa NS showed online and connected, but it actually wasn't. I have a feeling the NS restarts faster than the actual Kasa devices so it uses old IP addresses. Then it must not actually find the devices when they come back online because nothing works until I restart the NS.

Thanks for the words. I'll order 1 of each to test out. Leaving towards leviton though

Anyone have any comparison between: Enbrighten 55256 Z-Wave Plus Smart Receptacle, Works with Alexa, Google Assistant, Tamper-Resistant, 1 ZWave 1 Always On Outlet Hub Required, White https://a.co/71BUb61 Or Limited-time deal for Prime Members: Leviton ZW15R-1BW Decora Smart Tamper-Resistant Outlet with Z-Wave Technology, 1 Pack, White https://a.co/ijB5TsX ?? Both are S2. Leviton is $37 vs $49 for Enbrighten. Thanks, Jeff

Honestly with whatever extra you would buy, the bond bridge and it's NS should work and is probably cost equivalent. Caveat-i have a bond bridge but not blinds yet. Still building new house.

I got a direct scene done with my switches IAW UD directions.

Here is what I have:

The before and after only apply to the hours/minutes/or seconds before our after the appropriate time. 0/0/0 Before sunset is the exact same time as 0/0/0 after sunset. In program 1 above read it as follows: if from sunrise to sunset then Set Carriage lights Off else run program carriage lights 35% (if) There are 2 triggers: Sunrise and Sunset. At sunrise the program evaluates True and runs the then branch (carriage lights off). At sunset the program evaluates as false and it runs the else (run carriage lights 35% (if)). Note - this is commanding the execution of the 35% program NOT enabling it. Nothing else happens with this program at any other time of the day as there are no other triggers. In the second program there are 3 triggers (change in motion sensor status, sunset and sunrise (next day). Since you have 0 hms, these triggers occur exactly on the event. If motion status changes that starts an evaluation of the program condition. SO DOES sunset and sunrise as they are also triggers. (I assume this program is enabled or it would only execute once per day based on program 1.) So when motion status change is the trigger, then it evaluates all three conditionals (motion status off, and is it from sunset to sunrise (next day)). This program will also evaluate the if statement at sunset and sunrise (next day). If motion sensor status is True and the current time is between sunset and sunrise (nd) then the lights will come on to 100%. If motion sensor status is true and current time is outside sunset to sunrise (nd), or between sunrise and sunset then the lights will go to 35%. Basically the only time the lights go to 100% is with true motion and between sunset and sunrise. Between sunrise and sunset all motion sensor status changes will command lights to 35%. Also motion to false between sunset and sunrise (nd) will also set lights to 35%. Hope this makes sense, Jeff

I just updated my Polisy and I think the tag NS. I am now getting similar emails: URL: GarageDoor Index (zero based) must be greater than or equal to zero and less than the size of the argument list., URL attempted to call: http://10.0.1.71:41171/update?tmgr_mac=D244789C9054&name={0}&tagid={1}&temp={2}&hum={3}&lux={4}&ts={5}&batv={6}&signaldBm={7}&txpwr={8} Sent at: 3/10/2022 2:46:41 PM. The 10.0.1.71 is my polisy address. I assume the 41171 is the port for the NS.

@lilyoyo1There are local voice activations currently in development (almond/Ada). They will be integrated with HA.

@lilyoyo1 True, but baby steps for now. There are some local only voice activations I am looking into.

Mostly because then I have to maintain 2 different integrations. The alexa integration is cloud based and it seems the NS is local, no? Jeff

Couple of things. 1. 0 minutes before sunrise (next day) and 0 minutes after sunrise (next day) are the exact same time, so no difference. 2. The second program will trigger 3 times: When the motion sensor status changes, at sunset and sunrise (next day). Looks like to me during daylight hours and with motion the lights should go to 35% (else condition). Same thing when the status changes to off (no matter the time of day).

I'm not sure if this is true, but I can't add any Kasa device to alexa. Suggested on UD forums to ask to make sure hints are set correctly. For the H105 plug it probably should be category of 0x04 and a subcategory of 0x02, I think. Also added to Github. Thanks, Jeff