Fma965

i finish work at 4pm (UK Time) i will get this done then

Guys be aware that the repo has changed and therefore the already installed versions won't update any more, your best way around this is to remove the plugin and install it from the community apps plugin or with the updated URLS on https://github.com/CyanLabs/corsairpsu-unraid

Anyone using HA may also want to check out which i just created

No worries, any issues let me know, the code for the redesigned dashboard is janky so if something breaks the dashboard on a new unraid version my first guess would be this plugin if anything.

sensor: - platform: rest name: Corsair PSU json_attributes: - temp1 - temp2 - fan_rpm - capacity - 12v_watts - 5v_watts - 3v_watts - watts - load - uptime - poweredon resource: "http://TOWER/plugins/corsairpsu/status.php" username: root password: !secret unraid_password authentication: basic value_template: '{{ value_json.product }}' headers: User-Agent: Home Assistant Content-Type: application/json @LintHart This code works and will get all those attributes in to a sensor called sensor.corsair_psu you can also seperate them in to seperate sensors if you wanted with this code sensor: - platform: template sensors: psu_temp1: friendly_name: 'Temperature 1' value_template: '{{ states.sensor.corsair_psu.attributes["temp1"] }}' psu_temp2: friendly_name: 'Temperature 2' value_template: '{{ states.sensor.corsair_psu.attributes["temp2"] }}' psu_fan_rpm: friendly_name: 'Fan Speed' value_template: '{{ states.sensor.corsair_psu.attributes["fan_rpm"] }}' psu_capactiy: friendly_name: 'Capacity' value_template: '{{ states.sensor.corsair_psu.attributes["capacity"] }}' psu_12v_watts: friendly_name: '12v Watts' value_template: '{{ states.sensor.corsair_psu.attributes["12v_watts"] }}' psu_5v_watts: friendly_name: '5v Watts' value_template: '{{ states.sensor.corsair_psu.attributes["5v_watts"] }}' psu_3v_watts: friendly_name: '3v Watts' value_template: '{{ states.sensor.corsair_psu.attributes["3v_watts"] }}' psu_watts: friendly_name: 'Current Load' value_template: '{{ states.sensor.corsair_psu.attributes["watts"] }}' psu_load: friendly_name: 'Current Load Percentage' value_template: '{{ states.sensor.corsair_psu.attributes["load"] }}' psu_uptime: friendly_name: 'Uptime' value_template: '{{ states.sensor.corsair_psu.attributes["uptime"] }}' psu_poweredon: friendly_name: 'Total Power On Hours' value_template: '{{ states.sensor.corsair_psu.attributes["poweredon"] }}' I will likely tweak it to add raw values in the php file so you can get temp1 which would be 45°c or you can get temp1_raw which would be just 45 instead of 45°c

only my new version supports the new layout my understanding is something like this, replace value_json.temp1 with value_json.XXXX depending on which value you want. - platform: rest resource: "http://192.168.1.3:965/plugins/corsairpsu/status.php" username: root password: !secret unraid_password authentication: basic value_template: '{{ value_json.temp1 }}' headers: User-Agent: Home Assistant Content-Type: application/json EDIT: just tested it works.

I use home assistant my self. I could potentially implement a .PHP?value=temp1 or .PHP?value=fan_rpm etc but I think ha can just parse the JSON anyway

I would personally pull from http://TOWER/plugins/corsairpsu/status.php instead of ssh Your layout is the same as mine so I expect all PSU will be output 0 is 12v and output 1 is 5v and output 2 is 3.3v. my new dashboard panel version auto detects this anyway This is the output of the php page { "temp1":"44.2 \u00b0c", "temp2":"37.2 \u00b0c", "fan_rpm":"0.0 RPM", "capacity":"1000W", "12v_watts":"72.0W", "5v_watts":"24.5W", "3v_watts":"11.0W", "watts":"106.0W", "load":"11%", "vendor":"CORSAIR", "product":"RM1000i", "uptime":"6d. 12h", "poweredon":"159d. 3h" }

I plan on adding progress/percent bars if i figure out how the existing progress bars work on the dashboard not released yet, code is super messy UPDATE: Now released. please note that currently this uses a bit of a hack to make it work as a dashboard panel, it doesn't currently support moving the panel (well it does move but it wont stick) i know a way to fix this but haven't got the time to do this right now, it's christmas lol. Beta version as shown above can be downloaded from https://raw.githubusercontent.com/Cyanlabs/corsairpsu-unraid/beta/corsairpsu.plg

i'm also working on a proper "dashboard" panel, the code works just deciding how to lay it out now. and the code is a bit messy as there is no official way to hook in to the dashboard panels.

12v is usually mechanical side of the hard drives, graphics cards etc. 5v is the logic controllers of the hard drives usually and sometimes 3.3v aswell I think if you are trying to reduce power only looking at 12V would be your best bet. EDIT: to make sure you have the rails correctly indentified send me the output of corsairmi via ssh/terminal

@LintHart I have forked the code and tweaked the layout adding 3.3v 5v and 12v and removing the badly named GPU load label. To install, go to Plugins > Install Plugin and paste https://raw.githubusercontent.com/Cyanlabs/corsairpsu-unraid/master/corsairpsu.plg Changelog Tidied up the uptime removing the raw time and showing just the days / hours Changed nominal power label to capacity and added W on the end Changed Watts to W (personal preference) Removed GPU load and added 12v, 5v and 3.3v loads

This isn't really related to this post but even a quick google search shows that you need to map /etc/grafana/grafana.ini or maybe the whole /etc/grafana folder in the docker container to get to the grafana.ini file located at this location, maybe try asking for help in the grafana docker thread or github pages?

https://grafana.com/docs/installation/behind_proxy/#examples-with-sub-path-ex-http-foo-bar-grafana

Just been trying to get this to work with no success until i realised my VLANS were causing the issue. I worked around it by overriding the code in the /etc/rc.d/rc.libvirtwol file. i replaced the variable $BRNAME directly with the hard coded value br0.1 (for br0 vlan 1) is it possible to get some sort of option for this added to the plugin?

You have to wait now before it will let you cert again, most likely your DNS hadn't propogated across the net so letsnecrypt wasn't going to the correct domain/ip

yes

did you restart the letsencrypt docker?

thats only to do with netdata, tbh i need to update my config example as mine is so much cleaner now.

its https you need to go to https://192.168.1.43:444 but really you should be accessing it from a domain externally even when internal

VALIDATION http you need to add that value to the docker

you cant use letsencrypt without public ip access you need to forward those ports

you need to ask in the letsencrypt docker thread. also make sure all your values are right in the docker such as domain name and stuff, no simple typo's, also try setting it to not use subdomains and put your domain jxxxxx1.duckdns.org as the main url/domain

just edited to say that before you posted but yeah

no you need to access it from your external IP or from your DNS not from the 192.168.1.104 address so you need to forward port 80 on your router to 85 and then try it from your duck dns address