
tlightne
Members-
Posts
375 -
Joined
-
Last visited
Everything posted by tlightne
-
@Geddy I did perform the update to 5.5.7 this morning. I also have had a ticket open since issues that surfaced with 5.5.5. I have been updating the ticket with the same info as here that way others with the same hardware are aware of the issues before migrating.. I know UDI has been working very hard to get all the issues resolved and I thank them for that. Just a little frustration showing up I am over that tonight.. Thanks for the response..
-
Upgrade to 5.5.7 Brought me nothing new. Open closed Sensors no change still report on and off not open close at least they are reporting. I have lost one of my Quickset 916 Locks. When I did an update no change when I did an update with interview is removed the only working nodes and added Entry Control Node. So I did an exclude and include the only node it loaded was Entry Control which is a blank node. On teh two remaining Quickset locks that remain Lock Access Control does not update. This worked in 5.5.5. First alert Smoke Combo will not include. First Alert Smoke reports numbers not text. Guess I will wait another week and see if it is my turn in the Que....
-
@Chris Jahn After upgrading to 5.5.6 Noticed today my Quickset door locks are no longer updating the Access Control Node when I lock or unlock the locks. I have three of them and none are updating. This worked as designed with 5.5.5. I did an update and nothing changed. Next did a update with interview and the Access Control node no longer shows up in AC. I updated my UD Ticket with this info and the DH Command Class from one of the devices. After upgrading to 5.5.6 That did fix the two Philio PAT02-2B Zwave Plus sensors now report temperature as Fahrenheit. I am still having issues with First Alert Smoke Detectors 1st (Not Zwave Plus) reports V1 Alarm Type as 13, V1 Alarm Level 255, and does report Battery Level. Second First Alert Combo Smoke/CO Detector (Zwave Plus) Includes two nodes one node is V1 Alarm and has V1 alarm type, V1 Alarm Level, and Battery Level and the second node is Wake up. It never completes interview in X-Ray. It has installed 5 different devices all with this same node names. I pulled the battery to stop it from adding Nodes. I did a Factory reset on the device and it automatically starts inclusion mode in the Polisy. It never updates the values in any of the nodes it created. The (9) KAIPULE Z-Wave Plus Wireless Door Window sensors that when door is open it reports as "On" in Polisy but when closed it reports as "Off" not closed. Thank you
-
PG3x stuck at login after eisy credential reset
tlightne replied to SteveBL's topic in Polyglot v3 (PG3x)
Open a ticket with UD.... -
@Chris Jahn @bpwwer Did the upgrade to 5.5.6 and I can not get PG3 started. I SSH into polisy and tried to run the command from @briansbut I get a permission denied. I am not a guru so any help will be appreciated.. EDIT: After clicking on Update Packages a second time PG3 has now restarted...
-
@Ricka2 Even if you have a brand new device it is best to do a remove on it before doing an add.
-
Did you do a remove on the fan controller before trying to do the add... You need to clear it first before trying the add..
-
Did you run a backup before migrating to Zmatter? From what I read in other posts you can restore a backup taken before the migration.
-
Upgraded to 5.5.5 could not get Zwave add or remove to start after hitting button. Pulled the plug on Polisy and after a reboot all seems to be ok now. I am still having issues with First Alert Smoke Detectors 1st (Not Zwave Plus) reports V1 Alarm Type as 13, V1 Alarm Level 255, When Smoke it detected it reports V1 Alarm Type as 1 and V1 Alarm Level 255. When hitting Test button on detector V1 Alarm type id 12 so it looks like it is reporting a Binary Alarm type. It does report Battery Level. Second First Alert Combo Smoke/CO Detector (Zwave Plus) does not report any status for CO Alarm, Co End of Life, Smoke Alarm, Test Alarm, and Smoke Detected all of which reported with Zoozs 700 Dongle. It does report Battery Level, System Alarm as Heartbeat, and its a wake status so it is communication with the Zmatter Board. After removing and readding the (9) KAIPULE Z-Wave Plus Wireless Door Window sensors I picked up a new node called Binary Door/Window Sensor, This reports On when Window/Door is opened and Off when closed. The Access Control node still reporthat when door is open it reports as Open in Polisy but when closed it repots Open when Window/Door is open but Idle when Window/Door is closed. As Chris reported did not have time to impliment the F/C fix this update so the two Philio PAT02-2B Zwave Plus sensors report in temperature as Celsius and the default is Fahrenheit. Awaiting the next code update.
-
@Chris JahnIs the glitch in the Build just PG3X or also PG3? I am holding off 5.5.5 until I hear back. Thank you
-
@bradshawkyle I am considering moving from a Nest to a Honeywell thermostat. What model Honeywell Home are you using? Thanks...
-
Just updating here my progress... Update: As of 01/29/2023 @ 13:51. All Original devices are now connected to the Zmatter Network. I had to uninstall the Eaton recepticle move it closer to the Polisy then it included in the Zmatter network. I am still having issues with First Alert Smoke Detectors 1st (Not Zwave Plus) reports V1 Alarm Type as 13, V1 Alarm Level 255, and does not report Battery Level. Second First Alert Combo Smoke/CO Detector (Zwave Plus) does not report any status for CO Alarm, Co End of Life, Smoke Alarm, Test Alarm, and Smoke Detected all of which reported with Zoozs 700 Dongle. It does report Battery Level, System Alarm as Heartbeat, and its a wake status so it is communication with the Zmatter Board. Both Smoke detectors have been in the Zmatter network for over 24 hours. The two Philio PAT02-2B Zwave Plus sensors report in temperature as Celsius and the default is Fahrenheit. Tried to change the configuration but it will not change. The (9) KAIPULE Z-Wave Plus Wireless Door Window sensors that when door is open it reports as Open in Polisy but when closed it reports as Idle not closed. I am hoping the next Firmware update will pickup and fix these.
-
@tazmanThanks for the update. I assumed someone already had a ticket opened but I thought the more the marrier....
-
I completed the migration to Zmatter yesterday.I few of my devices migrated with no issues however I have (9) KAIPULE Z-Wave Plus Wireless Door Window sensors that did not upgrade from the Zmatter install. I did an exclude and reinstall and the did show up. However when door is open it shows Open in Polisy but when closed it shows Idle not closed. I cannot get notified when the door or window is closed. I also have (2) Philio Zwave Plus Temperature and Humidity sensors and two First Alert Zwave Smoke detectors that will not include into the Zmater network. I see them go into the interview process but never get added. UPDATE: I also have 1 Eaton Zwave Plus outlet that I can not get included in the Zmatter network. I have excluded it both through the IOX and it also has a factory reset which excludes it from all settings. I have opened a ticket with UD support but thought I would put it out here as well.. Firmware is 5.5.4. Ploisy with Zmatter... Thank you
-
Is there a way to do mass-enable/disable of programs?
tlightne replied to waffles's topic in IoX Support
-
Did you unplug the power and wait a few seconds then repower your Polisy?? Just doing a backup should not make your Polisy go offline..
-
@bpwwer stated earlier there are issues with eisy and Pg3 a new level of Pg3 should be out next week.
-
Ambient Weather Node Server no longer updating on IOx
tlightne replied to tlightne's topic in Ambient Console and Weather
Thank you I guess I will try a delete and reinstall. I did a reinstall but did not change anything. Thanks again... -
@bpwwerAmbient Weather Node Server is blank on my IOx (Polisy). It has been installed and running fine for several months. I did a reinstall this morning and it is still not updating on Polisy. I have restarted the Polisy, and restarted PG3 and still same problem. I have attached PG3 log and Ambient Node serverLog. AmbientWeather_12-15-2022_90145-AM.zip pg3_12-15-2022_90005-AM.zip
-
I would start with replacing the power supply. I had to replace mine last summer.
-
Ambient Weather NS Not Updating to 2.0.7
tlightne replied to mbking's topic in Ambient Console and Weather
@bpwwer Just tried the restart and still shows version as 2.06 but like I said low priority for me... -
Ambient Weather NS Not Updating to 2.0.7
tlightne replied to mbking's topic in Ambient Console and Weather
I have the same issue but since everything was running ok it was low priority... -
Is there a limit on the number of messages that can be created?
tlightne replied to tlightne's topic in Notification
@Jimbo.Automates Got it Thank you.... -
Is there a limit on the number of messages that can be created?
tlightne replied to tlightne's topic in Notification
@Jimbo.Automates There is no message after 144 but there is a blank section for a message. How do you delete messages in the configuration? I have figured out how to do short custom messages so I can get additional messages that way at least for now. Thank you -
Is there a limit on the number of messages that can be created?
tlightne replied to tlightne's topic in Notification
@Jimbo.AutomatesAttached is the log file. I am not really very good at programing so I found it easier just to add them to Custom Typed Configuration Parameters in the configuration in the node server. It lets me enter them in and save them they just will not show up in the IOP. Here is an example of my programs: Notification_11-9-2022_14918-PM.zip