firstone

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

Missing step - in configuration tab you need to select ZMatter, If it says "Z-Wave dongle not responding", you probably hadn't. If it says "ZMatter not responding", then it might be defective ZMatter dongle.

It's an unused eisy. I don't have a backup but I guess I can just restore to factory state. I think that can be done with eisy. Was just hoping for less drastic solution.

So it seems you can get to IoX. When you use ISY launcher, click Add that put exactly the url you've just tried. If you see it showing up with firmware version, you should be able to open AC.

What do you see if you try https://<ip address>:8443/desc ? Anything?

Ok, allow me to elaborate. Both, Polisy and eisy come configured for non-Zmatter adapters by default. When you switch to ZMatter and run conversion, they're become configured for ZMatter. I have done it on Polisy and it works with ZMatter. I have also (prematurely) done it on eisy, because I was getting ready to move from Polisy to eisy. Now, because some devices don't work well with ZMatter, I'm considering using another adapter - 500 series. But because I already ran this conversion, the adapter is no longer recognized as eisy is expecting ZMatter now. I can try it in Polisy but I'm 99% sure the result will be the same. So I'm looking for a way to reverse ZMatter conversion / migration.

Yes, didn't work

When I plug in Z-Stick into eisy, this is what I get: \\ How do I fix this?

I'm not asking about how to move devices. IoX is switched to ZMatter and expecting ZMatter controller. How do I connect a different to controller to IoX?

Want to test some devices with a different controller.

The name "AVR" needs to resolve properly on polisy/eisy. If you ssh into it and 'ping AVR' or 'nslookup AVR', that will show you if name resolution works. It's a property of your DNS setup. 23 should be correct port. Check receiver settings. There should be settings related to IP control. I think by default it's off when receiver is in standby. But there could be others. You can test it with telnet from any computer. telnet 192.168.1.50 23 If it's up, you should connect and you can send telnet commands by typing them. Are you using version from prod store or new version from beta store? Also, PM logs to me. Easier to look in file format and doesn't pollute the forum.

Neither Denon nor LG will auto discover. You need to configure them in configuration page. You will need to put a name and IP address or a host name. Also, this only works with older WebOS LGs, not the newer one. Since I don't have newer one, I can't really support it. Which "Discover" button did you press? I'll fix the error.

Adb is not an officially published Android or Shield interface. The output of it can (and does) change with new android releases. When that happens, I might or might not be in a position to work on it right away and the fix might not even be possible. That's the downside. On an upside, you can do things that are not otherwise possible, such as fetching installed apps names. Similar functionality is available through (more official) chromecast interface. Chromecast does show media status for some apps. And you can technically add ability to start apps, thought that would have to be configured by hand, rather than automatic. You should look into it as a back up in case adb breaks in the future.

Same

Try 2.0.4. See if it works. You will need to reload profile. Probably the easiest way is to Get Apps command.

Try to rerun Interview or maybe remove/re-enroll.

both

I have the same thing. Node seems to be upgraded from 18 to 19 and upgrading this package fails as well. This update definitely breaks both, pg3 and pg3x.

If developer decides to stop developing what are the options? Creating completely new node server for the same integration? Kinds of sucks but I don't see any other possibilities.