shayne / hwinfo-streamdeck Goto Github PK

Monitor sensor readings with this HWiNFO64 Stream Deck Plugin

Makefile 0.89% Go 40.17% CSS 41.41% HTML 3.44% JavaScript 10.54% Batchfile 0.24% C 3.31%

hwinfo-streamdeck's Introduction

HWiNFO Stream Deck Plugin

⚠⚠ Major refactor landed in pre-release v2.0.0, plugin code open sourced, remote monitoring infrastructure support ⚠⚠

Thank you & Looking for Maintainers

Thank you everyone who has used and enjoyed this plugin. It started as a passion project and I continue to use it day to day. I am happy to finally release the full source on GitHub. When I first built it, it was closed under agreement with the HWiNFO64 project. They have since opened up the shared memory interface and now the plugin is freely open.

I haven't had the time to dedicate to this project in some time and appreciate everyone for hanging in there. I hope to work with some of you who are eager to take the project over. I am happy and ready to hand over the reigns. If there are development questions I'm happy to share my thoughts on the code and structure that exists.

-Shayne

NOTICE: HWiNFO64 must be run in Sensors-only mode for the plugin to work.

Enabling Support in HWiNFO64

NOTICE: It has been reported that running the "portable" version of HWiNFO64 doesn't work with this plugin. The recommendation is to run the version with the installer until I can figure out the issue.

Download and install HWiNFO64, if you haven't already

HWiNFO Website
Choose "Sensors-only" mode
Click "Settings"
Ensure "Shared Memory Support" is checked
(Optional) Recommended launch settings
Click "OK" then, "Run"

If the plugin doesn't work immediately, you may have to quit and reopen HWiNFO64.

From the system tray:

Install and Setup the Plugin

Download the latest pre-compiled plugin

Plugin Releases

When upgrading, first uninstall: within the Stream Deck app choose "More Actions..." (bottom-right), locate "HWiNFO" and choose "Uninstall". Your tiles and settings will be preserved.
Double-click to install the plugin
Choose "Install" went prompted by Stream Deck
Locate "HWiNFO" under "Custom" in the action list
Drag the "HWiNFO" action from the list to a tile in the canvas area
Configure the action to display the sensor reading you wish

hwinfo-streamdeck's People

Contributors

Stargazers

Watchers

Forkers

yorgyetson siver2918 triggy-b wolfinabox a55imilat0r franfearless aflawrence simplelover hopla thepvmgoats vinc3v3ga ergoz gwaldvogel icurbix

hwinfo-streamdeck's Issues

Support line breaks in titles

Could line break support be added for tile icons?

suddenly cannot install plugin

i'm using the 2.0.3 version. i tried both streamdeck app plugin installer and the download from github. suddenly my streamdeck hwinfo icons became " ? ",.... and if i search in plugins in streamdeck... can't find the plugin.
i go to app store... asks me to install... i try installing.... but when i close it... and reopen... says "install" again. it never fully installs... and the plugin doesn't work anymore.

a second computer i have the prior versions... still working.

Feature: image as background

Using images instead of solid color would be nice to quickly identify all the widgets.

Something like Stream Deck's CPU plugin.

HWInfo64 v7.06-4500 breaks plugin

The update to HWInfo64 that rolled out today appears to be not playing nice with the plugin.

Completely uninstalled the plugin, restarted the PC, reinstalled the plugin (2.0.0), double checked all of the settings, but still get an error stating the plugin cannot communicate with HWINfo64.

Not working with HWINFO pro v7.07-4505

After updating HWINFO, even with shared memory enabled and everything else as recommended, the Stream Deck keeps saying to "Please Launch HWINFO64"

request for feature

is there a way we can get the button to act like a button or the display like what I would love to do is see the load of my CPU tap that button and take me to a profile with what's the load on every cor or some think like that basically I'm asking for a feature where if you tap the button it could switch to another profile where I could have the information like that

GPU Performance Counters

This is not related to your plugin but I can't find a way to message you. I modified the streamdeck CPU sample to have a GPU button. I'm trying different variations of the GPU performance counter "\GPU Engine(_Total)\Utilization Percentage". After collecting the query data and I get counter value and it is always 0. Do you read GPU perf counters for your plugin?

No longer working on 7.06

HWiNFO64 just recently update to v7.06, and the Stream Deck plugin no longer connects, no matter how many times I reboot and re-check that the settings are correct. It worked just fine through v7.04. It now continually reports "Please Launch HWiNFO64." This project hasn't received an update in over a year. Are there any plans to continue supporting it?

Loading senor list... Win 10 + 6.00 / 6.10 Installer

Keeps loading sensor list.

HWinfo set to shared memory support.

Tried 6.00 / 6.10 (installer, 64)

Newest Stream Deck +plugin

Data does not load after changing profile

Hey guys,

i setup the HWInfo plugin and it works good.
But I got the issue, that after changing the Stream Deck Profile to my HW-Info-Profile, some data is not loading.

What is working:

CPU
System
GPU

What is not working:

HDD/SSD Read/Write
Network Up/Download
(didn't test anything else yet!)

After clicking on the individual item in the Stream Deck software, the plugin says "Loading..." and then it works again.

HWInfo64 Version: 6.22

Does anyone else have this issue?

Graph data resets when switching profiles

Whenever you switch profiles or folders, the little graphs reset to a straight line at the start-value.

It would be nice if - on initialization - you could get the historic data for the selected sensor and populate the button with that.
If that is not possible can you at least somehow store the previously collected data. I realize there's going to be gaps in the data that way, but it would still have more useful data than just the straight line.

I have a few of these on the same spot in multiple folders/profiles, so when I switch, they'll still be there for all but the most crowded of layouts. However, everytime I switch, the graphs reset...

KB to Mbit

Was able to convert the Download Value from KB to MBit, but it still shows KB/s next to the value. What should I change?

Feature: trafficlights system

I would like to have a traffic light system on the bargraph.
So that i can define some limit values like: green temp < 70°, yellow for 70-80° and red for values > 80°...

Plugin not installing.

When I try to install the plugin is it says that it installs, but does not show up in the custom place. When I go back to the download page it says that it is not installed

Can you do this for AIDA64 as well?

AIDA64 also supports shared memory, so forking this project to suit AIDA64 should be relatively easy. Let me know if you're interested. If not, let me know (in email) whether you would allow us to build our own Stream Deck plugin based on yours.

Best Regards,
Tamas Miklos (a.k.a. Fiery)

[email protected]
FinalWire Ltd.
www.aida64.com

Implement HWiNFO Gadget method support

Shared memory is now limited to a 12 hour period. After that you have to manually reenable it. This limitation can be remove by buying the new pro version. But they state, that they opened up the interface to read all the values. So there might be a chance to circumvent it?

Plugin not working (2.0.2 + HWnFO 7.12)

The plugin release 2.0.2 doesn't seem to be working on my setup, and I get the communication error:

HWiNFO Stream Deck Plugin: 2.0.2 (from GH)
HWiNFO: 7.12-4580
Stream Deck: 5.1.2.14743

I have a pro account and shared memory support is enabled.

HWinfo 7.06 doesn't display on StreamDeck icon

After updating to HWinfo 7.06, my streamdeck integrations all display "Please Launch HWINFO64". It's obviously running. And I have a licensed version with shared memory support enabled. I also can see the sensors in the streamdeck button, it's just not displaying on the button.

Any advice?

The letter 'n' in title is read as the function '/n'.

The word 'Intel' is whown as:
'I
tel'

Read sensors/readings from remote machine

I would like to be able to select to use remote sensors so I can report on my Gaming PC via my Streaming PC with streamdeck . I have the remote sensors showing in my HWinfo sensor list but are not visible in the plugin sensor list.

[Feature Request] Multiple lines - Format: \n

Hey,

is it possible to add support for \n in Format ?

Would love to show the unit (MB, KB, %, ...) i a second row.

\n does not work:

Greetings!

2.0.0 plug in stops running....

Been using the latest plugin since you updated it... But after a few days of the same issue, it is having a problem..

Basically sometimes it will not load the HWINFO specs on the first load/run. You have to exit streamdeck completely and start it again. Also, after a period of time (have not yet isolated exactly how long yet), it just stops working. It stops updating and you again have to exit streamdeck and load it again..

NOTE, I have TWO streamdecks running and I am thinking that could be possibly part of the problem? I.E. it is not updating the 2nd or higher hardware box after a while.. almost like it goes to sleep... The reason I say this is my first streamdeck (used for other stuff) does NOT stop working.. Only the one HWINFO is used on stops.

AMD Ryzen 9 5950X MHz Core Clocks missing with newest HWiNFO Version

Hi there,

I updated HWiNFO from v7.12-4580 to v7.14-4610 and now I can't use "MHz Core Clocks" anymore.
It shows me the average Clockspeed for every Core in MHz.
Maybe this PlugIn need an Update.
If I go back to the older 7.12-4580 Version, it works again.

temperature is displayed as □□C.

I am using hwinfo-Streamdeck v1.2.0 and HWiNFO64 7.02 in Windows 10 Japanese environment.
But only the temperature display is wrong. For example, the temperature is displayed as □□C.
Probably a font problem. Is there any way to fix it?

Sync refresh rate with HWiNFO64

Right now the plugin refreshes the graphs every 1-second. It should be possible to sync this to the refresh rate set inside HWiNFO64.

Additionally, it might be useful to have a second option to lengthen the refresh above what is set in HWiNFO64. For example: HWiNFO 64 is set to refresh every 1-second, but you'd like to only update the Stream Deck every 3 seconds.

Issue Plug In: com.exension.hwinfo.streamDeckPlugin

Hello.

Issue with version of plug in v2.0.2 .

It worked for a while and then I tried to put hwinfo64 in automatic in the startup folder. but it never loaded. therefore i uninstalled the plug-in in elgato stream deck. But since trying to reinstall the plug-in, it no longer loads the sensors. it remains on loading ... Now HWinfo64 7.12 is loaded automatically but I get stuck on this message in STREAM DECK. I had deleted the folder in AppData \ Roaming \ Elgato \ StreamDeck \ Plugins . The name of the folder is therefore com.exension.hwinfo.sdPlugin, is there anything else to delete ???

Indeed, thanks a lot for the job, it's a very good plug-in !

Upgraded to HWiNFO pro SD stopped detecting

Hiya,
I love this utility, but as soon as I upgraded to HWiNFO pro, my stream deck stayed stuck on the "Please Launch HWiNFO64" icon. None of my settings have changed from before when it was working fine. Does the plugin need to be updated, or is there an additional settings I need to tweak now that it's the pro version?
Thanks in advance!

Muti-reading button

Stream deck mini only has six buttons - which makes it hard to assign to a sensor per button. Given the size of the displays, we could fit multiple sensors on each button. For instance: CPU Utilization, CPU Temp, GPU Utilization, GPU Temp, Memory Utilization, and Network Up utilization and down utilization could all physically fit on a button, leaving a space for warning from SLOBS/OBS concerning skipped frames, or other issues like if the CPU or GPU thermally throttled. The graph could still map "behind" these metrics.

I have attached a small mock-up to make it easier to see what I mean.

Row A - CPU utilization % and temperature, the background could be the graph of CPU utilisation
Row B - GPU utilization % and temperature, the background could be the graph of GPU utilisation
Row C - Current up and down network throughput
Row D - space for warnings

It would also be useful if the text/background changed colour when certain thresholds were crossed - for instance if GPU thermally throttled, it could turn red - or put an icon to indicate the thermal throttling occurred.

How do the format functionality work?

Changes from Elgato

Explain to the user how to set up HWiNFO in the Property Inspector if the communication is not working

There are several reasons why the plugin would not work: HWiNFO not installed, Sensors-only disabled, Shared Memory Support disabled, ... If the user installed the plugin but have not installed HWiNFO or Sensors-only is disabled or Shared Memory Support is disabled, the user just sees "Loading..." in read in the Sensor field. I think there are several ways to improve this:
If you get an error when trying to connect to HWiNFO, you could display a message telling the user what to do. You could for example display a string like "The plugin can't communicate with HWiNFO64. Make sure to enable support in HWiNFO64" with a button "More Info" that would open the URL https://github.com/exension/hwinfo-streamdeck/blob/master/README.md
The Sensors text field is longer than the other fields
The Min textfield is not vertically aligned with the other fields

Not fully connected to HWINFO64

I just installed the actual versions of HWINFO64 (tested with 6.30 and 6.31-BETA) But i can't get this working.
All sensors will be readed out of the HWINFO, but the actual value will not be readed.
What did i wrong?

Range for temperature values

When i set a small range for some termperature value, say 40 degrees to 90 degrees, the tile doesn't scale correctly and it looks more like its 40 - 140 degrees. If I run the scale from 0 - 100, its fine.

Unexpected high CPU usage from hwinfo 2.0.2 caused by large number of TCP port bind and release.

Hi @shayne, thank you so much for making this plugin and I have been using this for long time on daily basis. To me, it is one of the killer plugin on streamdeck and very helpful to me!

And recently, I found an issue in HWiNFO 2.0.2, which makes it uses a lot of CPU and making my the entire system becomes very laggy. My desktop and mouse can lose response every once a few seconds. If you could help take a look and fix it, it will be very appreciated! And because of this issue, very sadly, for now, I will have to disable it...

To help root cause, I have analyzed this issue a little bit. I am using Windows 11 and here are the details of my rough analysis:

With netstat -anb, I am seeing huge number of TCP ports stuck in TIME_WAIT state (log 1). It means hwinfo-plugin.exe is creating TCP connections and closing it really frequently, as TIME_WAIT state only last for 4 mins, but we get ~15k port stuck in this state.
We can also see high CPU usage from bind/close as figure 1 shows. Because of this high port usage and frequent behavior, from figure 2, we can see it burns the CPU on the lock for TCP port list in the OS.
It also cause high CPU usage from kernel as well (figure 3), because TCP/IP stack needs to release the ports when their TIME_WAIT state it done.

Hope it helps and thanks a lot in advance!

Figure 1:

Figure 2:

Figure 3:

Log 1:

 [hwinfo-plugin.exe]
  TCP    127.0.0.1:10001        127.0.0.1:49160        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49161        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49165        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49169        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49172        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49174        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49181        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49188        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49191        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49192        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49195        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49196        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49197        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49198        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49200        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49203        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49204        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49221        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49241        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49247        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49250        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49251        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49258        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49261        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49264        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49265        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49268        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49276        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49280        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49292        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49299        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49304        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49305        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49306        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49307        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49312        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49322        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49330        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49332        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49341        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49342        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49344        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49346        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49351        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49353        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49354        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49355        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49366        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49368        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49369        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49371        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49372        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49377        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49382        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49391        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49393        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49395        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49396        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49399        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49443        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49444        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49460        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49464        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49499        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49513        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49516        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49517        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49519        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49523        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49527        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49528        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49532        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49538        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49553        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49576        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49577        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49579        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49581        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49583        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49584        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49628        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49629        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49641        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49646        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49662        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49690        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49694        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49801        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49803        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49806        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49810        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49811        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:49813        TIME_WAIT
.......
  TCP    127.0.0.1:10001        127.0.0.1:64596        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64605        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64609        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64614        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64615        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64616        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64617        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64621        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64634        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64643        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64644        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64649        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64660        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64673        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64677        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64678        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64682        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64687        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64696        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64700        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64704        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64715        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64722        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64731        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64736        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64737        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64739        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64741        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64743        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64744        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64747        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64760        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64764        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64770        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64775        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64781        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64784        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64787        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64789        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64790        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64795        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64797        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64798        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64801        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64806        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64811        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64812        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64814        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64819        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64825        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64826        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64829        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64839        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64840        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64847        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64853        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64856        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64867        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64868        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64882        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64886        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64889        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64894        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64900        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64923        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64928        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64941        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64942        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64943        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64956        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64957        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64965        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64972        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64975        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64978        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64985        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:64999        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65000        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65003        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65005        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65007        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65010        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65011        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65015        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65019        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65020        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65021        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65022        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65027        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65028        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65029        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65030        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65034        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65042        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65043        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65044        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65046        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65047        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65050        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65051        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65057        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65058        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65062        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65065        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65067        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65078        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65079        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65081        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65086        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65096        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65099        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65119        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65153        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65162        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65170        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65196        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65197        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65202        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65208        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65216        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65223        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65224        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65229        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65238        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65241        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65242        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65243        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65244        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65245        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65246        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65247        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65250        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65251        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65253        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65256        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65257        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65260        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65261        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65265        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65272        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65274        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65276        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65284        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65291        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65294        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65310        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65331        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65349        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65359        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65363        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65364        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65368        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65371        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65373        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65375        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65378        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65393        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65396        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65400        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65403        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65432        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65451        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65452        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65457        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65458        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65459        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65460        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65478        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65490        TIME_WAIT
  TCP    127.0.0.1:10001        127.0.0.1:65505        TIME_WAIT

Incompatibility with version 7.01 (beta 4425)

It seems like the plugin does not work with the latest beta of 7.01 (it shows "Please launch HWiNFO64" even if the tool is running and shared memory is enabled).
This is not a duplicate of #27 since it is not working at all, even with the Pro version.

Maybe the access to the shared memory changed in 7.01?

Cannot add new sensors after latest updates

After the latest updates of the plugin and HWiNFO the sensor dropdown is unable to load, even though the existing sensors continue to read data.

Trying to re-launch both applications does not fix the issue. Launching both apps as admin does not fix.

Un and Re-installing plugin does not fix the issue.

Double checking all HWiNFO settings I do not see any that are out of place.

HWInfo64 Free limitation 12h

Hello,

HWInfo64 Free edition now have a limitation :

HWiNFO64 (non-Pro) has a time-limited Shared Memory support to 12 hours. When this limit is reached during run-time, this feature will be automatically deactivated (and requires manual enabling again)

Could you consider using Open Hardware Monitor instead ?
https://openhardwaremonitor.org/
http://openhardwaremonitor.org/wordpress/wp-content/uploads/2011/04/OpenHardwareMonitor-WMI.pdf

[Feature Request] Change text size + Open-source the code

I'm kind of blind it seems and can't read the value text well (even though it's not completely necessary with the graph background). The ability to change the font/size would be great, as fmt doesn't have that capability AFAIK.

Also, do you plan to open-source the code? I'd be willing to help with some of these fixes if you did so. Would also make me feel more comfortable running it. Cheers.

Not working on AMD

I love the idea of the extension (I'm on v1.1.1)

Sadly it does not work on my machine... no matter what I do, I'm always presented with 'Please Launch HWiNFO64'.

CPU: AMD Threadripper 2990WX

HWiNFO is running (v6.08-3830) and set up as described in the README.md

I also tried running stream deck software with elevated privileges, to no avail.

Note: The list of sensors loads just fine, meaning that there is 'some' form of communication going on with HWiNFO64.

Followed by:

200kB send traffic from hwinfo plugin

My network has been stuttering today and I opened resmon to check out what could cause it. Right at the top of the processes using upload bandwidth is the hwinfo streamdeck plugin. I have no idea why this plugin needs to upload anything in the first place, let alone 200k bytes/sec. Is this a rat? @shayne

Not working since hwinfo 7.11

After upgrade to 7.11 it always says "Please launch HWiNFO64" on the keys, but communication seems still to work. Sensors-only mode is activated. Computer was rebooted.

After downgrading to 7.06 it works again instantly. So currently, I disabled auto updating.

Doesn't Currently Read Sensor Data

Current build with Stream Deck 4.3.1, plugin 1.1.1 and HWiNFO 6.0.8 Portable does not work.

I have my settings setup exactly like in the guide. I have restarted HWiNFO multiple times and the display still does not work. Surprisingly it does see the sensors because it allows me to select a sensor and reading. Upon selection of a reading though it immediate goes to the plugin error screen and says its unable to communicate with HWiNFO. So it is at least partially communicating with HWiNFO or else it wouldn't be able to figure out what my sensors and readings are.

how to change the text

95/5000
hi how do you convert Download speed to MB / s instead of KB / s so that both text and numbers fit

how to show Mbps
what should I divide it by

no graph and bigger number

Hi is there a way to mot use the graph and have the temp number bigger

HwInfo Strem Deck

How can i Dsiplay the GPU Temp. It's not availiable in the dropdown but i can see it in hwinfo.

Incompatibility with new version 7

Just installed HWInfo64 version 7 and lost all integration

Incorrect version in latest release

Latest release is marked as v1.2.0 however the plugin is still showing v1.1.1
(needs to be updated in manifest)

Perform an action if a sensor is clicked?

For example if you are displaying the GPU temp is it possible to click the button to run an action ?

Need to configure custom network port

When launching this plugin using the version on the Streamdeck store, it opens a connection on port 10000 automatically. Something I develop requires that port be free, so in order to run this plugin I need to stop streamdeck, wait until all the connections close (there can be as many as 10 "waiting" connections and it takes 2 minutes for them all to timeout and close), start my program so it can take ports 10000 and 10001. After that, I can finally run streamdeck with the plugin again and it will still run, taking up port 10002 this time.

While this at least lets me work around it, I'd like to have a way to configure this default port from the start, even if it's just an option in a config file somewhere.

Cpu Temperature hangs

Hello, after some time I have the problem in the Elgato Streamdeck that my CPU temperature just sticks and only runs normally again after restarting Hwinfo. Usually after 2-3 hours.

Sometimes hangs/stops updating tiles

I've noticed that sometimes, my HWiNFO64 tiles stop updating. Usually I notice this when unlocking the system (Win10 x64 1909).

However, the fix seems fairly simple. Normally, opening my Task Manager and killing the hwinfo.exe process of this plugin forces it to respawn and makes my HWiNFO64 tiles work again.

Not sure yet if it's a "real" bug, or a quirk of how my system is set up. My StreamDeck is disabled/enabled by Windows tasks when the workstation locks/unlocks (to let me keep "Sleep: Never" but still turn off the unit when my PC is not in use). Not sure if losing communication to the unit directly or indirectly affects this plugin.

Are there logs anywhere that might give a hint at what's happening? Happy to help debug in any way I can, if this seems like it might be worth trying to fix in a future update.