hart2hart

Blue man in post above gave the number to look for in AC administration Console. The move from 4.8 to 5.0.16 requires planning and time dedication. The technology has changed a lot in last several years. UDI is working to get you there but it can’t be painless migration between 4 and 5. I’ve been on 5.0.15 for about a year and it’s fantastic. I posted a how to guide which I’ll locate and point to in the next post.

1. 300 series Zwave board has a blue led on back of case. You can also look at AC under zwave and their is a number that tells you. 2. You should stay with 5.0.16 rc1 until you upgrade board to 500 series 3. See above, 5.1 RC2 and 5.2 RC3 are not recommend with 300 series board. Many people had terrible migration issues issues from 5.0.x versions. 4. You should upgrade to 500 series board before you move to 5.1 or 5.2

This is way in the weeds about zwave plus but my Schlage BE469 deadbolts are version prior to the BE469ZP versions. Any issues with them on 500 series board? Any reason to consider replacing them? They are the only two Zwave devices I need to have stay near 100% reliable.

Thanks it is battery operated so if I understand you that makes it a receiver only so not part of the mesh. Thanks. Whew! Bullet. dodged. Lol Is there a guide here that shows how to move from 300 to 500 series board? I’ve had a mini note since I first installed zwave board. As I recall I have to transfer control over to it to start process but that’s about all and that may be dated information.

As you can tell, I know nothing to very little about how zwave works. Is it still not a problem given that this vent is the closet zwavevdevice to the ISY?

All my devices are zwave plus except this vent. https://products.z-wavealliance.org/products/1044 Used to only allow AC but not heat to blow into AV equipment room. There is no replacement I can locate using any technology. What issues could it cause in zwave mesh?

Not what meant. Can you look on ISY console and see zwave devices including which generation/series they are from. I know that the board is 300.

I’m not home now but curious if you can look at ISY to determine which are series 3 and series 5 devices.

I answered this one time in the same way and was corrected. The essence was you could install 5.0.16 FW and restore a 4.x backup. The newer firmware had conversion code to move forward older backups. I’d still be inclined to put 4.7 FW back on and restore backup up to it then upgrade to 5.0.16. Too many variables doing it the other way. I would not attempt to restore a 5.1 backup to 5.0.16 FW.

Post deleted by author.

When I first saw release notes for 5.1.0, I feel certain it said that toggle to external antenna had been re-enabled. Two questions: 1. Is that true since not finding that note now? 2. Does 500 series board have external antenna connector? My ISY is in an RF intense area so getting zwave antenna away is a must which I did with 300 series board. I also do this with an extension cord for PLM.

I added 2nd Ring Outdoor Cam with existing cam and doorbell. The cam motion node is not showing in PGC or obviously ISY. I’ve stopped and started node several times. If delete and add back is required will I need to redo folders ring associated programs?

I'm still running 1.1.0 based on everything in the gui and in the log. Might explain why its not worked in weeks. How do I get the Ring PGC node server fixed? Thanks.

An older dimmer (10 years) started reacting to every near switch or dimmer (on or off) in that as it saw signal it would turn off and , pause couple seconds and then go. At the bad switch it would same thing. Already replaced hw and links via ISY. I keep a supply of sale days dual band replacements on hand. Anyone else seen this behavior? Mine have just always stopped responding as in power supply dying or dead —capacitor plague. Lol

I’ve seen this come up many times. I’ve speculated that one could: 1. Install regular dimmer in wall without load control from step 2 2. Use wires running to box from ceiling to create full time power to dimmer in box 3. Install micro dimmer/relay in ceiling to control light without direct control circuit to switch 4. Put micro module and dimmer in a scene I haven’t drawn this out or thought it all the way through but submit for consideration.

Did the addresses correct when you reloaded the console?

Admin Admin

Lights have two methods to evaluate state of the light. Status of a light — if light state is on/off Control of light —- if light is switched on/off Control is only true when a device enters that state and status is true while device is in that state and this leads to very different results when combined with and or in the same if. Does thermostat have status and control? Not where I can try it. Edit: Arrvied home and thermostat supports both, so if I recall the original question you could use if xxx-Heat is Switched Off which equates to using Control Vs Status. Sample of how they look follows: Test:Heat State - [ID 0124][Parent 0067][Not Enabled] If 'Basement / Basement:Thermostat- Heat' is switched On And 'Basement / Basement:Thermostat- Heat' Status is On And 'Basement / Basement:Thermostat- Heat' is switched Off And 'Basement / Basement:Thermostat- Heat' Status is Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

Please Copy them to clipboard and then post as regular text. Others may have utility to read this but many likely won’t.

Thanks. I'll implement the LD naming convention.

I know things are moving very fast including an unexpected office move and shipping out Polisys. Any update from UDI on the issues reported with Schlage locks?

To be sure I understand, the direct ip option does not include 14 day trial?

Do you have any else branch in the program that turns the fan on that is turning it off?

I had similar problem and solved it by deleting MobiLinc and adding it back to the device.

4.x has been the official branch for a few years. UDI has been updating the underlying architecture and working towards Z-wave certification in the 5.x branch. 5.0.16 (rc1) is solid and there is no reason to hold back. I was very conservative but made the move in June to 5.0.15A. Not a single issue.