firstone

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.

I will try to update my polisy to 5.9.1 and see if I can reproduce. But you can also put node server into Debug mode, restart and PM log package to me. Maybe something simple.

I don’t think ISY994 implemented security. I do not recall having to enter any codes. I’ve have older and zwave plus working with 994 but then had issues with polisy. But HA with modern usb stick will definitely have security.

The issue I've had was with ZP lock and newer firmware, FYI. Here's what you can do to troubleshoot it, if you're so set up. If you have another z-wave controller and have HA set up, you can try to enroll the lock into HA and see if it works correctly. From there you can generate the log files for enrollment and UDI maybe can see the difference. Some of these devices do not follow standard to a tee and sometimes half implement protocols. Which is why my "older" firmware was fine but newer wouldn't work. Schlage support was of zero help.

When you see this, you should usually see the notice on dashboard saying "Please press the button on the Hue Bridge(s) and restart the node server within 30 seconds". If you're not getting a notice there would be something wrong on pg3 side. But either way, try to do it.

Default timings are 500, 500, 50. Long poll and short poll are not used. To troubleshoot reliability, put plug in into Debug mode, do 5 quick presses, then 5 press and hold. Send log package to me, I will take a look.

I've tried installing it now again - it finished installation properly but gave some UDX error. Will try to work it out with UDI. Once installed, I was able to start it with no issues. Seems fine.

Unfortunately, I can only support devices I have or used to have. If it's something very simple like Denon or Onkyo, where you have a very limited set of commands with no authentication, I could do it. But Samsung TV is likely to have overly complex (and completely unneeded) protocol.

Set "Release threshold" to 50. I will release a new version with lower default value. Seems it's causing more problems than it solves.

I will take a look. I haven't changed anything for quite some time so possibly some new change in pg3 is causing it.

If IR signal is good, when everything works, it will work 100% of the time. Try one thing: go to settings and change "Release threshold" to 50. Restart and try. If that doesn't work, reach out to me in PM and we will get it working.

PM me and we will get it working. Seems like your remote is not triggering Flirc keypresses. Otherwise, you would see nodes under main controller. If your remote does not use "original ISY994 codeset", you need to teach its commands to Flirc. We can test it on any computer.