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

System Restore #43

Closed
bindingofman opened this issue Oct 9, 2024 · 13 comments
Closed

System Restore #43

bindingofman opened this issue Oct 9, 2024 · 13 comments

Comments

@bindingofman
Copy link

Hello,
Is it possible to add the Återställ switch to the integration.
Sometimes my machine needs a reboot. :)

Screenshot_20240408_120752_Chrome~2

@bj00rn
Copy link
Owner

bj00rn commented Oct 15, 2024

Implementing support is a bit tricky (not impossible though) I’m afraid. All the settings on the ”maintenance” page requires the websocket connection to be authorized using the master password. Implementing support would require:

  • a mechanism for password authorization (and probably reauthorization in case of websocket reconnect)
  • password setting to integration config flow

Side note; why do you need to reset the device?

@bindingofman
Copy link
Author

bindingofman commented Oct 16, 2024 via email

@bj00rn
Copy link
Owner

bj00rn commented Oct 16, 2024

Yeah, that's what I began to think after sending the request. Our unit is in an insulated (but not heated) extension to the house. I often get warnings about the supply air temperature is to low, and I need to clear them, occasionally the unit shuts down if the temp difference is 8°c, and thus needs the restart. But I can probably get around this by adjusting the required set temperature and air flow for the night, and have it kick back up in the morning.

On Tue, 15 Oct 2024, 22:49 Björn Dalfors, @.> wrote: Implementing support is a bit tricky (not impossible though) I’m afraid. All the settings on the ”maintenance” page requires the websocket connection to be authorized using the master password. Implementing support would require: - a mechanism for password authorization (and probably reauthorization in case of websocket reconnect) - password setting to integration config flow Side note; why do you need to reset the device? — Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2B5XMVY7RYQGBOGSC4JS2TZ3V5U3AVCNFSM6AAAAABPUHAF7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJVGA3TENZWG4 . You are receiving this because you authored the thread.Message ID: @.>

I had the same problem with shutdowns, I don’t want to the electric heater to kick in at night while still keeping heat rotor at 100% during the day to preserve energy.

I find If I use Svalka/Cool temperature mode with cooling mode activated, and set the temperature to a decent low setting, like 15-16 degrees, the unit will only activate electric heater if the supply air drops below this level. Heat rotor will stay at 100% even when supply air temperature is above this level since it’s trying to cool the supply air thus heating it instead.

Not the intended use of cooling mode of course, but hey it works.

@Fettkeewl
Copy link

I second the need for accessing the maintenance page =)
I too would like to be able to control when the heater should turn on aswell as be able to adjust the
temp value limit in order to maximize rotor efficiency, (currently i must manually change my summer/winter temperatures to avoid the rotor spinning down).

@bindingofman
Copy link
Author

Screenshot_20241019_095602_Home Assistant
Did you decide to give it a go?

@bj00rn
Copy link
Owner

bj00rn commented Oct 19, 2024

Screenshot_20241019_095602_Home Assistant Did you decide to give it a go?

Not sure what that is

@bj00rn
Copy link
Owner

bj00rn commented Oct 19, 2024

Looks like unlocking maintenance is as simple as sending payload with password

#IP:6666

This should probably before any call to maintenance commands.

Off/On, and reset looks fairly simple to implement. Feel free to PR :-)

@bj00rn
Copy link
Owner

bj00rn commented Oct 19, 2024

@Fettkeewl @bindingofman checkout pre-release https://github.com/bj00rn/ha-saleryd-ftx/releases/tag/v3.1.3-rc.0

I've implemented service to set system active mode (on, off, reset)
Unlock maintenance settings service must be called manually first with maintenance password

@bindingofman sidenote, Supressing the temperature warning/shutdown sounds fishy...

@bj00rn bj00rn closed this as completed Oct 19, 2024
@bindingofman
Copy link
Author

bindingofman commented Oct 19, 2024 via email

@bj00rn
Copy link
Owner

bj00rn commented Oct 19, 2024

@Fettkeewl @bindingofman target temperature now be set too, check out https://github.com/bj00rn/ha-saleryd-ftx/releases/tag/v3.1.3-rc.1

@bj00rn bj00rn reopened this Oct 19, 2024
@Fettkeewl
Copy link

@Fettkeewl @bindingofman checkout pre-release https://github.com/bj00rn/ha-saleryd-ftx/releases/tag/v3.1.3-rc.0

I've implemented service to set system active mode (on, off, reset) Unlock maintenance settings service must be called manually first with maintenance password

@bindingofman sidenote, Supressing the temperature warning/shutdown sounds fishy...

Could this unlocking not be a part of the process of those actions that require maintenance password?

  • User wants to change target temperature
  • User provides new set temperature
  • User provides maint. pass

All in the same service, then you internally in the integration check if the user provided correct pw and you have access to maintenance page?

Seems like an unnecessary step to have a specific service solely for unlocking the page :)
Just food for thought!

@bj00rn
Copy link
Owner

bj00rn commented Oct 21, 2024

@Fettkeewl @bindingofman checkout pre-release https://github.com/bj00rn/ha-saleryd-ftx/releases/tag/v3.1.3-rc.0
I've implemented service to set system active mode (on, off, reset) Unlock maintenance settings service must be called manually first with maintenance password
@bindingofman sidenote, Supressing the temperature warning/shutdown sounds fishy...

Could this unlocking not be a part of the process of those actions that require maintenance password?

  • User wants to change target temperature
  • User provides new set temperature
  • User provides maint. pass

All in the same service, then you internally in the integration check if the user provided correct pw and you have access to maintenance page?

Seems like an unnecessary step to have a specific service solely for unlocking the page :) Just food for thought!

Agree! Ideally password should be saved in integration config flow. I think its probably best to send unlock behind the scenes on every call to maintenance settings in each service in case the unlock has been lost for some reason. There currently no way to detect if a command to the FTX fails.

Maybe also a checkbox in configuration flow to enable/disable maintenance settings. Might be useful if we expose more sensitive/dangerous parameters such as fan speed etc,

@bj00rn
Copy link
Owner

bj00rn commented Oct 24, 2024

Try v4 release, i've removed the unlocking service. You need to reconfigure the integration, enable maintenance settings and set password there. "Maintenance services" will work out of the box.
image

@bj00rn bj00rn closed this as completed Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants