heardc

I have an mqtt topic in frigate set as a switch: - id: "drivedet" name: "driveway detect" type: "switch" sensor_id: "detect" status_topic: "frigate/driveway/detect/state" cmd_topic: "frigate/driveway/detect/set" I can set this to True or False in the admin panel or a program, but when I query the node, the message gets deleted in MQTT Explorer and the setting in Frigate goes to False. For now this is the reason why I am not going to use or rely on the MQTT Node Server and use python network resources instead. Can't risk the eISY running a query and wiping out all the topics. Is there a way to not allow this to happen?

Pushover is totally worth it. Keeps your notifications separate and is much more reliable.

Latest version of 5.9.1 behaves way different and largely far better than previous versions. 12 hours in after launching migration, I am up and running with eISY. Nice to have a FreeBSD box to work with. Half of my battery devices required exclusion and inclusion. Rest commands to configuration parameters do not work due to https protocol, which is sad but not vital. Zwave response is shockingly fast. Time will tell on stability.

Found the problem. An "Access Control Alarm [S0]" got added to the node list and was buried. This Node allows for programs to use status that includes manual lock, keypad lock etc.

I installed three of these deadbolts 10 years ago, they have been working with the ISY 994 nicely. Just installed the EISY today. The Yale deadbolts are showing up as status only. No settings for the difference between manual lock, key lock, or keypad. Anybody else see this? I am hoping that an exclude, and include will solve it. Sent from my iPhone using Tapatalk

Has anyone tried using Aeotec or similar USB Zwave stick in the eISY instead of the $120 combination dongle that I purchased? I’m starting to wonder if that thing is totally incompatible with my 10 yr old zwave network comprised of mostly 300 and 500 series devices.

Update on this: I heard back from Tech Support to Update Packages, did that, firmware stayed at 5.9.1. Got much further in the process, but still all wired devices disabled and non functional. Battery devices stuck in a never ending Network Heal / Finding neighbours loop that I had to kill after 6 hours of no progress. Why try to find neighbors of battery devices if they are likely asleep? Each device has 4minutes allocated to find neighbors, I tried waking them up after seeing status to that effect, still didn't help.

I did not ask and will do that.

No offer has been made by UD to send the unit back. I’m stuck with it and am praying that UD figures it out with new firmware. Not being able to roll back to a previous firmware is pretty bad. Peplink routers are spectacular for this single reason. In the meantime I will be turning a Lenovo Tiny PC into a Home Assistant box for at least an NVR and at most, a replacement to my dead eISY.

After 10 years with the ISY994, I decided to get the eISY and give it a shot. Had multiple hardwired computers spread out on the table, printed my migration instructions, fully rested with 8 hours available to do the work. Assumed that 15 battery devices would require Syncing, and was hopeful that the new unit would recognize the other 100 wired devices. I made one critical mistake which bricked my eISY. I clicked the “upgrade packages” button not knowing that this was actually a big firmware update from the stable 5.8.4 to 5.9.1. Apparently 5.9.1 doesn’t allow for migration with zwave for some reason and if I was made aware that upgrade packages meant a massive re-wiring of the firmware, I would have declined the offer. After Restoring IoX from the ISY994 backup, every zwave device is disabled with a red circle/slash. After enabling a device, syncing fails for all of them. The eISY is back in the box and I have submitted a ticket. Apparently I am not alone. Do not “upgrade packages” before doing a zwave migration!

Update is now available on the App Store and appears to work!

Hey I love my 10 year old isy994 too but am getting tired of having to reboot it every 3 weeks, fighting with Java and windows admin access and UD Mobile synchronization unpredictability. Does any of this stuff get better with eISY? If not, I may take the massive leap to Home Assistant.

I experience the same thing last night as well. Rebooted, resynced, no change. Submitted a ticket and got a reply saying that a new update to UD Mobile is about to show up on the App Store.

With Adding Secure Devices set to Yes.

Can’t get the device to include successfully. Sent from my iPhone using Tapatalk