Is your feature request related to a problem? Please describe.
currently ssl connections to integrations are only working with official certificates issued by a known CA

Describe the solution you'd like
Either i am able to get my own CA into the truststore or get an option to disable ssl verification.

Additional context
currently failing due to this error:

May 15 10:47:47 YIO-Remote-b827eb79b4c6 app-launch.sh[124]: WARN  homeassistant QAbstractSocket::SocketError(13) "The issuer certificate of a locally looked up certificate could not be found"

Is your feature request related to a problem? Please describe.

My living room has about 20 hue lights, way too many to control individually. So I use scenes in HA to control them. Currently the HA YIO plugin does not support HA scenes.

Describe the solution you'd like

It would be very nice to have HA Scene support.

Describe alternatives you've considered

Additional context

ACTUAL:
when connection gets lost a notification is displayed on the remote top header saying " lost connection"

Solution:
When Remote gets back connection, remove this notification again. Only display it as long as there is no connection.

Same task as YIO-Remote/remote-software#349

Expected Behavior or Design

The YIO Remote software is licensed under GPL v3 or later (see license information in each GitHub repository). This should not just be reflected in the LICENSE.md file but also in every source file.

Current Behavior or Design

Almost no source file has a license information.

Possible Solution

Add the same file header to each and every source file.
The new wifi control source files in feature/322-WiFi_rewrite branch have a file header defined. I suggest using this header as a template. See below in detailed description.

Detailed Description and Additional Information

• How to use GNU licenses for your own software (GNU docs)
• Using the SPDX License List for Tagging and Linking

Suggested license template for new files

I.e. entirely written by one author:

/******************************************************************************
 *
 * Copyright (C) <YEAR(S)> <AUTHOR> <EMAIL>
 *
 * This file is part of the YIO-Remote software project.
 *
 * YIO-Remote software is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 *
 * YIO-Remote software is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 *
 * You should have received a copy of the GNU General Public License
 * along with YIO-Remote software. If not, see <https://www.gnu.org/licenses/>.
 *
 * SPDX-License-Identifier: GPL-3.0-or-later
 *****************************************************************************/

Suggested license template for derived files

I.e. using code from other GPL v3 compatible sources:

/******************************************************************************
 *
 * Copyright (C) <YEAR(S)> <AUTHOR> <EMAIL>
 *
 * Third party work used:
 *
 * <PROJECT_DESCRIPTION>
 * Copyright (C) <YEAR(S)> <ORIGINAL_AUTHOR> <ORIGINAL_EMAIL>
 * Licensed under <LICENSE>.
 *
 *
 * This file is part of the YIO-Remote software project.
 *
 * YIO-Remote software is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 *
 * YIO-Remote software is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 *
 * You should have received a copy of the GNU General Public License
 * along with YIO-Remote software. If not, see <https://www.gnu.org/licenses/>.
 *
 * SPDX-License-Identifier: GPL-3.0-or-later
 *****************************************************************************/

Example wifi_wpasupplicant.h

/******************************************************************************
 *
 * Copyright (C) 2019 Markus Zehnder <[email protected]>
 *
 * Third party work used:
 *
 * DigitalRooster - QT/QML internet radio, podcast player and alarmclock.
 * Copyright (C) 2018 Thomas Ruschival <[email protected]>
 * Licensed under GPL 3.0 or later.
 *
 * wpaCute - A graphical wpa_supplicant front end.
 * Copyright (C) 2018 [email protected]
 * Licensed under BSD license.
 *
 *
 * This file is part of the YIO-Remote software project.
 *
 * YIO-Remote software is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 *
 * YIO-Remote software is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 *
 * You should have received a copy of the GNU General Public License
 * along with YIO-Remote software. If not, see <https://www.gnu.org/licenses/>.
 *
 * SPDX-License-Identifier: GPL-3.0-or-later
 *****************************************************************************/

Would love to see the fan entity in home assistant supported so I can operate my ceiling fans.

thanks

Description

When SSL is setup on HA, the integration cannot connect to the HA instance.

Expected behavior

The integration should be able to connect when SSL is used in HA.

• Version used: v0.3.0
• Running on:
  • YIO Remote* Operating System and version if not running on YIO Remote:

Additional context

Add a boolean data key that indicates if SSL is used on the HA instance. Based on that repalce ws with wss.

Description

When I open the web-configurator and want to add a new integration the setup dialog doesn't show for Home Assistant. This prevents me to setup the integration on the latest versions.

How to Reproduce

Steps to reproduce the behavior:

1. Go to the web configurator integrations page.
2. Click on "Add Integration".
3. Select homeasssistant from the list.
4. Nothing is rendered.

Expected behavior

I would expect the form with IP, Token etc. to show up.

Your Environment

• Version used: 0.4.2
• Running on:
  • YIO Remote
• Web Configurator: tested on 0.1.4 and 0.1.1

Additional context

The relevant error in the logs seems to appear when the examples of one of the ssl booleans are rendered. undefined refers to the examples property:

TypeError: Cannot read property '0' of undefined

Downgrading to v0.4.1 fixes the issue.

I control a lot with NodeRed and depending on other events, so i have created several dummy switches, but these are input_boolean switches, would it be possible to include them as entities?
In theory they should work similar to a normal switch
#FeatureRequest

Description

Climate integration shows 0° when opening the card.

How to Reproduce

Steps to reproduce the behavior:

1. Add climate from home-assistant
2. The preview on the page shows the correct current temperature
3. Open the card. The current temperature is 0°. When I change the temperature, to eg 1°, then in HA, the temperature is also 1°.

Expected behavior

Have the correct current temperature

Your Environment

• Version used: 0.5.7
• Running on:
  • YIO Remote
• Operating System and version if not running on YIO Remote: