Closed CBDesignS closed 2 months ago
So if this is not fixed it will no longer work in HA? I was just about to purchase the hat,but not sure what to do now.
it will work up to Nov 2024 as that is when 2024.11 will be due to be released. This should be fixable by the repo/code owner and be a seamless update once they get round to it, or even someone else may clone the repo and fix it as there seems to be a few users that use this.
Hmm it seems someone has forked this and added some fixes,but unfortunately not for this problem!
if Andrew fixes the bugs and his code works it might be better to use his fork until this repo pulls the updates. HA complains about a couple of other things, the battery reporting unit and summit else I can not think of right now. unfortunately this level of code is well above my station so I have to wait on others doing the hard work fixing things, we have to hope others can help or we might be stuck until someone than uses the ups come up with a fix.. I here Argon40 are working on an ups device for there cases so maybe it might be similar and we can use their code if push comes to shove, or use some of their code to fix this.
You have been most helpful with this,but i am still sitting on the fence about purchasing the waveshare ups. Is there a method other than this for implementing the ups for safe shutdown,in case no fixes are forthcoming? I am using hassio on a raspberry pi 3 and have had sd cards corrupted in the past through power cuts. And i am not sure if it is possible to use the waveshare default scripts in hassio,at least that would be a backup just without the integration and dashboard stuff. Any advice would be greatly appreciated.
I just installed this and used it as is. I think there is similar version of this but with less bells and whistles but I can not remember if its was in the hacs store or it was a link to add it to the hacs store. If I find the link I will let you know.
As for the corrupt sd card, its the big down side of using a raspy pi in any scenario, they corrupt with ease and it is advised to use an external drive of some kind when using hassio mainly due to the amount of data writing and reading, (make sure you also backup your data daily, the addon I use backs up locally and to a google drive account, if the shit hits the fan and the hdd dies I still have a G drive backup I can restore) I used to use a laptop 2.5" hdd in a usb caddy since the pi can boot form usb, I then upgraded to a 2.5" ssd drive in the same caddy and the load times were 1/2 that of the hdd. Then I moved up a pi 4 and got the Argon40 case with built in ngff ssd . Now about 6 months later it looks like I am going to have to retire the rpi4 and build a small pc to run the whole thing as I am out growing the power of the rpi4. 90% of my house is now controlled by HA, from boiling the kettle, lowering the lounge blinds when its dark , telling me there is a person outside the door right thru to monitoring the temperature of each room. A guy in one video I watched said using HA is akin to being addicted to crack, the more you use it the more you want to use it and it takes over our life..
Yes there is another in the hacs store https://github.com/uvjim/rpi_waveshare_ups Don't know if there are any install problems though. If it works it may be a backup if there is no fix. Thank you.
Unfortunately, I can't find any of these errors in the logs. Could you provide me with more information?
Fixed with #17
thanks @odya.
Now I have the problem of finding the i2c address. in hassio on the pi I have no way that I can find to get the correct address to use in the new settings. i2cdetect is not available to me. I know i2c is active because my argon40 fan works and reports the temperature changes every 30 seconds. the ups used to give me the sensor data but now all I get is error after error using the address of 0x41. Any ideas what to do next @odya
using the setup for Argon40 I found the address and it is correct at 0x1a & the ups is at 0x41 so all good there.
Detecting Layout of i2c, we expect to see "1a" here.
checking i2c port 0 at /dev/i2c-0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
not found on /dev/i2c-0
checking i2c port 1 at /dev/i2c-1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- 41 -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
found at /dev/i2c-1
I2C Port 1
Settings initialized. Argon One Detected. Beginning monitor..
2024-07-07_22:51:33: 46C - Fan 3% | hex:(0x03)
now I just need to get the sensors working.
my log file just shows failed to start.
@CBDesignS In latest versions config format was changed https://github.com/odya/hass-ina219-ups-hat/blob/master/README.md Seems like you have ina219 on channel 1 0x41. This is default channel and addr. Maybe changes in latest versions fixed your problem?
I got it sorted just forgot to close the issue here. It worked great but I had to upgrade my system from the Rpi 4 to an i5 Nuc with 16gb ram to keep up with the addons and HA in general as I was pushing the pi 90% cpu usage under daily use. thx
Just a heads up that Home assistant is depreciating accesses hass.helpers.discovery.. the HA Logs show the following warning:-
Detected that custom integration 'ina219_ups_hat' accesses hass.helpers.discovery. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from discovery directly at custom_components/ina219_ups_hat/sensor.py, line 70: hass.helpers.discovery.load_platform('binary_sensor', DOMAIN, {, please create a bug report at https://github.com/odya/hass-ina219-ups-hat/issues Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 645: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues