danbutter

I am able to use the thermostat through the AC, but I lost control of fan modes that I had before and it still shows strange behavior with the neighbors: Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] ---------------------------------------------- Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] Main_Floor_Thermostat Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] ZW006_1 uid=6 security=None type=4.8.6 mid=275 tid=17750 pid=21556 Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x20 V1 BASIC Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x40 V1 THERMOSTAT_MODE Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x42 V1 THERMOSTAT_OPERATING_STATE Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x43 V2 THERMOSTAT_SETPOINT Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x44 V1 THERMOSTAT_FAN_MODE Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x45 V1 THERMOSTAT_FAN_STATE Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x70 V1 CONFIGURATION Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x31 V1 SENSOR_MULTILEVEL Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x86 V1 VERSION Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x72 V1 MANUFACTURER_SPECIFIC Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x85 V1 ASSOCIATION Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x2C V1 SCENE_ACTUATOR_CONF Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x2B V1 SCENE_ACTIVATION Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x73 V1 POWERLEVEL Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - x81 V1 CLOCK Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - Secure Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] Last working route from ISY to Node 6 - Main_Floor_Thermostat Sat 09/05/2020 04:32:40 PM : [ZWAVE-TX ] [01123456789F] REQ ZW_GET_LAST_WORKING_ROUTE Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] - Node 23 - Plant Light Sat 09/05/2020 04:32:40 PM : [ZW-SHOW ] Sat 09/05/2020 04:32:41 PM : [ZWAVE-TX ] [01071234567890F18F] REQ ZW_GET_ROUTING_INFO Sat 09/05/2020 04:32:41 PM : [ZWAVE-TX ] [01071234567890F28D] REQ ZW_GET_ROUTING_INFO Sat 09/05/2020 04:32:41 PM : [ZWAVE-TX ] [01071234657891F38C] REQ ZW_GET_ROUTING_INFO Sat 09/05/2020 04:32:41 PM : [ZW-SHOW ] Node 6 - Main_Floor_Thermostat has the following neighbors Sat 09/05/2020 04:32:41 PM : [ZW-SHOW ] - - Node 3 - Front Door Lock Sat 09/05/2020 04:32:41 PM : [ZW-SHOW ] Sat 09/05/2020 04:32:41 PM : [ZWAVE-TX ZW006_1] [85/05] Assoc Groupings Get ACK,AUTO,EXPLORE To=0x06 Sat 09/05/2020 04:32:41 PM : [ZWAVE-RX ZW006_1] [85/06] Assoc Groupings Report supported=0x03 ACK,AUTO,EXPLORE From=0x06 Sat 09/05/2020 04:32:41 PM : [ZW-SHOW ] Node 6 - Main_Floor_Thermostat has 3 association groups Sat 09/05/2020 04:32:41 PM : [ZWAVE-TX ZW006_1] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x06 Sat 09/05/2020 04:32:41 PM : [ZWAVE-RX ZW006_1] [85/03] Assoc Report grp=0x01 max=0x05 frames=0x00 nodes=0x01 ACK,AUTO,EXPLORE From=0x06 Sat 09/05/2020 04:32:41 PM : [ZW-SHOW ] Associations for group 001 of ZW006_1 Main_Floor_Thermostat Sat 09/05/2020 04:32:41 PM : [ZW-SHOW ] Max Associations = 5 Sat 09/05/2020 04:32:41 PM : [ZW-SHOW ] - Node 1 - [This ISY] Sat 09/05/2020 04:32:41 PM : [ZW-SHOW ] Sat 09/05/2020 04:32:42 PM : [ZWAVE-TX ZW006_1] [85/02] Assoc Get grp=0x02 ACK,AUTO,EXPLORE To=0x06 Sat 09/05/2020 04:32:42 PM : [ZWAVE-RX ZW006_1] [85/03] Assoc Report grp=0x02 max=0x05 frames=0x00 nodes=0x01 ACK,AUTO,EXPLORE From=0x06 Sat 09/05/2020 04:32:42 PM : [ZW-SHOW ] Associations for group 002 of ZW006_1 Main_Floor_Thermostat Sat 09/05/2020 04:32:42 PM : [ZW-SHOW ] Max Associations = 5 Sat 09/05/2020 04:32:42 PM : [ZW-SHOW ] - Node 1 - [This ISY] Sat 09/05/2020 04:32:42 PM : [ZW-SHOW ] Sat 09/05/2020 04:32:42 PM : [ZWAVE-TX ZW006_1] [85/02] Assoc Get grp=0x03 ACK,AUTO,EXPLORE To=0x06 Sat 09/05/2020 04:32:42 PM : [ZWAVE-RX ZW006_1] [85/03] Assoc Report grp=0x03 max=0x05 frames=0x00 nodes=0x01 ACK,AUTO,EXPLORE From=0x06 Sat 09/05/2020 04:32:42 PM : [ZW-SHOW ] Associations for group 003 of ZW006_1 Main_Floor_Thermostat Sat 09/05/2020 04:32:42 PM : [ZW-SHOW ] Max Associations = 5 Sat 09/05/2020 04:32:42 PM : [ZW-SHOW ] - Node 1 - [This ISY] Sat 09/05/2020 04:32:42 PM : [ZW-SHOW ] Sat 09/05/2020 04:32:42 PM : [ZW-SHOW ] ---------------------------------------------- The last working route isn't through the only neighbor and the only neighbor is a battery device. On top of that it has three associations with the ISY. Did you factory reset your thermostat after excluding it and before adding it again? Not saying you should have to, but these upgrades aren't going smoothly so maybe that would make the difference? Maybe clearing java cache? Good luck.

Unfortunately this didn't do anything for my situation. No changes. Still the only neighbors are the ones that disappeared when I hit synchronize and then had to add again. Soooo not looking forward to trying to exclude and add everything back. I'm going to have to put a UPS and my ISY and a wireless network bridge in a backpack and walk around my house...get out the ladders for my floodlights. Uggh...So I think I'm going to revert to where I was before for a while. Maybe I'll try the next update in a couple of months. I sure hope they can figure it out.

So a general recap of my experience with 5.2.0. No problems with insteon. All my issues are with zwave. I have the 500 series controller/board/dongle. I have a mix of the non-plus zwave devices as well as plus devices. After upgrading most of my devices show no neighbors. If I do show info in event viewer then the last working route from ISY to node shows which node the packet traveled through. Then right after that they show no neighbors. If I do a synchronize on a non plus device it disappears from the ISY and that is it. It is just gone. If I do a synchronize on a plus device it may or may not work. If I do update neighbors directly after the above scenario where it says the last known path is through two devices, but it has no neighbors then it will list a neighbor that wasn't listed just before. In fact if it does say success in updating neighbors then after doing show all info it will only ever list a device that has disappeared after a synchronize and then later excluded and re added to the ISY. So any neighbors are ones that have been excluded and added again while on 5.2.0. None from before. It seems like my only option is to exclude and re-add every device to get them all working again. Less than ideal. Anybody have any ideas or something I missed? Thanks

GE/jasco outlet. Not a plus model. I don't really use it much outside of winter so I picked it to try this on. I just tried on a zwave plus switch that I don't have installed yet...just on a pigtail and wirenuts and the sync worked ok. Added a new node that has zero controls though...strange. I hope to have a bit of time this weekend to mess around and will try on some non-plus devices to see if they all disappear like last time I tried to sync.

Well I was a bit leary of the synchronize because the last time I tried I never got the node back, but I have a backup so I tried again, but now with 5.2.0. So before doing the sync I did the show all and this is what I got: Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] ---------------------------------------------- Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] Mudroom_Outlet Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] ZW020_1 uid=20 security=None type=4.16.1 mid=99 tid=18770 pid=12337 Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x25 V1 SWITCH_BINARY Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x27 V1 SWITCH_ALL Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x75 V1 PROTECTION Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x73 V1 POWERLEVEL Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x70 V1 CONFIGURATION Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x86 V1 VERSION Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x72 V1 MANUFACTURER_SPECIFIC Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x77 V1 NODE_NAMING Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - Secure Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] Last working route from ISY to Node 20 - Mudroom_Outlet Thu 08/27/2020 04:07:59 PM : [ZWAVE-TX ] [01040092147D] REQ ZW_GET_LAST_WORKING_ROUTE Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - Node 22 - UnstableZ Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] Thu 08/27/2020 04:08:00 PM : [ZWAVE-TX ] [01070080140000FE92] REQ ZW_GET_ROUTING_INFO Thu 08/27/2020 04:08:00 PM : [ZWAVE-TX ] [01070080140100FF92] REQ ZW_GET_ROUTING_INFO Thu 08/27/2020 04:08:00 PM : [ZWAVE-TX ] [01070080140001EB86] REQ ZW_GET_ROUTING_INFO Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] Node 20 - Mudroom_Outlet has the following neighbors Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] No Neighbors Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] Node 20 - Mudroom_Outlet does not support associations Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] ---------------------------------------------- It is a (non plus) GE outlet. Notice how it has no neighbors, but had to go through another node to get to it??? So I did the synchronize and it disappeared and didn't get added back. This is what the event viewer showed for that: Thu 08/27/2020 04:08:21 PM : [ZWAVE-NODE-SYNC] [DS1] sync [ZW020_1] request Thu 08/27/2020 04:08:21 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:08:21 PM : [ZWAVE-NODE-SYNC] ---- Start Processing Z-Wave Node 20 (0x14) ---- QT1 Thu 08/27/2020 04:08:21 PM : [0046 15] Statement 1, line in 'Then' reset for node [ZW020_1] Thu 08/27/2020 04:08:21 PM : [0045 15] Statement 1, line in 'Then' reset for node [ZW020_1] Thu 08/27/2020 04:08:21 PM : All program references removed for node [ZW020_1] Mudroom_Outlet Thu 08/27/2020 04:08:21 PM : [ZWAVE-NODE-SYNC] Z-Wave node 1 (0x14) does not exist, removed 20 associated ISY node(s) Thu 08/27/2020 04:08:21 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:08:21 PM : [UZW-CMD 45 ERR ] Get NodeDef : ZW020_1 Thu 08/27/2020 04:08:22 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:08:22 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:08:22 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:08:22 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Thu 08/27/2020 04:08:22 PM : [ZWAVE-NODE-SYNC] -- Finished -- ISY/Z-Wave Node Sync -- So now it is just gone. So I went and hit the button on the outlet after it was no longer in the ISY and got this: Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105004A85FECB] REQ ZW_ADD_NODE_TO_NETWORK Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105004B05FF4B] REQ ZW_REMOVE_NODE_FROM_NETWORK FUNCID=5 STATUS=255 UID=75 Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105004D05EB59] REQ ZW_CONTROLLER_CHANGE Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105005000EC46] REQ ZW_SET_LEARN_MODE Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:25:51 PM : [ZWAVE-RX ] CAN Thu 08/27/2020 04:25:51 PM : [ZWAVE-WAIT ] Waiting 5 ticks for retry 1 of 3 Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:25:53 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:25:53 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Still not in the ISY though. Anybody else have their zwave nodes just disappear when doing a synchronize on them?

Ok so thanks to all that answered my question about a mixed zwave network. I do have the 500 series board in my ISY so I took a chance and upgraded to 5.2.0. So far it seems like no zwave device knows about any other device. Do I have to run that Update Neighbors on every zwave device I have since the "Heal" is gone now? The other thing I have noticed is that my Kwikset locks don't like this version much. If I manually operate the locks they show up in the AC, but after that ISY doesn't seem to know they are there anymore and there is no battery level displayed like there always has been before now. Saw this in the event viewer when running a query on one of them: Wed 08/26/2020 06:15:32 PM : [ZW-TX-FAILED] enc=Fail uid=29.0 cmd=0x80.02 BATTERY Thoughts?

So I'm a bit worried about this as I still have quite a few devices that are not "Plus"/500 series. I have two thermostats, outlets, plug in modules, multiple door locks that would likely cost me $1000 or more to replace all of to get a newer zwave plus equivalent. So do I upgrade to the 5.2.x firmware now or not? Will this leave me in a spot where I can't make something route correctly without the "heal" or no?

Good to know this works in ISY. I was just going to post to ask if anyone had tried and then found this thread through searching. I plan to get these for my kids rooms and guest room since the speed of the fan isn't something that needs to be changed much in these locations. I'll have to run new electric with another conductor for the fan motor, but that will be more annoying than difficult. Thanks for posting.

Haven't had much time to play with it, but it did trip and I didn't get notified again. Wondering if it is the plug. It is an inovelli outdoor plug and I have had lots of issues with inovelli and the ISY. If it stops raining maybe I swap it for a GE that I have and see if it makes a difference.

Okay so I have two programs to try and make this work. The first one is: DeckLightsPowerOffQuery - [ID 0056][Parent 0001] If Time is 5:15:00AM Then Set 'Outside / DeckLights' Query Repeat Every 15 minutes Else - No Actions - (To add one, press 'Action') Not really sure if I need the IF statement or if the ISY will start running this program when it boots up or?? Then after TexMike posted I did this second one: DeckLightsResponding - [ID 0057][Parent 0001] If 'Outside / DeckLights' Responding is False Then Send Notification to 'D Text' content 'DeckLightUnavail' Else - No Actions - (To add one, press 'Action') It looks exactly like the second post TexMike made with the obvious change of device name. It just doesn't work though. I can go hit the test button of the outlet (trip the GFCI) and wait more than 15 minutes, even an hour and I get no notifications. I can go into the AC and manually query and nothing. If I right click on the device and hit zwave - synchronize or if I just try to turn it on while it has no power then the second program runs and I get the text message. Oh and the GFCI is new. Not saying recent storms couldn't have damaged it, but regardless the ISY isn't seeing the device missing and it isn't powered by this GFCI. Just trying to figure the ISY part out first. Too hot out to sit in the sun and rewire outlets right now anyway. Any other thoughts?

Thanks for the info TexMike! I tried really quick before running out the door this morning. I tried query, but nothing happened. I have to try to turn it on or try to synchronize before ISY will see that it isn't just off, but also off the network. On my phone now, but hopefully I'll have a few mins this weekend to post my program to see if I'm missing something.

Most often when there is lightning.

Ok I have a zwave device that is plugged into a GFCI outlet. When this outlet trips I would like to be notified. I have tried watching for the "unknown" status, but status usually just stays off and the missing device never seems to be noticed. I tried writing a program to query the device every 15 mins to see if it would show the true status then...doesn't work. Anybody know a way for me to get the ISY to tell me when this device drops off the (zwave) network?

This looks like a great idea to me as I'm trying to retire my old raspberry pi that is now only running a very old version of nodelink. I tried to install, but I can't seem to get it to work. Trying to install on ubuntu 18. I made a nodelink folder and in place of the $PWD$ I have /usr/share/nodelink. I'm not well versed in linux or docker so I'm likely missing something simple. After it was made I looked at the container with portainer and the logs say: 2020-07-19T17:03:11.034681729Z checking if NodeLink exists 2020-07-19T17:03:11.043682891Z --2020-07-19 10:03:11-- http://automationshack.com/Files/NodeLink.dll 2020-07-19T17:03:11.107667799Z Resolving automationshack.com (automationshack.com)... 68.65.120.219 2020-07-19T17:03:11.185291462Z Connecting to automationshack.com (automationshack.com)|68.65.120.219|:80... connected. 2020-07-19T17:03:11.275521895Z HTTP request sent, awaiting response... 200 OK 2020-07-19T17:03:11.275555688Z Length: 632320 (618K) [application/x-msdownload] 2020-07-19T17:03:11.275562962Z Saving to: ‘/NodeLink/NodeLink.dll’ 2020-07-19T17:03:11.275613877Z 2020-07-19T17:03:11.510217999Z 0K .......... .......... .......... .......... .......... 8% 295K 2s 2020-07-19T17:03:11.599020602Z 50K .......... .......... .......... .......... .......... 16% 325K 2s 2020-07-19T17:03:11.744566332Z 100K .......... .......... .......... .......... .......... 24% 343K 1s 2020-07-19T17:03:11.822284002Z 150K .......... .......... .......... .......... .......... 32% 647K 1s 2020-07-19T17:03:11.915259575Z 200K .......... .......... .......... .......... .......... 40% 606K 1s 2020-07-19T17:03:11.981893345Z 250K .......... .......... .......... .......... .......... 48% 646K 1s 2020-07-19T17:03:12.058600758Z 300K .......... .......... .......... .......... .......... 56% 654K 1s 2020-07-19T17:03:12.079640403Z 350K .......... .......... .......... .......... .......... 64% 2.31M 0s 2020-07-19T17:03:12.152468236Z 400K .......... .......... .......... .......... .......... 72% 687K 0s 2020-07-19T17:03:12.225882460Z 450K .......... .......... .......... .......... .......... 80% 680K 0s 2020-07-19T17:03:12.277675528Z 500K .......... .......... .......... .......... .......... 89% 966K 0s 2020-07-19T17:03:12.303464756Z 550K .......... .......... .......... .......... .......... 97% 1.88M 0s 2020-07-19T17:03:12.303655804Z 600K .......... ....... 100% 84.4M=1.0s 2020-07-19T17:03:12.303669470Z 2020-07-19T17:03:12.303765169Z 2020-07-19 10:03:12 (601 KB/s) - ‘/NodeLink/NodeLink.dll’ saved [632320/632320] 2020-07-19T17:03:12.303776140Z 2020-07-19T17:03:12.309449237Z --2020-07-19 10:03:12-- http://automationshack.com/Files/NodeLink.runtimeconfig.json 2020-07-19T17:03:12.361280055Z Resolving automationshack.com (automationshack.com)... 68.65.120.219 2020-07-19T17:03:12.439156994Z Connecting to automationshack.com (automationshack.com)|68.65.120.219|:80... connected. 2020-07-19T17:03:12.529202609Z HTTP request sent, awaiting response... 200 OK 2020-07-19T17:03:12.529242103Z Length: 154 [application/json] 2020-07-19T17:03:12.529251290Z Saving to: ‘/NodeLink/NodeLink.runtimeconfig.json’ 2020-07-19T17:03:12.529276668Z 2020-07-19T17:03:12.529342682Z 0K 100% 16.6M=0s 2020-07-19T17:03:12.529374492Z 2020-07-19T17:03:12.529444383Z 2020-07-19 10:03:12 (16.6 MB/s) - ‘/NodeLink/NodeLink.runtimeconfig.json’ saved [154/154] 2020-07-19T17:03:12.529471894Z 2020-07-19T17:03:12.530493321Z starting NodeLink This makes it look like it is running, but it dies right away and portainer status says stopped with exit code 0. Anyone have any tips for getting this running? Thanks

A few days ago one of my zwave locks started acting up and after much troubleshooting with the lock itself I figured it must be the lock that is broken. Now before I bought a new lock for another couple hundred bucks I logged into the AC to see what I could find. I ran a network heal. Then things went sideways. Six or seven of my devices (z wave only though...no insteon devices acted up) were suddenly non responsive. So after the heal finished I rebooted the ISY from the AC. When it came back up the lock was working again! Yay! However, I got this error: There was a thermostat that wasn't talking, but I just removed power from it and when restored the ISY picked it up again. As of now everything seems to be talking. So does the above error point to anything specific? The last couple days of error logs show: Fri 2020/07/10 03:00:41 AM System -170001 [TCP-Conn] -6/-140002, ISY Fri 2020/07/10 03:00:41 AM System -170001 [TCP-Conn] -6/-140002, ISY Fri 2020/07/10 03:00:41 AM System -170001 [TCP-Conn] -6/-140002, ISY Fri 2020/07/10 03:01:10 AM System -140005 Net Module Rule: 38 Fri 2020/07/10 07:16:32 AM System -100 [DHCP] state=RENEW Fri 2020/07/10 12:31:35 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 15 Fri 2020/07/10 12:31:36 PM System -140005 Net Module Rule: 13 Fri 2020/07/10 04:10:07 PM System -170001 [UDSockets] HTTP:32 error:6 Fri 2020/07/10 04:10:17 PM System -170001 [UDSockets] HTTP:34 error:6 Fri 2020/07/10 04:10:22 PM System -170001 [UDSockets] HTTP:34 error:6 Fri 2020/07/10 04:10:27 PM System -170001 [UDSockets] HTTP:32 error:6 Fri 2020/07/10 04:10:27 PM System -170001 [UDSockets] HTTP:34 error:6 Fri 2020/07/10 04:10:32 PM System -170001 [UDSockets] HTTP:32 error:6 Fri 2020/07/10 04:10:32 PM System -170001 [UDSockets] HTTP:34 error:6 Fri 2020/07/10 04:10:37 PM System -170001 [UDSockets] HTTP:27 error:6 Fri 2020/07/10 04:10:37 PM System -170001 [UDSockets] HTTP:34 error:6 Fri 2020/07/10 04:10:42 PM System -170001 [UDSockets] HTTP:27 error:6 Fri 2020/07/10 04:10:42 PM System -170001 [UDSockets] HTTP:34 error:6 Fri 2020/07/10 04:10:47 PM System -170001 [UDSockets] HTTP:27 error:6 Fri 2020/07/10 04:10:47 PM System -170001 [UDSockets] HTTP:34 error:6 Fri 2020/07/10 04:10:52 PM System -170001 [UDSockets] HTTP:27 error:6 Fri 2020/07/10 06:09:21 PM System -100 [DHCP] state=RENEW Fri 2020/07/10 06:59:37 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 15 Fri 2020/07/10 06:59:38 PM System -140005 Net Module Rule: 13 Fri 2020/07/10 10:55:01 PM System -140005 Net Module Rule: 13 Fri 2020/07/10 10:58:01 PM System -170001 [UDSockets] HTTP:27 error:6 Sat 2020/07/11 05:19:36 AM System -100 [DHCP] state=RENEW Sat 2020/07/11 08:38:06 AM System -170001 [UDSockets] HTTP:34 error:6 Sat 2020/07/11 08:38:41 AM System -170001 [UDSockets] HTTP:34 error:6 Sat 2020/07/11 08:38:46 AM System -170001 [UDSockets] HTTP:34 error:6 Sat 2020/07/11 08:38:50 AM System -170001 [UDSockets] HTTP:31 error:6 Sat 2020/07/11 08:39:31 AM System -170001 [UDSockets] HTTP:31 error:6 Sat 2020/07/11 08:52:46 AM System -170001 [UDSockets] HTTP:34 error:6 Sat 2020/07/11 08:58:21 AM System -170001 [UDSockets] HTTP:34 error:6 Sat 2020/07/11 09:18:25 AM System -251001 RX-U 01050048F02260 Sat 2020/07/11 09:20:20 AM System -251001 RX-U 01050048EF237E Sat 2020/07/11 09:22:58 AM System -251001 RX-U 01050048F42365 Sat 2020/07/11 09:25:34 AM System -251001 RX-U 01050048F42167 Sat 2020/07/11 09:25:48 AM System -251001 RX-U 01050048F42365 Sat 2020/07/11 09:37:55 AM System -251001 RX-U 01050046F0004C Sat 2020/07/11 09:40:21 AM System -5012 40 Sat 2020/07/11 09:40:35 AM System -5 Start Sat 2020/07/11 09:40:36 AM System -110022 /CONF/INSTENG.OPT Sat 2020/07/11 09:40:36 AM System -110012 /CONF/INSTENG.OPT Sat 2020/07/11 09:40:40 AM System -110022 /DEF/F6/I1/NLS/EN_US.TXT Sat 2020/07/11 09:41:34 AM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/07/11 09:41:34 AM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/07/11 09:41:44 AM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/07/11 09:41:47 AM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/07/11 09:41:55 AM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/07/11 09:42:05 AM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/07/11 09:42:05 AM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/07/11 09:40:47 AM System -170001 [Network] Established Sat 2020/07/11 09:47:43 AM System -170001 [UDSockets] HTTP:29 error:6 Sat 2020/07/11 09:47:53 AM System -170001 [UDSockets] HTTP:27 error:6 Sat 2020/07/11 09:47:58 AM System -170001 [UDSockets] HTTP:27 error:6 Sat 2020/07/11 09:48:03 AM System -170001 [UDSockets] HTTP:27 error:6 I have the 500 series zwave chip and am running 5.0.14. Thanks

Ok thanks for confirming that. Hopefully I have time to do the swap this weekend...and hopefully it works this time!

Well first things first...I just made a backup of the ISY with everything "normal" at least as far as the ISY can tell. Now on to the keypads. So are you saying even though the keypadlincs can be switched back and forth from 6 to 8 buttons that I can't replace one that started as an 8 button with one that started as a 6? It (the new keypad) did show up with 8 buttons in the admin console and it did do a replace...it just didn't seem to finish. I had never tried the query insteon engine thing that seemed to help early this evening though. I'll likely try the whole replace thing again this weekend assuming I have time. It beats spending $80 on a new one if I can get what I already have to work.

Ok did the checks with device link tables and ended up with the 101010 again as it couldn't write to the keypad. I did query insteon engine and they (the 101010) vanished and then I was able to run the device link table diag. It found two mistakes. I did a restore and it wrote to the keypad. Tested it and it takes between 5 and 10 extra button hits before it will do what it is supposed to. I'm using the admin console to turn on and off various lights around the house and everything works fine. Soooo....I'm going to assume the keypad is just dying. Now how do I go about swapping it out for the new one I have. Would I do anything different than just add it to the ISY and then hit replace old with new? After taking it out of the folder that it is in of course (for anyone who stumbles across this later and didn't know that already). Thanks for all the help. Oops I forgot to mention the unit is a 2334-2 Keypadlinc Dimmer 8 Buttons v.43

Ok so the keypad is not acting normal. I have the keys linked to scenes for lights and fan speeds as well as a basement off program. When I got home last week it wouldn't control anything. I pulled the tab out to air gap it for a bit and after that it would turn on the light linked to the A button, but not off or anything else. I have no load connected to this keypad. The red wire is simply capped in the box. The A button is linked to a scene that controls the light in a fanlinc. After the whole thing last weekend it was back to normal for a few days. Now it seems random as to what works and what doesn't. The backlight is odd and doesn't correspond with the scenes. I can control other insteon lights from my phone so I assume the plm is okay also, but not sure why I can't write to the new keypad. I'll try the diagnostics when I get home tonight. I did try a restore last weekend, but that didn't work. It was only after I tried the replace with the new keypad and then went back and did a second replace with the old one that it began to work again.

TL;DR: keypadlinc went stupid. Tried to replace with new. Couldn't get new to take programming. Put old back in and it worked...for a week and went stupid again. Tips? So of course while out of town for work last week my 8 button keypadlinc stops working. When I get home I grab a 6 button new in the box and hook it to power factory reset it and did the hold a and h button thing and covert it to an 8 button. Added to isy and it popped in all 8 buttons. Went into the admin console and hit replace old with new. Well it took off and looked like it was going to be fine so since there was a lot of info to write I walked away for a few. When I came back the little green icon of 1010101 was beside all 8 buttons. So I hit write changes and it started saying writing to, but then when I looked at what it said it was writing to it was zwave devices and nodelink stuff...not the insteon address of my new keypad. So it never wrote to the new keypad. I tried it and only the main (A) button did anything which you would think is normal, but I don't even have a load connected to the keypad. It's linked to a fanlinc and it turned that light on, but not off. So I wired up the old keypad to power and did the replace back the other way and it worked fine again so I reinstalled it. Now it has gone goofy again and isn't working right. No other issues with any of the insteon in my house. Anything anybody can suggest I try with the new keypad to get it to work? Do you have to have an 8 button to replace an 8 button? The new one showed 8 buttons in the AC and let me hit replace. Could this be the plm? I'm grasping at straws now. Any help is appreciated.

Well I feel silly. I looked at polyglot and it said connected, but it wasn't. I restarted it and the program worked. I tried a couple different things and I stopped on less than 1% when I thought of restarting polyglot, but I think my original program would work. Just FYI the decimal places were the only option.... I didn't add them all. Thanks for the reply.

Running polyglot v2 with the Hue nodeserver and in the AC I can see the status of the bulbs. I have two lamps on my headboard and a 6 button KPL in my bedroom where one of the buttons toggles a scene. I'm trying to turn off that scene (MasterHeadboardLights) when the bulbs are (both) off. I made a program that says: MasterHeadboardSceneOff - [ID 002A][Parent 0001] If 'Hue Bridge / Left Light' Status is 0.0000% And 'Hue Bridge / Right Light' Status is 0.0000% Then Set 'Upstairs / MasterHeadboardLights' Off Else - No Actions - (To add one, press 'Action') But it doesn't work. What am I missing? I can use my phone to turn the scene on and off and see the KPL key light up and go dark. Running 5.0.14. Any thoughts? Thanks

Glad it helped

Try looking at this thread:

That would be great. Thanks for the help on this.