Skip to content
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

Aurora ABB Powerone Intergration Serial port selection #137281

Closed
BrenD24 opened this issue Feb 4, 2025 · 8 comments
Closed

Aurora ABB Powerone Intergration Serial port selection #137281

BrenD24 opened this issue Feb 4, 2025 · 8 comments

Comments

@BrenD24
Copy link

BrenD24 commented Feb 4, 2025

The problem

When setting up the intergration only the TTYs0 and TTYs1 serial interfaces are preseneted dispite there being more ports avalable

What version of Home Assistant Core has the issue?

Core-2025.1.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Aurora ABB Powerone Solar PV

Link to integration documentation on our website

https://www.home-assistant.io/integrations/aurora_abb_powerone/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Feb 4, 2025

Hey there @davet2001, mind taking a look at this issue as it has been labeled with an integration (aurora_abb_powerone) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of aurora_abb_powerone can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign aurora_abb_powerone Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


aurora_abb_powerone documentation
aurora_abb_powerone source
(message by IssueLinks)

@BrenD24
Copy link
Author

BrenD24 commented Feb 4, 2025

Some Images to add context incase my explaination isnt clear

Image

Image

@davet2001
Copy link
Contributor

Hi @BrenD24 thanks for reporting this issue!

I'm sorry to hear that you are having problems making a connection.

The available ports in the web based setup for Aurora ABB Powerone should be the same as the ports listed by

python3 -m serial.tools.list_ports -s

If you are able to run this command from a terminal where HA is running, please tell me the output.

If that's not possible, could you tell me which hardware you are running on?

Thanks!

@BrenD24
Copy link
Author

BrenD24 commented Feb 4, 2025

Hi, @davet2001 ,

The system is running Home assistant OS and not sure how to get to a shell on it to run the command.
The system is running atop VMware ESXi 7

ha hardware info shows the bellow output on serial ports however, not sure if it is helpful.

`- attributes:
DEVNAME: /dev/ttyS0
DEVPATH: /devices/pnp0/00:06/tty/ttyS0
MAJOR: "4"
MINOR: "64"
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: "3956810"
by_id: null
children: []
dev_path: /dev/ttyS0
name: ttyS0
subsystem: tty
sysfs: /sys/devices/pnp0/00:06/tty/ttyS0

  • attributes:
    DEVNAME: /dev/ttyS1
    DEVPATH: /devices/pnp0/00:07/tty/ttyS1
    MAJOR: "4"
    MINOR: "65"
    SUBSYSTEM: tty
    TAGS: ':systemd:'
    USEC_INITIALIZED: "3956875"
    by_id: null
    children: []
    dev_path: /dev/ttyS1
    name: ttyS1
    subsystem: tty
    sysfs: /sys/devices/pnp0/00:07/tty/ttyS1

  • attributes:
    DEVNAME: /dev/ttyS2
    DEVPATH: /devices/platform/serial8250/tty/ttyS2
    MAJOR: "4"
    MINOR: "66"
    SUBSYSTEM: tty
    TAGS: ':systemd:'
    USEC_INITIALIZED: "3956702"
    by_id: null
    children: []
    dev_path: /dev/ttyS2
    name: ttyS2
    subsystem: tty
    sysfs: /sys/devices/platform/serial8250/tty/ttyS2

  • attributes:
    DEVNAME: /dev/ttyS3
    DEVPATH: /devices/platform/serial8250/tty/ttyS3
    MAJOR: "4"
    MINOR: "67"
    SUBSYSTEM: tty
    TAGS: ':systemd:'
    USEC_INITIALIZED: "3956731"
    by_id: null
    children: []
    dev_path: /dev/ttyS3
    name: ttyS3
    subsystem: tty
    sysfs: /sys/devices/platform/serial8250/tty/ttyS3`

@davet2001
Copy link
Contributor

Ok, not easy to get a command terminal within the HA container if you've not already done that before. Probably not essential to debug this. If you want to try, it is possible using the 'Terminal & SSH' addon.

Technical info: If the system is reported as linux (which I believe HA OS will), this code is what is generating the serial port list:
https://github.com/pyserial/pyserial/blob/7aeea35429d15f3eefed10bbb659674638903e3a/serial/tools/list_ports_linux.py#L91-L106
Note that (see last line) this listing will try to hide what it deems as non-present internal serial ports.

Do you have 4 real serial ports?
How are they implemented and do they pass through to physical serial ports on your host machine?

The most common RS485 adaptors I see usually show up as /dev/ttyUSB0,/dev/ttyUSB1,/dev/ttyUSB2, etc.

@BrenD24
Copy link
Author

BrenD24 commented Feb 4, 2025

VMWare is presenting presenting a virtual serial port from a Serial<>Ethernet Bridge (i.e. VMWare is handling the Network stuff).

The machine is only supposed to have one serial port as far as i know but i will have a dig deeper into what they are.

I have confirmed the bridge and everything works correctly (On a different VM with the same settings)

I acctualy think this may be a Driver issue now that i have dug a bit deeper, when i remove the Serial port from the VM the same 4 ports exsist

@BrenD24
Copy link
Author

BrenD24 commented Feb 5, 2025

Had a win,

the OVA image i used to install Homeassistant OS was in VMWare compatability for V5.5 upgraded it and it seems to be working now

@davet2001
Copy link
Contributor

Ok thanks for clarifying. Please reopen if this is not resolved.

@davet2001 davet2001 closed this as not planned Won't fix, can't repro, duplicate, stale Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants