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

Switching [to this] Fork #14

Closed
marq24 opened this issue Sep 9, 2023 · 0 comments
Closed

Switching [to this] Fork #14

marq24 opened this issue Sep 9, 2023 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@marq24
Copy link
Owner

marq24 commented Sep 9, 2023

Introduction - good to know

in order to address certain concerns switching to this fork (coming from mchwalisz/home-assistant-senec)

  1. This fork will use the same folders as the original in your ha-installation - so it's not possible to have both installed at the same time.

  2. Before you switch to this fork, you might like to create a backup of your current ha-installation - even if I tried hard to avoid any possible issues in the 'migration' - you never knows - and I can not test all possible scenarios that might exist in the world

  3. Even if I just used the word 'migration' - updating to this fork will not change anything on the configuration objects that the original code has created - so with other words I tried hard to be backward compatible - it is possible to remove the home-assistant-senec from your HACS - install this ha-senec-v3 one and restart your HA and you are all done!

    BUT when you switch to this fork cause you have the need to use https to communicate to your SENEC.Home in your LAN - this simple approach does NOT WORK - sorry! - So if you need https support please follow the described procedure below.

  4. When initially configuring this integration, you have the option to specify a display name - in order to be backward compatible with mchwalisz/home-assistant-senec version use 'Senec' as the display name (no matter of the case - so can be 'senec', or 'SENEC' or even 'seNeC'). If you decided to use something different the date of the original will not be picked up.

    When using 'senec' (as display name) all entities will continue to record it's data (since this Integration (LAN-based) is using the same names for the Sensors. Please note, that with the update you will get additional Sensors that did not existed in the original - but this should become no issue for you.

Switching to to ha-senec-v3 fork

As mentioned in 2.) above - you might like to create a backup first - have in mind - everything you do, you do on your own risk!

  1. Make sure that you have the latest Version of HA installed/running [the fork use some additional functionality that require a newer version of HA then the initial fork - see also error {"message":"Invalid handler specified"} when try to configure the integration

  2. Remove the existing 'Senec' integration from your 'Devices & Services' in the HA frontend - as explained in 4.) once you installed this integration (with the name 'senec') the previous existing Sensors will continue to record it's data

  3. [UPDATE 2023/12] Adding a this as custom repo is obsolete since the ha-senec-v3 repo have been added to HACS default as well - but you should remove the existing senec HACS integration and have to add the Senec.Home Integration (this one here) in HACS.

    Switch over to HACS and add the (yet) "none official" repo: https://github.com/marq24/ha-senec-v3
    image

  4. [UPDATE 2023/11] Obsolete, since the current release include all required features

    enable the Show beta versions switch for this repo to get the pre-release (if you want to use the additional WebAPI later)

  5. [UPDATE 2023/11] Obsolete, since the current release include all required features

    Select 3.0.5 (for just the https version) - or 3.0.6-test-xx from the list and press Download - (the files will be stored in the same directory as the original integration! /config/custom_components/senec)

  6. After the download is completed, restart your HA

  7. After the restart go to 'Devices & Services' again and press the + Add Integration button and start to type 'senec' - this should show you the SENEC.Home Integration - if it's said just 'senec' then something between the steps 1-5 went wrong!

  8. The first step of the setup is to specify your SENEC.Home System - please select SENEC.Home V3 hybrid/SENEC.Home V3 hybrid duo or SENEC.Home V2.1 or older depending on your hardware

  9. Now the the most important part when changing to this fork - select 'senec' (no matter of the case) as Display name
    image

  10. Enter the IP/hostname of your SENEC.Home in your LAN and press the submit button

You are done! - well almost...

There are more changes with the HTTPS update by Senec

With the update by Senec the STATISTICS data is no longer available - therefor please read Since SENEC Application v0825 no STATISTIC data is provided [No Data for multiple Sensors] and select one of the alternatives... After you have your alternative statistics you need/want to adjust your Energy Dashboard (don't remove the current configured Entities - even they are reported as missing - we never know, IF and WHEN they might come back!) - please read all details here: How to configure Energie Dashboards (after SENEC.Home have been updated to 0825+)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant