Intel D54250WYK: Issues with power on / off commands

Issue with Intel NUC D54250WYK:

  • Power Off acts as Power On
  • Power On doesn't work

Full disclosure: I actually don't own this device but use its IR commands with an Arduino to control a modified Chrombox with LibreELEC: https://github.com/zehnm/arduino-kodi-ir-keyboard/tree/mce-remote

It works flawlessly with Logitech but not with NEEO. It's still possible I did something wrong in my setup or Arduino programming, but since it works with my Harmony I believe there's an issue with the NEEO IR codes. 

Could you please re-check?

FYI: these are the IR scancodes I'm using:

#define IR_MCE_POWER_ON       0x800F0429
#define IR_MCE_POWER_OFF      0x800F042A
Reply
39replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Thanks a lot for the feedback. Our device driver team will check this and once fixed they will sure as you to give this another try.

    Reply Like
  • Markus Zehnder

    This should be fixed! The new data appears around 7PM CET. Please update your device according to this guide. Thanks!

    Reply Like
    • Andy Thanks a lot! It's working now 👍

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Markus Zehnder 

      Glad to hear!

      Reply Like
    • Andy 

      I have the same NUC, but for me the Power On command does not work. Also, the Power Off command puts the NUC to sleep instead of turning it off completely but I can manage with that.

      I am able to wake the NUC with my Lenovo MCE remote.

      Reply Like
    • Pascal Buijs Did you update the device in the NEEO app and which version is shown in the device configuration? The updated version 97 works with my 'virtual NUC receiver'.

      Only issue I have is bad IR detection with my setup, i.e. sometimes I have to press multiple times Power On to actually power it on. But this is most likely an issue in my Arduino IR decoding which I have to investigate... Unless you have the same issue, then the problem would be with the NEEO IR timings.

      Reply Like
    • Markus Zehnder 

      I indeed have the latest version 97. No offense to your hard work for your Arduino setup, but I would prefer this to be changed/fixed for my NUC.

      Reply Like
    • Pascal Buijs 

      I fully agree it has to work with the real device. It's just weird that I got the power on and power off commands from Logitech Harmony and they are also used in other MCE remotes.

      This one here looks interesting: https://communities.intel.com/thread/118048
      Power on with Intel NUCs only seems to work with very specific MCE remotes.

      I guess Andy needs to dig deeper...

      Reply Like
    • Markus Zehnder Andy

      interesting find! I wouldn’t mind testing different codes if necessary...

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      Please try the MCE commandset we already support and see if the included power command works. Thanks!

      Reply Like
    • Andy 

      Both MCE standard power toggle and MCE advanced power on/off don’t work.

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      I'm sorry to hear. Not sure what's next. It looks like powering on and off is just not possible for your device.

      Reply Like
    • Andy 

      I kindly disagree, since I can power on my NUC with my lenovo RC6 MCE remote without issue...

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      I was not aware of this. Sorry. We'll order this remote and learn the commands. Just to be sure, you did not remap any commands on the RC6 remote?

      Reply Like
    • Andy 

      This is a non-learning remote (as is NEEO right now ;) ), so no

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      For some MCE remotes, you can remap buttons in a app. That's why I asked. But in the end that's good news. Means we can add the power as soon as we have the remote.

      Reply Like
    • Andy 

      That would be nice, awaiting patiently...

      Reply Like
    • Andy 

      So I had some spare time today and decided to update the drivers and BIOS of the NUC. This has solved most of my  problems with IR on/off! I am now able to wake/turn on using the NUC power on command in NEEO. Also the NUC power off command puts my NUC to sleep. I would prefer power off, but that is probably something I have to change on the NUC. Also after wake-up, the screen stays black, although kodi etc runs on the background. So probably also something NUC/Windows related.

      Reply Like
    • So, managed to change the power off IR command to actually power off the NUC and not to sleep. Thank you obscure Windows forum with regedit work arounds...!

      For me the NEEO now works properly to control the NUC. Next project: Kodi API!

      Reply Like 1
    • Andy 

      The firmware update caused the on command to stop functioning 😕

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      Do they still work on the shortcut screen?

      Reply Like
    • Andy 

      No, it’s Just the power on command btw and the NUC still reacts to my MCE remote

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      Can you please check if the power off command does serve as power toggle command? I had a NUC user yesterday where this was the case. And he did use the same driver as your device uses. Thanks!

      Reply Like
    • Andy 

      Power on = no action on or off

      Power off = toggle

      Power toggle = toggle

      It used to work as it should before the update. If I remember correctly, I also performed an update of the NUC driver after the firmware update. I think I had a much higher version number then (96?) as compared to now (6)?

      Reply Like
    • Andy 

      Also some other strange behaviour: the app does not seem to keep the recipe activated when I use the power toggle instead of the not working power on...?

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      Can you please try if the NUC5i5RYH does act correctly with the power commands?
      Regarding the "Active" situation - as long as a device does have discrete power on and off commands in the driver, power toggle will not be taken into account for showing an active recipe. If the device does have power toggle only, it will show as active. Let me know if the 5i5 power commands work. If not, I'll create a driver with the power toggle only.

      Reply Like
    • Andy 

      From the NUC5i5RYH driver, only the power toggle works. 

      Like I said, it used to work perfect! I don’t understand why it stopped working other than that somehow I have an earlier version now...

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      Finally, we figured out what was going wrong. Can you please add the device Intel NUC Test? It will appear around 6PM CET. If this works, I'll attach this driver to your device. I'm sorry for all the trouble caused!

      Reply Like
    • Andy 

      Nope, none of the power commands work... 😑

      Reply Like
    • Andy any progress?

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      Hi again,

      We did dig out every POWER ON command that was ever added or is till added for any MCE enabled device. If no one works, I'm afraid it has to be on the NUC side. E.g. inside the Bios or the registry.

      If this still doesn't work, power toggle works, correct?

      The Live IR Test works the following way:

      1. Navigate to the Settings Menu in your NEEO app.
      2. Navigate to NEEO Brain.
      3. Click on "Live IR Test".
      4. Enter into the text field the following code: FemBS0KnQW
      5. Test the commands

      Thanks for testing!

      Reply Like
    • Andy none of the IR live test commands work.

      Please let me remind you that the distinct power on and off commands used to work flawlessly before the last firmware update.

      Maybe you should look into the NUC commands instead of MCE commands?

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      I did. All NUC commands are MCE commands. And the test contained all power on and off command that where ever added to any Intel NUC device - plus all other possible MCE power commands. 

      I understand that this used to work. But as the test contains every power command that ever was added to Intel devices, the one that used to work has been included for sure. This means, the issue is not in the data. Did you edit the recipe back then and added some other command that used to power on and off the device? Maybe the Power toggle?
      It happened at the same time as the update. It makes sense to search there. But is it possible that you changed anything within the NUC? Was there an update? Did you change the BIOS settings, or something somewhere in the registry? And if you run Kodi, did you change something there. It also has a IR button config file. 
      On our side, we can try two more things. Power toggle does work to turn off and on the device, correct? If yes, we can solve it with this command. The current new power handling is much better and does a good job with power toggle devices. 
      Another possibility would be that you send me the remote. This does only make sense if the remote contains separate, discrete power on and off buttons.

      Reply Like
    • Andy no changes to NUC whatsoever. I still beleive that there must be something you guys are missing, but for now let’s agree to disagree.

      Power toggle is working, however with the limitaties of the activation problem.

      Please adjust this so that I can at least use the toggle properly...

      Reply Like
      • Andy
      • Andy
      • 1 yr ago
      • Reported - view

      Pascal Buijs 

      Adjusted! But we had to add a new driver in order to not break anything for other users. The new data appears around 12AM CET. Can you please delete and re-add the device? Thanks!

      Reply Like
    • Andy it’s me again...

       

      Due to Z wave rearrangement to Domoticz as primary controller, I had to reset the NEEO because a Z wave reset is not possible (see other posts on this forum). Also, because you don’t keep a backup of my configuration, I had to start al over again making my recipes.

       

      Somehow the power toggle option that used to work (kindof) isn’t available anymore in the driver for my NUC. So now I’m back to the same problem from months ago...

       

      Please fix this (again)...!

      Reply Like
      • Andy
      • Andy
      • 5 mths ago
      • Reported - view

      Pascal Buijs 

      I'm sorry for this! As the discrete commands work for other customers with this device, the changes where reverted by a co-worker. To make sure that this doesn't happen again, I've now created a separate device. It's called "Intel D54250WYK (Alt. Power)". It will appear around 12AM CET and includes the power workaround that works for you.

      Reply Like
    • Andy 

      Thank you for the effort of readding the power toggle commands, it is sort of working now. Sort of, because I have some strange behaviour when shutting down the recipe. Although toggle off is placed as a final step in my recipe to be able to use the assumption mode, shutdown starts with it, and also end with it?

       

      see pictures attached for recipe start and stop, starting from the SDK driver. HTPC kodi is from the SDK driver, which I have to add to keep the recipe running. HTPC 2 are the newly added Intel NUC power toggle commands.

       

      Hope this makes sense...

      Reply Like
      • Andy
      • Andy
      • 5 mths ago
      • Reported - view

      Pascal Buijs 

      The first power step is from the old device, the old power off. It looks like you have just added the new device and added the new power. It doesn't hurt to leave the old command in there. It's up to you.

      Reply Like
Like Follow