
oper8
Members-
Posts
47 -
Joined
-
Last visited
Everything posted by oper8
-
No harm done and sorry for my show of frustration. I might open a ticket with Universal Devices on this. Thanks,
-
I was referring to the pulldown menus in ISY, not the thermostat. Anyway, never mind. I see nobody does understand my problem. I'll leave it be. Thanks all ! Issue closed.
-
Thank you for the help. This can be more than just a Z-Wave topic. See attached a screen from the same system but showing a Insteon thermostat mode 2441TH. ISY is reporting the temperature properly, with one decimal, in this case 21.5 C, the thermostat is actually showing the round-up integer temp of 22 C on its display, and on the ISY there is no way to set the thermostat to a temp. with one decimal, the drop down temp scale is only showing integer numbers. Anyway, it's not something very critical, but more of an annoyance for us users outside US not using the USCS measure system. It would be great if these issues could be fixed.
-
No, this is the temperature reported by a Z-Wave thermostat. Model is GoControl GC-TBZ48. I'm attaching a screen. You see the temperature in Celsius in integer number, but the thermostat can display or set the temp in Celsius with one decimal. I think it can do increments of 0.5 C. I would need the capability to be able to program the thermostat via the ISY in increments of 0.5C for better resolution.
-
mmb, I highly appreciate your help, can you be more specific ? what "variable row" ?
-
I'm using ISY version 5.3.4 with Z-wave support and I want to know if I can display my thermostat temperature - and accordingly, use in my programs - in Celsius with one decimal. My z-wave thermostat is reporting the temperature with one decimal, in Celsius, but the ISY console can display only the integer number.
-
Schlage 469 Locks, Aeotec Gen5, 6 repeaters Z-Wave issues
oper8 replied to JTsao's topic in Z-Wave - Series 300/500
This is extremely helpful ! Thanks wingman1487 ! I did not know I can see the z-wave routes and nodes information. This can explain a lot of issues and can help troubleshoot the z-wave mesh. In my case the Schlage lock connects via 2 other nodes before reaching ISY. -
Schlage 469 Locks, Aeotec Gen5, 6 repeaters Z-Wave issues
oper8 replied to JTsao's topic in Z-Wave - Series 300/500
I have only one Lock now, the second was a constant pain and I took it off. As for repeaters, yes I have one Aeotec in between but I presume the lock connects directly to ISY - I have no way to see this with ver. 5.3.0.... -
This is very helpful. I have over 40 of these z-wave nodes, I placed them in a separate "NOT USED" folder so they don't clog my AC interface. So it's perfectly fine and safe to delete them ?
-
Schlage 469 Locks, Aeotec Gen5, 6 repeaters Z-Wave issues
oper8 replied to JTsao's topic in Z-Wave - Series 300/500
I had nothing but trouble with the Schlage BE469ZP Lock. Stay away from this version. I also have a BE469NX and it does work perfectly fine. -
Status Unreliable after ISY Query of Z-Wave Battery Operated devices
oper8 replied to WFP's topic in Z-Wave - Series 300/500
From my own experience, I don't think this is a broken mesh issue, but rather some sort of "incompatibility" with particular z-wave devices, in special with the (in)famous Schlage BE469ZP Lock. I have two of these locks, one is the older model BE469NX, firmware ver. 0.8.0. This older one responds perfectly fine to query, does also show the complete menu in the AC, zero issues. The newer BE469ZP is responding "UNKNOWN" to query and the menu is missing the "options" tab. I tried everything possible with this lock, installed it at 10 inch distance from ISY, downgraded my ISY firmware, remove it, add it, remove it and add it again.... hours of painful tests.... same result. As such I gave up on it, found an older 469NX on eBay and I hope it will solve this issue. I also forgot to mention, the older one is farther away from ISY. I have a clean network with lots of wired devices (repeaters). -
This is a very cool workaround ! I will try it to fix the same problem with reporting the temperature real-time.
-
I experience the same issue. Running ISY 5.3.3 The thermostat is responding to my programs, I have one that is changing the heat (or cold) setpoint at different times during the day and one that is turning the fan to "on" or "auto". The problem is with the current temperature reporting through ISY. It doesn't update real time. Must do a query to show the current temperature.
-
I will rather wait. Maybe a new version will fix this. So far everything is working with the "crippled" lock, but working. I have at least a dozen new devices added since 5.0.16 and lots of new programs and scenes. It will be almost like rebuilding my entire network. Note for self: never jump in upgrading to bleeding edge new version until all the bugs are identified and fixed.
-
Hi lilyoyo1, How did you go back to 5.0.16 ? I installed several new devices since 5.0.16 and my last backup on that version does not have them. Will I have to join them again ? I'm quite nervous about the downgrade, but I would very much want to go back to that version. I really don't like how the z-wave devices are showing with multiple nodes in 5.3.3, lots of things don't make sense, it's all super un-friendly and counter intuitive.
-
Sorry Michael, I have to report that I opened a ticket indeed but got nowhere with it. The recommendation that came from your support was to go back to 5.0.16C I'm quite disappointed and I now regret upgrading to 5.3.3 Everything was working fine for me with 5.0.16C. And I don't know if going back to the older ISY firmware will not cause more trouble....
-
More on this. Not only that "Options" are no longer available in the new 5.3.3 but there is something wrong in terms of communication. I have two locks fairly close to each other, one that was installed with the previous 5.0.16 version, showing Options and all and no comm. errors. The second lock was recently installed under 5.3.3, I'm missing "options" and showing some strange comm. errors when query. The lock works but it seems unreliable with these errors. I added the Aeotec gen 7 repeater and there is ZERO improvement. Is there any chance the 5.3.3 will be fixed or is there a way to go back to the older 5.0.16 firmware that was working better ? Here is the event viewer log with the errors: Tue 04/13/2021 08:20:43 PM : [ZWAVE-TX ] ... Tue 04/13/2021 08:20:48 PM : [ZW-TX-FAILED] enc=Ok uid=36.0 cmd=0x62.02 DOOR_LOCK Tue 04/13/2021 08:20:48 PM : [ZWAVE-TX-E ] ZWAVE-WAIT Waiting for retry 1 of 2 Tue 04/13/2021 08:20:48 PM : [ZWAVE-TE ] [62/02] CC=0x62 cmd=0x02 [] ACK,AUTO,EXPLORE To=0x24 Tue 04/13/2021 08:20:48 PM : [ZWAVE-TX ZW036_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x24 Tue 04/13/2021 08:20:50 PM : [ZWAVE-RX ZW036_1] [98/80] Security Nonce Report - nonce=[7D51F33F450FF722] ACK,AUTO,EXPLORE From=0x24 Tue 04/13/2021 08:20:50 PM : [ZWAVE-RX ZW036_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x24 Tue 04/13/2021 08:20:50 PM : [ZWAVE-TX ] ... Tue 04/13/2021 08:20:54 PM : [ZW-TX-FAILED] enc=Ok uid=36.0 cmd=0x62.02 DOOR_LOCK Tue 04/13/2021 08:20:54 PM : [ZWAVE-TX-E ] ZWAVE-WAIT Waiting for retry 2 of 2 Tue 04/13/2021 08:20:55 PM : [ZWAVE-TE ] [62/02] CC=0x62 cmd=0x02 [] ACK,AUTO,EXPLORE To=0x24 Tue 04/13/2021 08:20:55 PM : [ZWAVE-TX ZW036_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x24 Tue 04/13/2021 08:20:56 PM : [ZWAVE-RX ZW036_1] [98/80] Security Nonce Report - nonce=[AF5601DFC582273E] ACK,AUTO,EXPLORE From=0x24 Tue 04/13/2021 08:20:57 PM : [ZWAVE-RX ZW036_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x24
-
Yes, I have UI and F/W both showing "Insteon_UD994 v 5.3.3". Done more research into the issue and it seems it all about z-wave having communication issues. I have over 20 z-wave devices, including 2 Schlage locks, plus over two dozen Insteon devices all working together. Performance is 99% but with only these odd z-wave issues caused only by the battery powered devices. I just added a AEON repeater but did not see a significant improvement. I'm looking at better ways to heal the network, the current ISY version does not have the whole network healing feature as before. I'm also looking at more advanced ways to troubleshoot communication issues. I hope a newer ISY version might address this. I love ISY and want to continue to use it but moving more on the z-wave devices and retiring the old INSTEON items.
-
I have the same problem. Just added a new BE469ZP, Firmware ver. 0.11.0 I'm running ISY on 5.3.3 I don't have Options showing for the new lock and also, what is most concerning, the status of the lock is showing "unknown". I can control the lock from ISY and I can also change the user password. But I cannot retrieve the status and also see the options to be able to change them. Is there a fix available ?
-
What happened to HEAL & REPAIR with the new dongle & 5.3.2?
oper8 replied to Cottonwood's topic in Z-Wave - Series 300/500
Same with my 5.3.3. I see only "Synchronize Nodes" -> "New & Deleted" or "All". -
CLOSED --- Z-Wave 500 Series Beta
oper8 replied to Michel Kohanim's topic in Z-Wave - Series 300/500
I run with the 500 series board and all my z wave devices are 500 series. Is this board compatible with the new 700 series Z Wave devices ? And is there a plan to provide an upgraded 700 series ISY controller board ? -
I left it on and now it does load the value in the variable. It seems it's working but I don't 100% trust the number. It's showing 81%. It was installed 2 years ago... I'm slowly retiring the INSTEON devices. I see not much future with them. I'll be moving all my devices to Z-Wave. And I still want to continue to use ISY. I love it.
-
I tried the program presented by ELA and I don't get the value of the battery level loaded in the variable I create for the notification. I don't think the motion sensor is reporting the battery level in any way.... I might just give up on having a program notify low battery and just change it every 2 years max. I hope a higher capacity CR123A can last for 2 years on a normal use.
-
Upgraded from 5.3.2 to 5.3.3 and everything works perfectly fine. I can also say the response time is better (faster) for all devices, not only z-wave.
-
Update on this issue: No more problems, the parameter change is transmitted perfectly fine to device. I pressed "Set Configuration", the "Write changes", then "Query" Thanks for the help !