sensor.argon_one_addon_fan_speed entity not created (anymore) #61
Comments
|
I concur with @pascalkrielen on this too. Having recently started with HA and now fallen down that rabbit hole, I have upgraded and purchased the Argon case. I came across @adamoutler's excellent addon, installed, configured and it works perfectly so thank you very much for the effort here. However, not that it's a major issue but I just can't find the fan entity. I've configured, restarted, rebooted, turned off and read the whole community thread but still no entity. Standard HAOS build, nothing fancy. |
|
Same problem here. Since update to `
|
|
Same issue here, apparently with the latest changes in HA |
|
Not sure how to handle this. I cannot reproduce. |
|
This problem is related to issue " Post sent to supervisor is invalid (unix2dos not working) #60" as I had it when Supervisor got updated to 2023.07.2 version of Supervisor.... it has to do with the AIOHTTP package. |
|
I have lost the speed sensor too. |
|
I've been doing all my updates and hearing about this problem and checking every day. I just rechecked. This is the first abnormality I've seen with my unit as of last night at ~18:00EST I see the following message within my Supervisor logs. The following test demonstrates the problem and can be run with SSH&Terminal addon via ssh docker exec -it $(docker container ls|grep argon|sed 's/ .*//' ) bash #open a bash script in the Argon container
#run the actual problematic command used, but add dummy data
fanPercent=100
icon=mdi:fan-speed-3
fanMode=High
CorF=C
cpuTemp=199
fanLevel=3
reqBody='{"state": "'"${fanPercent}"'", "attributes": { "unit_of_measurement": "%", "icon": "'"${icon}"'", "mode": "'"${fanMode}"'", "Temperature '"${CorF}"'": "'"${cpuTemp}"'", "fan level": "'"${fanLevel}"'", "friendly_name": "Argon Fan Speed"}}'
nc -i 1 hassio 80 <<< unix2dos<<EOF
POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1
Authorization: Bearer ${SUPERVISOR_TOKEN}
Content-Length: $( echo -ne "${reqBody}" | wc -c )
${reqBody}
EOFI can observe the following response with the above test HTTP/1.0 400 Bad Request
Content-Type: text/plain; charset=utf-8
Content-Length: 307
Date: Wed, 09 Aug 2023 19:04:43 GMT
Server: Python/3.11 aiohttp/3.8.5
Invalid header value char:
b'Authorization: Bearer 250099d1de7c4c97b63b533168c8de287f61d9387715686a199571615bde5bcc128869bf5eef4466ac3aa07affe2ec209d769a98ead32fbf'I don't have time to troubleshoot right now, but later tonight. |
|
Ran my test and expected results through ChatGPT and it provided this. I'm going to see if I can clean it up a bit. I like the idea of having the entire request written out the way it was before. I'll see if I can do something better. |
|
Sounds positive. Thanks for the details and the effort @adamoutler. I'm intrigued by how you are using ChatGPT to help troubleshoot. |
|
Yes, thanks for looking into it so quickly. The use of ChatGPT is intriguing.
… On Aug 9, 2023, at 1:28 PM, Yorkie71 ***@***.***> wrote:
Sounds positive. Thanks for the details and the effort @adamoutler <https://github.com/adamoutler>. I'm intrigued by how you are using ChatGPT to help troubleshoot.
—
Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHOJDTKJ4RVQW56XONCRN23XUPQELANCNFSM6AAAAAA3F2HVEQ>.
You are receiving this because you commented.
|
|
So I came up with this replacement method. Keeping in mind that we are trying to avoid using binaries when possible, this method is technically superior. If you add this repo, not the adamoutler/addons repo, then you can get your sensor back now. The problem is it is both updating the sensor, and causing an error in the supervisor with each tick. I'll work on it tomorrow about this time. I spent most of today debugging for changes in the build system environment since the last build. |
|
Anyone using this repository should try updating to version 30a AFTER these checks pass and the build system gives a green light. https://github.com/adamoutler/HassOSArgonOneAddon/actions/runs/5825999372 I'll push to the production repo, adamoutler/addons later tonight assuming no problems. Let me know about your results in ArgonOne, ArgonOne Classic, and ArgonOne Linear. |
|
Green light, go! |
|
Just updated the package and now I see the entity is listed. Nice work. Thanks. |
|
Same here, updated to 30a and it is back, thanks @adamoutler |
|
It's all right now. After the update it works as expected. Many Thanks you act so quick. |
|
works again. Thanks |
|
Great! Having problems with pushing to production automatically |
|
Amazing - THANK YOU! This add-on rocks and I am so glad to have the entity back! |
I found that for some time now the sensor.argon_one_addon_fan_speed entity is not created anymore.
Not sure when this started to happen as multiple updates were probably installed before I noticed the thing being gone.
I tried deinstalling and re-installing both the "normal" and the "linear" version, but both only provide a sensor called something like update.argonone_active_linear_cooling_update
The logs do show the basic functionality is working though, so it does its job, but would be nice to have the sensor entity so it also shows this in the dashboard and history.
The text was updated successfully, but these errors were encountered: