firstone

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?

I have 4 BE469ZP working fine with eISY and previously with Polisy. It prompts for code when enrolling. There was a bug initially but UDI had fixed it since, I believe.

There are two steps as far as I remember: In Developer menu, turn on USB Debugging. Once that's done, there will be another option - Network Debugging. Once that's turned on, restart AVRemote and you should see prompt on Shield allowing you to connect. Accept that and it should connect.

Did it ever work for you previously? Did you turn on Network Debugging on Shield itself?

I suspect you're missing authorization. When you connection attempt is made, your Shield should ask to allow developer connection. If it doesn't do it, plug-in will not be able to communicate and will be "offline". Also, I do not know if Shield will allow multiple developer connections. If you've moved from another device/ip address, maybe go into Shield set up and disable current authorization in developer options. If it all fails, PM the log to me, I'll see what I can find.

If you point me to a document that describes new protocol, I'll see if I can do it. If it's as simple as sending volume command differently, test it and share an example of what it looks like.

It's ESP32 based and has low powered antenna. I've had ratgdo and other esp based devices lose wi-fi connectivity a few times. But other than that, never had an issue with it.

I will take a look and get back to you

I'm thinking of maybe some brand that will require 120v. But yes, if you only need 5 or 12v, you can pass it over ethernet cable.

Do you see all bulb in a hue app? The process is not really that complicated - if you have installed into new slot, the configuration would not carry over. On start up, node server would try to authenticate. It can only do it if button is pressed. If it's not, it should publish a notice. Try to restart and maybe post some of the log around restart.

You'd lock yourself to only vendors supporting POE. I don't know if it's good idea. Seem like easier to run an outlet from nearby outlet that running ethernet to each window and using wireless z-wave or whatever protocol.