cyberk

Thanks for the feedback, no backup so I guess i'll just start from scratch.

Hello Team, For various reasons, we had to do a factory reset on our Polisy. I got it back up and running, installed my old polys, but now I have no idea how to link them to the existin entries in ISY After connecting the Polisy to the ISY, it imported the node server entries that were configured on the ISY, as unmanaged. How do I get these back in a managed state and link them to the Polisy? Many thanks in advance

so i figured i'd post in here in case anyone has a solution before I continue to troubleshoot with UDI. Short story, after updates I can no longer ssh in with admin/admin These are the steps I followed - ssh into Polisy - run command curl -s https://pkg.isy.io/script/update121.sh | sudo bash sudo shutdown -r now - reboot Polisy - run command cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now - reboot Polisy - run command sudo pkg update && sudo pkg upgrade - reboot Polisy - no longer able to SSH in, admin/admin no longer works. No web page on port 80 or port 3000

Has anyone on the 500-series chipset tried to receive primary back to the ISY, as in you have another primary controller, and you're trying to make the ISY primary...?

Pretty sure the ISY can only support one active portal at a time. Have you tried disabling the mobilink portal and seeing if that re-enables the ISY portal? Sent from my iPhone using Tapatalk

@blueman2 Review the documentation for your Z-wave devices. Each device has its own set of parameters and association groups. Different association groups do different things, but usually, every zwave device has at least one association group, and that is the lifeline group. The nodes in that group are the ones that will receive instant status of changes, although from what I understand, they’re no longer needed in zwave+ (500) devices since they all support HAIL by default. So it’s possible your devices have 2 association groups, and that each association group does something else. But we won’t know for sure until we see the documentation for that specific device. Sent from my iPhone using Tapatalk

Thanks for the heads up, I went ahead and enabled the “Freeze ISY Nodes” option, hopefully that helps alleviate the issue. I guess my issue is happening with Aeotec Multisensors, I was going to test more but you saved me time Sent from my iPhone using Tapatalk

Not from what I've seen or read, UDI has confirmed this is an issue in the past, however, it could be with openzwave and not necessarily UDI. There's an experiment I need to perform to see if i can view the ISY secure key in the other controller, I need to get around to it. On other news, I am seeing that for every "Synchronize nodes All" that I initiate, random ghost sensors get created each time, not a lot, just a few each time. I'll have confirmation on this from another ISY sometime tomorrow, but if anyone cares to test in the meantime, that'd be cool

@Michel Kohanim

Just a heads up, although this was an existing issue for us prior to the beta, it looks like joining the ISY to an existing z-wave network still doesn't allow communication with already existing secure z-wave devices. If anyone has the ability to test this, I'd like to see if the issue is widespread, or just limited to open-zwave.

I didn't see an entry for the 500 series beta in the wiki, so I went ahead and created one. Those of you with access to maintain the wiki, please feel free to update it as needed.

If you ask me, if it’s going to help development, the price should be increased. Michel, charge me $50 a year! Sent from my iPhone using Tapatalk

Ah ok, I figured it had to do with amazon, google, and Microsoft deploying those fixes on the bare metal hosts, and the compounding effects of the same fixes on the virtual server. The biggest performance hits are to database servers and others with heavy file-Io. I also believe network IO is taking a hit in some cases. Thanks for making sure out Alexa/Google Home calls keep working! Sent from my iPhone using Tapatalk

Sounds like specter and meltdown are to blame! Lol Sent from my iPhone using Tapatalk

Thanks Benoit! Any chance you can make it so that the default on function for a fanlinc motor is “high”. If I tell Alexa to turn on the motor on a fanlinc, she replies without an error, but nothing happens to the motor. If I tell her to set it to 100%, it goes high. Sent from my iPhone using Tapatalk