firstone

Removing zone nodes is not going to do much. Technically you can ssh into eisy and remove corresponding lines from yaml config file. I will add checkbox for zone3 when I get a chance. You'll just have to be a beta tester.

Seems like your receiver just doesn't respond to Zone3 commands. Do you have zone3? If you do, you can shut off AVRemote and just connect via telnet cmd line and try running some of Z3 commands. See what you get as a response.

I don't see anything abnormal in that log. Let's try this - in PG dashboard AVRemote details, click on Log, make sure Debug level is selected. Go to Configuration and try to change and save. And not the time you've clicked "Save" button. Then go back to Log and click "Generate Log Package". PM the file to me, don't post it in this thread.

Configuration is not saved directly but uses polyglot that's running it. I doubt that itself would be broken. Try to generate log package and PM it to me, I'll see what I can find.

PM Log package to me, please. Put it into "debug" mode, do some key presses and then generate log package. If nodes are created, there should be SOME activity.

Yes, my authentication key only worked for 100 people. After that you need a complicated "review" process where you have to make a video, etc. The only way is to create your own api key which you can enter as a parameter.

Put node server into debug mode, generate log package and PM to me. I'd like to see both, you changing source using remote, as well as trying to change it via AC. Please, write down the time for both. "Connect on demand" is a workaround where some models do not function with permanently opened telnet connection. So it's opened at the time node server reads or writes.

I can comment on Alexa network connection. Perhaps you can try to work it out with Amazon support. But as far as interface - why do you even need to use it? I set up all voice commands via ISY portal. I don't think I ever needed to touch Alexa interface or app for that. Just set up devices and scenes. I can turn on (hue) bedroom lights (that will auto shut off in 30 min). I can open z-wave blinds. I can turn on some selected Insteon switches. Alexa doesn't like certain words but other than that, it mostly works fine for me. Home assistant does have "voice preview edition". People have various success with it, from what I've read. But I do believe it's local only and doesn't need cloud. So definitely a plus there. I, personally, use Alexas as speaker so that doesn't really work for me. But if Amazon further messes it up down the line, will definitely look into it.

Same here. Did not upgrade Hue plug-in so definitely v6 related. Good thing is everything should work fine after few hours of recreating linking. 🤦‍♂️

I'm pretty new to this UI but have noticed that all "Nodes" are flat. While in AC I have everything organized in folders. For instance, First Floor -> Living Room -> Blind, Second Floor -> Master Bedroom -> Blind. So now in nodes I have have like 5 "Blind"s and don't know which one is which. How do I migrate this?

This is awesome and hopefully you can work out all issues. I, personally, couldn't get V2 working reliably. I use Hyperion and every time I switch from V1 to V2, always stops working after a while - getting some "ssl timeouts". Developer blamed on "network latency being more strict in ssl" but my hub is hard wired and on the same switch. I don't think there could be any less latency. Could be I have one of the earliest 2nd gen hubs but the firmware is the latest.

If you're capable of running ssh commands, PM me and we can try to figure out what have gone away. I can also probably tell you how to get it back temporarily.

I haven’t upgraded to 6 yet. I will do it and will work with UDI to resolve this.

I've fixed it. Prod was pointing to dev branch. The only changes are addition of new gen onkyo support. Those do volume in half db increments. There aren't any other changes.

Antennas come with module. You don't have to buy them. You can try without them as well and see if they work. Old ISY had horrible range for zwave. But it if worked fine for you, possibly you don't need antannas. Also I think you can get any other USB z-wave adapter, like Zoos stick. Those don't have external antenna.

I don't think z-wave will work without antenna. But you can use USB extension cable to physically move adapter away from eISY if it makes your life easier.

Upgraded and restarted. Still same error:

Try setting "Host Name" to TV's IP. When properly connected, TV will prompt you to accept incoming connection. Also, note that only works with older generation of LG. Newer one had changed protocol and I don't have new model to get it working.

It show as running: eisyui is running as pid 6276. I've tried restart. Luckily fixed Portal connection but UI itself still shows same error. It was working when I've originally installed it.

I've noticed my Alexa stopped working and when I've check portal - it's disconnected. UI itself says "Error: Network Error". I could live with UI issues but losing Alexa functionality is very annoying. Tried restarting isy service but that did not fix it. Everything else seems to be working fine - AC, Polyglot. Anything I should try and/or check before I reboot eisy?

Have you exchanged power supply? If you have Insteon PLM, can you try unplugging it and redoing the test? If not, we can look at threshold values and take it from there.

I did not expect eisy-ui would affect legacy AC functionality.

Seems it could be my fault. I have tried installing eisy-ui prior to upgrade. The page there says "This is no longer the case. When eisy-ui is installed, eisy-ui connects to portal instead of IoX. This change is transparent. ". So this could be the reason. Once I've finished installing eisy-ui, portal shows eisy as connected.

I have started upgrade at 6pm last night. I'm assuming it's enough time. I've just rebooted this morning and it's still the same.

Updated to 5.9.1 last night and eisy will not connect to portal. Everything else seems to work but portal page doesn't show any info and clicking on Refresh shows "Bad request". Anybody else has seen this?