[Bug]Doesn't work with OMV in NanoPC T6 (FriendlyElec) about homeassistant-openmediavault HOT 11 CLOSED

looks like a broken api. I would need to see debugs

from homeassistant-openmediavault.

Thank you...but it's strange that the same "installation" is working fine with the CM3588 and not with the T6.

Can I help you sending debugs?

from homeassistant-openmediavault.

well, I need to see those debugs to know what is happening.

from homeassistant-openmediavault.

from homeassistant-openmediavault.

https://github.com/tomaae/homeassistant-openmediavault?tab=readme-ov-file#enabling-debug
debugs will be in ha log

from homeassistant-openmediavault.

Thanks but it's very strange because now it's working "fine" ;)

Only there is a bug:

As I explained I have two OMV installed: OMV (in the CM3588) and OMV_T6 (in the T6)

As you can see in the attached figure there is a problem with the device "SERVICES" name.

It would be OMV**_T6** services...

but not OMV_ service... services_2

from homeassistant-openmediavault.

we will know more from debugs, without them its not possible to tell whats happening in this case.

from homeassistant-openmediavault.

I attach the two last ha.log ... when it's "working"

ha.log.zip

from homeassistant-openmediavault.

Seems to be working correctly. Are you sure those are not leftover entities from previous tries?
Only entity I see crashing is following: sensor.buhardilla_dect but I dont think its related.

from homeassistant-openmediavault.

@tomaae
As I was saying, although it’s strange, the issue resolved on its own, and this LOG is after the problem, so it’s logical that nothing related to it appeared. On the other hand, indeed, the other entity has nothing to do with it.

Thank you and sorry for the inconvenience. 😊

from homeassistant-openmediavault.

no problem, I guess OMV went bit crazy. I seen that happen few times

from homeassistant-openmediavault.