Phasak PH 7690 UPS

This UPS Uses the same card as CyberPower

This means that if I change the includes/definitions/cyberpower.yaml to:

os: cyberpower
text: Cyberpower
type: power
icon: cyberpower
over:
    - { graph: device_voltage, text: Voltage }
    - { graph: device_load, text: Load }
discovery:
    -
        sysObjectID:
            - .1.3.6.1.4.1.3808
poller_modules:
    ports: false
discovery_modules:
    ports: false
snmp_bulk: false

removing the

        sysDescr_except:
            - 'Power Management Card'

from the original file, It is detected fine.

Can you please create a new device category for this ups?

I would also like it to be added specifically for Phasak’s model.

It is also the same module as PowerWalker: SNMP Card 2 | BlueWalker

PowerWalker doesn’t have the sysDescr_except mentioned on the post from OP. But the sysObjectID is different, even though the MIBs given on the PowerWalker website are .1.3.6.1.4.1.3808.

MIBs available at Software | BlueWalker , on the SNMP Card 2 section.

I have two different generation Phasak UPS that uses two different SNMP cards:

PH 7690 SNMP Module and
PH 9100

One of them is detected as CyberPower (the one I mentioned when I opened this thread) if I remove the

sysDescr_except:
- ‘Power Management Card’

The other one is detected as Orvaldi UPS without changing anything.

Anyway, in both cases the reported values are correct.

So it looks like it would be “easy” to get a proper definition for PHASAK.

Hi @SPP

It is very common in the UPS world to use the same SNMP card for a lot of devices and brands, making it difficult (and sometimes impossible) to differentiate them …

For the first one, I guess that the “except” was added to prevent the detection by this YAML and probably match another brand/device using the same card with a different name. So removing simply is probably not the solution (will break the other one). Finding the PR where this except was added will probably help find the other (if any) OS that is similar, and from their, you can decide to create another exception or include your device in one of the existing ones.

For the 2nd one, if it is detected correctly, I would stick with it, simply to avoid creating a new scenario like the above. It will specify another vendor name but your UPS will be detected as expected, which is what matters at the end of the day.

Bye