search

sebr / bhyve-home-assistant

Orbit BHyve custom component for Home Assistant
MIT License
251 stars 42 forks source link

trying to control a 57946 controller (supposedly supported) #250

Closed GHSTUDIO1 closed 1 month ago

GHSTUDIO1 commented 2 months ago

Many issues

1) I have three switches (for my 3 programs). All are defined, but all are unavailable.

2) the switch names are switch.zone; switch.zone_1_zone_2; switch.zone_3 (zone 2 is wrong)

3) I can't find any "rain delay" switch

4) I only see one program switch with none of the attributes shown in the documentation.

-->

sebr commented 2 months ago

You need to add the device diagnostics, as requested in the issue template

GHSTUDIO1 commented 2 months ago

I have the following in my configuration.yaml file:

logger:

default: critical

logs:

custom_components.bhyve: debug

pybhyve: debug

However, I don’t see any log entries.

I’ve checked and Bhyve is in my custom components folder and I have a (normal) warning message:

2024-06-28 07:51:29.095 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bhyve which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

But there are no log entries. Am I looking in the wrong place???

BTW, the device integration shows as UPNP……it should show Orbit as it’s name, shouldn’t it???

From: Seb Ruiz @.> Sent: Friday, June 28, 2024 1:40 AM To: sebr/bhyve-home-assistant @.> Cc: GHSTUDIO1 @.>; Author @.> Subject: Re: [sebr/bhyve-home-assistant] trying to control a 57946 controller (supposedly supported) (Issue #250)

You need to add the device diagnostics, as requested in the issue template

— Reply to this email directly, view it on GitHub https://github.com/sebr/bhyve-home-assistant/issues/250#issuecomment-2196179491 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALT3EX7ZXUJW62RIHHRF5MDZJTZLTAVCNFSM6AAAAABKA3TUKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJWGE3TSNBZGE . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ALT3EX6SCPD52USWLZW557TZJTZLTA5CNFSM6AAAAABKA3TUKCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUC44FCG.gif Message ID: @. @.> >

sebr commented 1 month ago

Please attach the Home Assistant diagnostics for the B-hyve device. Sensitive information is redacted when compiling the diagnostic data.

GHSTUDIO1 commented 1 month ago

orbi_debug.txt

sebr commented 1 month ago

@GHSTUDIO1 I cannot help you if you do not follow instructions.

GHSTUDIO1 commented 1 month ago

I followed the instructions. Debug is on and I sent you the log Is it the wrong log???

From: Seb Ruiz @.> Sent: Sunday, June 30, 2024 11:23 PM To: sebr/bhyve-home-assistant @.> Cc: GHSTUDIO1 @.>; Mention @.> Subject: Re: [sebr/bhyve-home-assistant] trying to control a 57946 controller (supposedly supported) (Issue #250)

@GHSTUDIO1 https://github.com/GHSTUDIO1 I cannot help you if you do not follow instructions.

— Reply to this email directly, view it on GitHub https://github.com/sebr/bhyve-home-assistant/issues/250#issuecomment-2199156133 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALT3EXYNNGH4TPDHJIM2AS3ZKDDSFAVCNFSM6AAAAABKA3TUKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJZGE2TMMJTGM . You are receiving this because you were mentioned. https://github.com/notifications/beacon/ALT3EX3SY2DDC64SO2EYRLDZKDDSFA5CNFSM6AAAAABKA3TUKCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUDCR22K.gif Message ID: @. @.> >

sebr commented 1 month ago

At this stage I don't need your logs, but rather the device diagnostics. I refer you to my comment here:

https://github.com/sebr/bhyve-home-assistant/issues/250#issuecomment-2198514160

GHSTUDIO1 commented 1 month ago
  1. I can’t find a diagnostics integration … so I can’t add it. I have tried looking at system integration, Haacs and addins. If there is an integration I should have for this, I don’t know how to addit.
  2. Diagnostics,py is installed in the custom components section with your other code.
  3. I don’t have an option to print out any diagnostic data….the only thing I can send is what I sent.

I wish I could find the diagnostics integration that is supposedly included in the Home Assistant package. Note: I added diagnostics: to my comfiguration.yaml which didn’t change anything

I’m trying to help get this fixed….I must be missing something.

From: Seb Ruiz @.> Sent: Sunday, June 30, 2024 11:50 PM To: sebr/bhyve-home-assistant @.> Cc: GHSTUDIO1 @.>; Mention @.> Subject: Re: [sebr/bhyve-home-assistant] trying to control a 57946 controller (supposedly supported) (Issue #250)

At this stage I don't need your logs, but rather the device diagnostics. I refer you to my comment here:

250 (comment) https://github.com/sebr/bhyve-home-assistant/issues/250#issuecomment-2198514160

— Reply to this email directly, https://github.com/sebr/bhyve-home-assistant/issues/250#issuecomment-2199176645 view it on GitHub, or https://github.com/notifications/unsubscribe-auth/ALT3EX6FSHDB7MJGX6ZKGNDZKDGX7AVCNFSM6AAAAABKA3TUKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJZGE3TMNRUGU unsubscribe. You are receiving this because you were mentioned. https://github.com/notifications/beacon/ALT3EX7YCSRZFYMIKHDNNTTZKDGX7A5CNFSM6AAAAABKA3TUKCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUDCTC4K.gif Message ID: < @.> @.>

sebr commented 1 month ago

Diagnostics is enabled and bundled by default.

Did you look at the screenshot? https://user-images.githubusercontent.com/81972/179869298-3d2a33ca-f847-4a25-8e77-20757e49f914.png

GHSTUDIO1 commented 1 month ago

close this issue.....the problem was that the integration did not load correctly.

On my initial install, I entered an incorrect password at least twice and the integration remembered the incorrect password. Attempting to reinstall, I got a message that the integration had already been registered, but as I said, it was registered with the wrong password so the integration was unable to start.

The resolution was to delete the bhyve section in /homeassistant/.storage/core.config_entries and reinstall the integration. I might have been able to fix by just replacing the password in core.config_entries, but I chose to just delete that section.