firstone

Authentication works for me on pg3, which is where I've originally tested it, but not on pg3x. I will take a look. As far as updating, I don't think I can help with that, other than removing and installing fresh. But wait until I fix authentication.

I've had it running on VM but not working. IoX acted wacky. Couldn't set time zone, for instance. And didn't see PLM. Had a conversation with UDI and they weren't interested in porting to VM at the time. Perhaps if there's more demand, they might change their mind in the future. But 1. A lot of people here seems to like idea of having separate box for separate things. 2. Support would likely be an issue. It's one thing to support known hardware / known firmware. Another thing to support all various configuration variants.

I cannot comment on other node server but I recommend it because I've changed how data is saved in this version. Better to start clean.

This was the issue with PG3x, specifically. It is fixed now with latest update.

Can you PM logs to me, please. I will only be able to deal with it next week though. Maybe try remove and clean install if you haven’t already.

It should work on Polisy with PG3 3.1.18. If you're not on that version, please, update and make sure you restart. If you are, turn on debug logging, try it and PM the logs. I've tested it and it should work.

Are you on eisy or Polisy? I've prematurely released the fix that works with pg3 but it hasn't made it to pg3x yet.

It's might be standard for console but not necessarily for PLM. There is a post that someone used to convert console USB adapter by re-crimping RJ45 connector. Search for it. There are only 3 wires I think. You should be able to crimp this cable if you know how.

Hue node server is awesome and integrates very well into ISY scenes. It's not a native scene like Insteon but is still great. Keep in mind that hue lights pretty much need constant power. Otherwise, they will take a while to respond.

There is an option to purchase available now in Production store. Through I'm still working with UDI on automating setup and not requiring ssh manual steps.

Synchronize should create IoX nodes for devices that are in zwave controller (which is kind of independent from IoX). Those could be devices that were added but failed to interview and/or create IoX nodes. Those could be devices that you've removed from IoX without properly removing them from zwave controller in the past. Synchronize with Interview means that same as above, except Interview attempt is done for those devices. If they're added "with Interview" that likely means interview is done and those are valid nodes of actively responding device, rather than some stale old devices.

Just remove that one and go to "non-production" store and install from there. If you have issues with discovery with that version, PM the logs to me.

My fallback plan was to use stick with HA just for locks. And it works fine except writing user codes requires a bit of work. But then Chris fixed it for me. It really sucks that newest update seems to break locks. I'll wait to update until issues are worked out.

If you're using version from production store, I'd suggest fully removing and switching to beta version. But, also, make sure you enable Chromecast in config first. Edit: Are you using it in PG2? I haven't touched PG2 in a while. It used to work before.

Thank you. As a programmer I find the idea of copying the same thing distasteful. I have this script working in HA with ISY devices perfectly well. Just list of devices and fires e-mail when state changes. I don't see why IoX cannot do the same.

I've seen some programs in another post that basically triggers 26 hours countdown on detecting heartbeat. If I understand it correctly, every day the program time counter would restart upon receiving a refreshed heartbeat. While it technically works, I 1. Cannot combine the same program for multiple devices. 2. Because it fails by timer rather than device, I cannot use variable substitution for notification. Thus, if I have 10 devices, I need 10 program and 10 separate notification. And if I get more creative with state variables, I need 10 variables. Does it seem like an overkill? Why wouldn't program just get triggered by state change? The Heartbeat node DOES get updated correctly (to no state from On). Why can't it trigger the program? What am I missing.

You will, unfortunately, need to use pre-ZMatter backup to go to stick But I can tell you that it works. As does Chris's fix.

Did you do anything with those locks after update? Recreate links? Re-enroll? Or just stopped working?

I haven't been ISY customer from earliest days but I'm willing to bet ISY didn't become stable platform overnight either. There are always growing pains. Also, I think majority of issues are related to ZMatter specifically, which is kind of Beta supported. That is, if you take zooz stick and use that instead (with S0, instead of S2), I think everything should mostly work. I think maybe firmware updates should be managed slightly differently with a way to back out. But if you want more stable system, go back to stick, stop updating firmware and wait it out.

Try restarting udx

You'll have to wait for UDI unfortunately. You can check isy or udx service log files but it's not like you can do anything to fix it. Here are my versions for the reference. Not sure if it's possible or a good idea to try to downgrade. I would wait udx-3.3.5_4 = isy-5.5.5_1 = pg3-3.1.17 =

can you hit it by ip from browser? https://<ip>:8443/desc

Can you guys be more specific on what is "dead"? Seems like you can ssh and package are there? Are you unable to open AC or something else? Do you see isy service running? [admin@polisy ~]$ sudo service isy status isy is running as pid 29385. [admin@polisy ~]$ ps aux|grep isy isy 29386 3.9 3.5 292336 146852 - S Wed10 154:04.05 /usr/local/bin/isy-freebsd-x64 -w /var/isy isy 29385 0.0 0.1 12848 2292 - Is Wed10 0:00.06 daemon: /usr/local/bin/isy-freebsd-x64[293 admin 41314 0.0 0.1 12840 2404 0 S+ 15:04 0:00.01 grep isy If so, maybe just advertising doesn't work?

I said that but that's related to lock updating status as well as ability to write user codes. I don't believe that it would affect lock not creating nodes. I don't have that issue. A couple of times enrolled devices wouldn't create nodes. I had to run z-wave -> synchronize and it was created after that usually.

The solution for this was identified by @Chris Jahnand should be available in the next firmware release