Jump to content
C4 Forums | Control4

projekZERO

c4Forums Member
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

projekZERO's Achievements

  1. Sorry I never followed up on this. We updated the system when 2.10 first came out and that somehow fixed the issue. It has been many months now and all the LG TVs fire up and shut down instantly and consistently. Believe me when I say the issues we were having before updating to 2.10 were real. We didn’t do anything to the TVs, all we did was update the controller and everything has been perfect. We weren’t expecting the update to change anything with the LG driver, but it was a nice surprise and I’ll take it.
  2. Well we fixed it, for a day... We paired the TV a second time yesterday and that fixed it. However, in the middle of the day today it started doing the same thing. We paired it again and it is working...for now. My master Bedroom TV and family room TV have each had to be re-paired once, but when they fail they do not work all together. The living room is just working incorrectly. Not sure if the expectation is to pair the TV periodically, like every day... The only TV I can count on in the house is the Vizio controlled by IR. -Steven
  3. This makes sense, and explains the issue of my Master bedroom. The other TVs never have the problem, even after power is removed. Still haven't figured out why the master bedroom TV takes 4 seconds to turn ON at times. Now I am having an issue with my Living room TV. It doesn't power on with C4 anymore. The living room input and AMP come ON, but not the TV. Then I go to shut the living room back down and try again and the TV comes ON ONLY when I turn the living room off. I thought this was a discreet Wake on LAN command, but it acts like a toggle, except it only toggles when it the OFF command. Mobile TV is still turned ON, and we have reset everything from the TV to the EA5. We also disconnected everything from the network one at a time to make sure wake ON LAN packets weren't getting eaten. We are a bit stuck right now trying to figure this out. -Steven
  4. I'm not worried about the WebOS 1.4 TV. That TV does not have Mobile TV ON, so it was never expected to power ON (but for some reason reason We use IR just to power it ON, and the driver for everything else. The driver works for everything else. What types of devices have you encountered that are eating WOL packets? I see other forum posts where people are having issues with volume feedback in the C4 App. Some report the volume is not even there at the top of the App. I noticed this as well, but it does appear after a while. The most important thing is I notice it doesn't report correctly on the App all the time or is slow to report correctly. The TVs volume changes instantly and always reports correctly, so it is just on the App. I'll double check which TVs it happens on, but I am going to assume only the V1.4 TV since the other two TVs run sound though the C4 matrix amp and not the TVs themselves.
  5. I am running this driver in my project with three LG TVs. One TV is a 2016 model running WebOS 3.0 One TV is a 2015 model running WebOS 2.0 One TV is 2014 model running WebOS 1.4 (which was the "WebOS 2.0 light" version that some 2014 TVs were upgraded to) All TVs are connected via Ethernet. The WebOS 2.0 TV has been flawless. It does have the 30-40 second delay after start-up, but it works great after. The WebOS 3.0 TV has failed to power ON twice. I end up turning it ON with the remote and it seems to work fine afterwards with no issue (doesn't need to be paired again). It does seem to power on slower than the WebOS 2.0 TV. There is about a 3-4 second delay before you hear the initial click from the TV. This could be the TV and not the driver though. The WebOS 1.4 TV will power OFF and change volume (after 30-40 seconds), but will not power ON using the driver. We tried different settings but no luck so far. If I remember right, I think it will power ON once or maybe a couple times when you first pair it, but stops powering ON quickly after that. I can double check that as I am not 100% sure if it ever powered ON with the driver but my memory tells me it did a couple times. Also, changing volume within the C4 app doesn't always register in the APP. For example: Volume is set to 20, I tap volume down in the App. The TV will report volume at 19, but the C4 App still shows 20 (incorrectly). I tap volume down again and the TV reports 18 and the C4 App reports 18 as well. Sometimes when this happens, the C4 App will correct itself after a 5-10 seconds, but sometimes it never corrects itself until you change the volume again. Not a big deal, but not clean. Just my experience so far.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.