firstone

Test program is separate from node server. We can use it to rule out remote code set issues, communication issues, etc. Basically if test program will work, node server will also work. So if you still want to give it a shot, PM me.

This is PG3 log. I need a lot for AVServer itself. You can generate log package. PM that to me, please.

Are you capable to ssh-ing into eisy and running commands? I can PM you test program. You're a second person having this issue - the only thing I'm thinking about is that Flirc changed firmware or hardware somehow and it doesn't function as expected.

https://github.com/firstone/av-remote-poly#lg-tv-web-os-devices if TV doesn't prompt to accept connection it will not work.

Before you start playing around with code sets, I'd still recommend trying some tv remote - just to see if it fixes things. Also, maybe try rebooting eisy just in case. If you haven't rebooted since you've installed, it could be permissions issue that would also cause lost signals.

Check log files in /var/log. You should be able to grep on DHCPOFFER I think.

I would check polisy and dhcp server logs and see what's being offered and assigned. I don't believe polisy does any kind of special ip address caching, nor it would be proper behavior. Unless it's somehow misconfigured to static maybe.

Probably should be done by your dhcp server - there should be a way to give static dhcp lease for a particular mac.

If it's universal remote, then it's not a function of a remote but rather specific code set you're using. Changing to different code set should fix things. If you're comfortable ssh-ing into eisy and running python script, you will be ok.

Number one thing to try is to use another simpler remote - like TV remote, and see if this clear things up. Some code sets do not send key press finish events and it breaks things. On PC it reacts but doesn't necessarily send all correct signals. Next step, if you're comfortable doing it, I can give you a test program in python that you can run on a pc or eisy. That will show exact signals your remote is sending.

Holidays either come from python lib, which has a lot defined. https://pypi.org/project/holidays/. Or you can set up your own by date. With that in mind, above use case is not something this was written for. It's more like day based. Something like if Today is a holiday, do not lower thermostat. Or if tomorrow is a holiday, keep outside lights longer. The more important part is its dynamic. You can turn it on of off. For example, you can set up WFH for Mon and Fri. But I can say "Alexa, turn tomorrow on" and tomorrow will become WFH, running all WFH schedules. Something like that. For above use case I'd just use regular schedule as others have said.

Latest code is here https://github.com/firstone/av-remote-poly/tree/dev/esp8266/RESTRemote

Updated it to version 6 but cannot test and do not guarantee that it works. Only that it compiles.

I've just downloaded IDE version 2.2.1, selected Generic ESP8266 module, loaded .ino and it compiled. Not sure why it's not working for you. I have ArduinoJson 5.13.1 installed.

I don't think it's being widely used, if at all. To be honest, I haven't touched it for a while. I will try to get it recompiled when I get a chance but can't promise any timeline. If you figure out required changes, PM them to me, please. Otherwise, I'll update when I can.

@GQuackI've published version 2.0.7 with update input list per above. Although I've had a report of 2.0.6 not working from one person but no logs so far. If it happens to you, PM log package to me.

Sorry, I don't get notifications for repeated posts for some reason. PM me next time to get my attention.

If you know command for it, I can add it. It would be in form of "SLI xx". For example "SLI 01" is cable / sat.

Removed extra 0. Next time it "updates", it should get fixed.

It connects on telnet port, there's no other set up. If it says connected, that should be it. I'd try turning off all other apps as they might interfere. Change NS into debug mode, go to AC and try a few commands, Mute On/Off, change volume, etc. PM the logs to me.

Are you able to set user codes by hand (via keypad)? And do you see Lock/Unlock changes in IoX when you open/close lock manually?

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.