-
-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HCL] TED Electric 3100VA 1800W UPS Line Interactive supported by probably Richcomm #2590
Comments
Hello, try increasing the debug verbosity for the driver ( |
Hi @jimklimov - thank you for the reply.
These are the log levels I have in the addon: Anything I can try? |
I ran again the addon with Trace as debug level and here is the output:
|
These options seem to bump the debugging of HA scripts, not NUT programs (driver in particular). They do have a bit of effect, with the driver's logs getting a timestamp and lines' debug level prefix (e.g. Unfortunately I am not a HA user so can't help directly about it, more so when it is a VM, so can only suggest generic ideas at the moment: check that the host system does not have any software attached to the device (e.g. a NUT driver or something else), and that it is not forwarded to any other guests. If you have a chance to rule out more moving parts, by checking if the UPS is seen by NUT on a bare-metal machine (e.g. install/build it on the host of that HA VM), that would be helpful. In the end, you are managing physical power of physical computers, and whatever automation a mere VM does to e.g. command the UPS to power off can be minutes away from the other VMs or the host itself being ready to kick the bucket (ordering it to go down last in case of shutdown can help though, but...) Also, this is one of a couple of drivers (along with Perhaps ask that community or docs to see how the |
Regarding custom NUT builds, please take a look at https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests and the docs it mentions for dependency lists for various platforms. You can test a driver from the build workspace, without changing the OS there. If you are crafty, you can also custom-build the dependencies (e.g. libusb) to use from the temporary or homedir based installation, and avoid putting those into the OS too as long as you are "just testing". Be sure to NOT have the device actively forwarded to a VM when trying to use it in the host OS context. Another idea is to follow the community-contributed notes https://github.com/networkupstools/nut/wiki/Building-NUT-integration-for-Home-Assistant about building your own newer HA plugin with a specified NUT version. I believe originally it relies on packaged NUT, so you would have to craft that, or adapt the recipe to install dependencies and build NUT as part of creating the container with the plugin. |
Hi, |
I wonder if you "may" do such re-publication of binaries here, license-wise. Do they have a download link of such ISO or files it contains? |
As for your existing deployment, to step back in complexity:
This might expose some system-level issues (e.g. permissions or poorly written settings - as I wrote above, I am concerned about a couple of keywords that may be present in config and may be rejected by this driver). Building your own (NUT and plugin) is a next-level option to check if newer code fares better with your device; eventually perhaps experiment with some fixes to the driver to help it support your device model, if it does not yet. |
Ok, I managed to get the software online (https://powermanagerlite.software.informer.com/download/) I connected my laptop to the USB of the UPS after installing the PowerManager lite software and it detects the UPS. So it means that the driver from this package works. And it also has Linux Drivers in the package. |
Hi @jimklimov ,
So it detects ok the USB as Richcomm usb driver
Any idea on how to debug further why is not working? Also, running:
|
One clue is the reported fatal error. Another would (probably) be that this driver does not have options for Also with NUT 2.8.0 and newer, on OSes with systemd, the nut-driver-enumerator may create a service unit for each driver which would conflict with manual |
Hi Jim,
So, what are my next steps?
Sent from mobile phone
mie., 21 aug. 2024, 21:16 Jim Klimov ***@***.***> a scris:
… One clue is the reported fatal error.
Another would (probably) be that this driver does not have options for
vendorid/productid and would next complain about these.
Also with NUT 2.8.0 and newer, on OSes with systemd, the
nut-driver-enumerator may create a service unit for each driver which would
conflict with manual upsdrvctl runs.
—
Reply to this email directly, view it on GitHub
<#2590 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEDBF6LJRKPAKGD4CT34OP3ZSTKRNAVCNFSM6AAAAABMJYXNXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBSGY4TAMBYG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
First, get the driver program running: comment away Check |
Hi,
Then, I ran the following commands:
If I run the following commands, I get:
Also, by running
In the end, by running the below commands I get the following:
I hope this helps in pinpointing the issue - or at least I hope so :) - can you advise further? |
Thanks! So far this one is the most important part:
The driver did get past its configuration options, but a callback to check if the device looks like it is supported did not recognize it. Logic-wise, it is called at Line 511 in c9132a5
Lines 236 to 281 in c9132a5
The logic here is simpler than in other USB-capable drivers:
If you add Also check if your system has It is also a possibility that this device does not fit this driver (billed as "dry-contact to USB driver") - maybe your UPS is newer and smarter than posting a few yes-no bits over USB, and needs some As a quick test with even older NUT versions,
This is actually an odd one, I can't quickly say. The |
Ok, so, I edited the
Then ran:
If I run:
Running
among a lot of other rules. Running a
I don't see anything regarding Richcomm in the rules file - should I add a new line there? and if so what? Thank you very very much for all your help. |
It's here. Glued to CPS block for some reason, but present:
As for the driver startup, logs (thanks!) indicate that the loop of 3 retries does behave differently on first and later cycles. With responsible code lines (to help track this fault down):
So on the first cycle it did pass "USB configuration" and a few other operations in the Maybe the "auto detach kernel driver from USB device" just before the loop is also at fault, at least it is not available on all systems out there. I think at this point I can only recommend a custom build of NUT from master branch per https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests and fiddling with the driver source to comment away the suspected culprits (one then another) and see if your device would become recognized. |
Hi @jimklimov |
Cheers, the Wiki article refers to Then you can run a built driver from the build workspace, e.g. stop the existing services and run By editing your copy of |
Hi,
I have recently purchased this TED Electric UPS (TED Electric 3100VA 1800W UPS Line Interactive - https://www.tedelectric.eu/product/3100va-1800w-ups-line-interactive-lcd-display-3-outputs-ted-electric/) and I want to add it to Home Assistant. In the packaging I found a CD pointing to Richcomm for drivers - and I am in the process of finding a CD-ROM to try to get those drivers from the CD and see at least who's the manufacturer.
From the NUT https://networkupstools.org/stable-hcl.html list, I have tested with almost all drivers I found listed, none of the worked, the only one that showed some promise was indeed the richcomm one, but with the below errors:
I have tested with both the USB cable that came in the box and also with another one, in the VM where the HA is hosted, I have 2 USB devices listed - I have connected them both to the VM:
Can someone please guide as to how I can add this UPS to HomeAssistant? The reasoning is that if I can add and monitor it via HA - then I can write automations to shutdown the environment and then the Synology in case the battery drops under a certain threshold.
Any help is greatly appreciated. And if I missed any information, please let me know and I will try to find it asap.
The text was updated successfully, but these errors were encountered: