Git Product home page Git Product logo

iobroker.hass's Introduction

Logo

ioBroker.hass

Number of Installations Number of Installations NPM version

Test and Release Translation status Downloads

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.

This adapter allows the connecting of Home Assistant to ioBroker.

Usage

Create a long term token in HASS and use it as PW (copy it also in the repeat field).

Then it should read out all attributes for all devices. Services might be controllable (e.g. "turn_on"). To control services you have two options:

Set a direct value

Set the state with an ack=false value which is not a string (e.g. Boolean true) then it will be triggered also in HASS without additional service data. This will only work if the service has one field to be sent - then the value is sent as this field! If the service has more than one field you will find a warning in the log that provides more details about the fields taht are possible to be sent, e.g.

Please make sure to provide a stringified JSON as value to set relevant fields! Please refer to the Readme for details!
Allowed field keys are: temperature, target_temp_high, target_temp_low, hvac_mode

Set a stringified JSON to provide one or multiple fields

Set the state with an ack=false String value which is a stringified JSON object to call the service and use the JSON object as service data

For the last option on a light.turn_off with e.g. {"transition":10,"flash":"short"} these two service data details are sent with the call to HASS. The available fields with their exact data definition can be seen in the JSON definition of the ioBroker object in the native.fields section and would look like the following in the above example:

... native: { "fields": { "transition": { "name": "Transition", "description": "Duration it takes to get to next state.", "selector": { "number": { "min": 0, "max": 300, "unit_of_measurement": "seconds" } } }, "flash": { "name": "Flash", "description": "If the light should flash.", "advanced": true, "selector": { "select": { "options": [ "long", "short" ] } } } }, "entity_id": "light.mi_control_hub_light", "attr": "turn_off", "type": "light" } ...

For some services like set_speed it is required to call with a JSON object like {speed: "high"} in general to provide required values. In this case the field definition look e.g. like:

...
    native: {
        "fields": {
            "speed": {
                "name": "Speed",
                "description": "Speed setting.",
                "required": true,
                "example": "low",
                "selector": {
                    "text": null
                }
            }
        }
        ...
    }
...

Configuration

There is a good article about connection.

Please check it https://www.smarthomejetzt.de/mit-iobroker-auf-eine-home-assistant-hass-io-installation-und-die-geraete-zugreifen/

Unfortunately only in german, but the google translate works rather good

Changelog

1.4.0 (2023-01-03)

  • (Apollon77) Added more guidance logging when setting services incorrectly
  • (Apollon77) Prevent crashes when attributes contain "." at the end of their names
  • (Apollon77) Added logging for state updates for unknown objects

1.3.0 (2022-07-01)

  • (Apollon77) Further optimize sending data to HASS and allow to set values like numbers as normal states if the service has one attribute and it can be mapped

1.2.0 (2022-06-17)

  • (Apollon77) IMPORTANT: Replace special characters in entity attribute names with an underscore! Object IDs might change!
  • (Apollon77) make sure a "null" value in state changes is not crashing

1.1.2 (2022-03-29)

  • (Apollon77) Fix crash cases reported by Sentry

1.1.1 (2022-03-25)

  • (Apollon77) Show password fields masked again in config

1.1.0 (2022-03-24)

  • IMPORTANT: You need to re-enter the password once after installing this version!
  • (Apollon77) Implement Service triggers to use any value to trigger or stringified JSON to call with fields
  • (Apollon77) Optimize unload handling
  • (Apollon7) Add Sentry for crash reporting

1.0.1 (2021-09-04)

  • IMPORTANT: js-controller 2.0 is needed st least!
  • (Apollon77) Fix start issue
  • (Apollon77/Garfonso) Fix issue where value could not be set in hass

1.0.0 (2020-12-13)

  • (bluefox) added the support of compact mode

0.1.0

  • (bluefox) initial release

License

The MIT License (MIT)

Copyright (c) 2018-2023 bluefox [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.hass's People

Contributors

alexalex89 avatar apollon77 avatar dependabot[bot] avatar diemade avatar germanbluefox avatar lgtm-migrator avatar mcm1957 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

iobroker.hass's Issues

Release script: Action required

Hi, it looks like you are using @alcalzone/release-script to manage your releases.
When updating to the latest version, you need to remove the following line from your .github/workflows/test-and-release.yml if you want the releases to keep working:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/master' &&
      startsWith(github.ref, 'refs/tags/v')

It may also look like this one:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/main' &&
      startsWith(github.ref, 'refs/tags/v')

Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter hass for common errors and appropiate suggestions to keep this adapter up to date.

This check is based the current head revisions (master / main branch) of the adapter repository

Please see the result of the check below.

ioBroker.hass

Downloads Number of Installations (latest) Number of Installations (stable) - Test and Release

ERRORS:

  • ❗ [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
  • ❗ [E033] @iobroker/adapter-core 2.6.8 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
  • ❗ [E035] No devDependency declared for @iobroker/testing. Please add "@iobroker/testing":"4.1.3" to devDependencies at package.json
  • ❗ [E162] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.

WARNINGS:

  • 👀 [W172] "common.localLink" in io-package.json is deprecated. Please define object "common.localLinks": { "_default": "..." }
  • 👀 [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
  • 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
  • 👀 [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
  • 👀 [W853] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

  • 📌 [S519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
  • 📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.

Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.

You may start a new check at any time by adding the following comment to this issue:

@iobroker-bot recheck

Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

Last update at Fri, 06 Sep 2024 08:06:37 GMT

has no existing object, this might lead to an error in future versions

Hi

My log on IOBroker is full with warn messages likes this:

hass.0 2022-12-02 09:14:20.723 warn State "hass.0.entities.light.eg_eingang.color_mode" has no existing object, this might lead to an error in future versions
hass.0 2022-12-02 09:14:19.665 warn State "hass.0.entities.light.ug_kellerabgang.color_mode" has no existing object, this might lead to an error in future versions
hass.0 2022-12-02 08:48:56.424 warn State "hass.0.entities.light.ug_garage_velo.color_mode" has no existing object, this might lead to an error in future versions
hass.0 2022-12-02 08:48:40.987 warn State "hass.0.entities.light.ug_kellerabgang.color_mode" has no existing object, this might lead to an error in future versions
hass.0 2022-12-02 08:48:28.340 warn State "hass.0.entities.light.eg_hwr.color_mode" has no existing object, this might lead to an error in future versions
hass.0 2022-12-02 08:47:09.184 warn State "hass.0.entities.light.ug_kellerabgang.color_mode" has no existing object, this might lead to an error in future versions
hass.0 2022-12-02 08:46:44.610 warn State "hass.0.entities.light.eg_eingang.color_mode" has no existing object, this might lead to an error in future versions

All this entities coming from the KNX integration within Home Assistant.

I have the following versions in use
HA:
HA OS 9.3
HA Core 22.11.5
IOBroker:
v6.2.23
Node.js: v14.19.3
NPM: 6.14.17

Please help!

Thx!
Raphael

Please mark project as abandoned

With no updates for 8 months, and the adapter not working on the current version, it'd be nice of you to make people aware that it is abandoned, and they shouldn't waste their time with it.

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/ioBroker/ioBroker.hass

  • [E605] No actual year found in copyright. Please add "Copyright (c) 2018-2022 bluefox [email protected]" at the end of README.md
  • [E701] No actual year found in LICENSE. Please add "Copyright (c) 2018-2022 bluefox [email protected]" at the start of LICENSE

I have also found warnings that may be fixed if possible.

  • [W505] setTimeout found in "main.js", but no clearTimeout detected

Thanks,
your automatic adapter checker.

User ist missing

I have tried this adapter. There ist a Textfield for the password, but not for the username.
So the connect to Homeassistant fails.
(3432) Invalid answer: {"type": "auth_invalid", "message": "Invalid access token or password"}

Please add you adapter to our repository

We saw your adapter and if it is ready please request that it is added to the repository. With this it becomes available for all users. Please consult https://github.com/ioBroker/ioBroker.repositories#add-a-new-adapter-to-the-latest-repository and the following sections for more details.
If you need help, contact us in the forum https://forum.iobroker.net/ or in the developer chat https://github.com/iobroker-community-adapters/info .

Thank you for your support.

Can't set temperature for climate control

Hello!

I use HASS to control some climate devices. 3 "modded" Midea (remko) ACs with ESPHome and 2 Tuya thermostats.

I can control these devices from HASS without any problems. Setting the mode (heat/ cool/ auto) is working, setting a target temperature also.

From IOBroker I can set the mode (for example cool) or other values like "low fan". But one thing does not work on any of my climate devices: Setting the temperature.
I tried different types for set temperature (mixed, number, ...), nothing.

I always get an error when setting the temperature to for example 22°C: "Cannot control hass.0.entities.climate.heidenfeld.set_temperature: true"
I
I already reinstalled the adapter from GIT (before I uses 1.0.3 from the IOBroker source), no change.

What else do you need? I already read, that there was a similar issue - but installing the GIT version did not help for me.

I have attached the objectdata for "set temperature" in my IOBroker.

Many thanks in advance!

set_temperature.txt

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Add possibility to filter entities before syncing

Would'nt it be a good idea to not sync all of the entities from Home assistant to iobroker?
In the FHEM-Adapter there is a possibility to filter just what you need to be synced by adding "iobroker" as room name in FHEM. If doing so, just "objects"/devices which are in room iobroker get synced to iobroker an all the others are not synced but fully functional within FHEM (for automations and so on).
The only problem I see is, that you actually can't set such an attribute for each entity but only for whole devices in Home assistant. But even that would be better to sync only devices and their whole entities which belong to a room iobroker instead of just syncing all of them.
As a workaround I deactivated all the entities I don't need in Home assistant and iobroker, but others are needed in Home assistant but not in iobroker.

need current js version (v12 is in addon). Needed: v16

Hey guys,
I currently try to integrate gruenbeck water desalting equipment to ha. Therefore I have to install MQTTT Client in iobroker provided by iobroker.hass addon. MQTT client installation fails with errormessage: nodjs version v16 required v12 is installed.
Is it possible to uddate nodejs version inside of your container?

Thx and regards

Gerhard

Values write in hass

If I follow the instructions I can install the adapter and also configure it correctly. I get the data points displayed in objects. However, no writing of values is possible. In the log the following message appears when writing:

-Object of state "hass.0.entities.light.buro_decke_2.turn_on" is missing the required property "common.type".

-Cannot control hass.0.entities.light.buro_decke_2.turn_on: true

Is there anything else that needs to be adjusted?

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/ioBroker/ioBroker.hass

  • [E150] No common.connectionType found in io-package.json
  • [E152] No common.dataSource found in io-package.json
  • [E812] file test/ found in repository, but not found in .npmignore
  • [E814] file appveyor.yml found in repository, but not found in .npmignore
  • [E815] file .travis.yml found in repository, but not found in .npmignore

I have also found warnings that may be fixed if possible.

  • [W505] setTimeout found in "main.js", but no clearTimeout detected

Thanks,
your automatic adapter checker.

Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter hass for common errors and appropiate suggestions to keep this adapter up to date.

Please see the result of the check below.

ioBroker.hass

Downloads Number of Installations (latest) Number of Installations (stable) - Test and Release
NPM

ERRORS:

  • ❗ [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
  • ❗ [E033] @iobroker/adapter-core 2.6.8 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
  • ❗ [E035] No devDependency declared for @iobroker/testing. Please add "@iobroker/testing":"4.1.3" to devDependencies at package.json
  • ❗ [E162] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.

WARNINGS:

  • 👀 [W172] "common.localLink" in io-package.json is deprecated. Please define object "common.localLinks": { "_default": "..." }
  • 👀 [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
  • 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
  • 👀 [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
  • 👀 [W519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
  • 👀 [W522] Please consider migrating to admin 5 UI (jsonConfig).
  • 👀 [W853] .npmignore found - consider using package.json object "files" instead.

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.

Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

All Objects in read only state

Describe the bug
I have installed the "Kia Uvo / Hyundai Bluelink" Integration with HACS on Home Assistant.
But alle objects are in read only state.
I cannot switch the climate on and a cannot set the charging limit.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'hass.0.entities.binary_sensor.ev6_air_conditioner.state'
  2. Set it to on
  3. See error

Expected behavior
To write/set the state

Screenshots & Logfiles
image
image

`

2023-07-13 11:21:09.827 - warn: javascript.0 (4896) Read-only state "hass.0.entities.binary_sensor.ev6_air_conditioner.state" has been written without ack-flag with value "on"

2023-07-13 11:21:09.850 - warn: hass.0 (48436) Object hass.0.entities.binary_sensor.ev6_air_conditioner.state is not writable!

`

Versions:

  • Adapter version: v1.4.0
  • JS-Controller version: 4.0.24
  • Node version: v16.19.0
  • Operating system: Windows 10 Pro - 64bit

Unable to change the state of any entity

Describe the bug
All entities are marked as unwriteable and changing that setting just throws errors. Is this supposed to be able to update states or just read them?

Please check ioBroker.hass with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

Invalid access token or password

Hallo,
ich habe den Longlive Token in meiner Homeassist Installation erstellt:

image

Diesen habe ich dann unter Passwort zweimal eingefügt.
IP und Port stimmt auch in der Instanz:

image

Bekomme aber trotzdem diese Meldung im Log:

image

Was mache ich da falsch?

Не подключается к hass

Describe the bug
Не подключается
нет поля для ввода логина, только пароль
кнопки сохранить и сохранить и выйти не стандартного вида, случайно получилось нажать сохранить.

Screenshots & Logfiles

host.iobroker 2020-12-16 03:07:08.849 info Restart adapter system.adapter.hass.0 because enabled
host.iobroker 2020-12-16 03:07:08.849 error instance system.adapter.hass.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.iobroker 2020-12-16 03:07:08.848 error Caught by controller[0]: at internal/main/run_main_module.js:17:47
host.iobroker 2020-12-16 03:07:08.848 error Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
host.iobroker 2020-12-16 03:07:08.848 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:708:14)
host.iobroker 2020-12-16 03:07:08.848 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:863:32)
host.iobroker 2020-12-16 03:07:08.848 error Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
host.iobroker 2020-12-16 03:07:08.847 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:999:30)
host.iobroker 2020-12-16 03:07:08.847 error Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.hass/main.js:399:5)
host.iobroker 2020-12-16 03:07:08.847 error Caught by controller[0]: at startAdapter (/opt/iobroker/node_modules/iobroker.hass/main.js:18:56)
host.iobroker 2020-12-16 03:07:08.847 error Caught by controller[0]: ReferenceError: stop is not defined
host.iobroker 2020-12-16 03:07:08.846 error Caught by controller[0]: ^
host.iobroker 2020-12-16 03:07:08.846 error Caught by controller[0]: Object.assign(options, {name: adapterName, unload: stop});
host.iobroker 2020-12-16 03:07:08.846 error Caught by controller[0]: /opt/iobroker/node_modules/iobroker.hass/main.js:18
host.iobroker 2020-12-16 03:07:08.576 info instance system.adapter.hass.0 started with pid 17436

image

Versions:

  • Adapter version: 1.0.0
  • JS-Controller version: 3.1.6
  • Node version: 12.20.0
  • Operating system: docker 5.1.0
  • Home Assistant 2020.12.0
  • Версия Python | 3.8.6
    -- | --

Additional context
Add any other context about the problem here.

Warnings since update JS-Controller

Since last stable update of JS-Controller (3.3.15) I get a lots of warnings in iobroker log:

`
hass.0
2021-08-11 16:48:56.058 warn Object of state "hass.0.entities.sun.sun.state" is missing the required property "common.type"

hass.0
2021-08-11 16:44:56.057 warn Object of state "hass.0.entities.sun.sun.state" is missing the required property "common.type"

hass.0
2021-08-11 16:43:21.310 warn Object of state "hass.0.entities.device_tracker.xxxxx.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:56.056 warn Object of state "hass.0.entities.sun.sun.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:45.314 warn Object of state "hass.0.entities.person.yyyyy.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:45.277 warn Object of state "hass.0.entities.person.zzzzz.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:45.237 warn Object of state "hass.0.entities.person.aaaaa.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:45.232 info State value to set for "hass.0.entities.sensor.hacs.repositories" has to be one of type "string", "number", "boolean" but received type "object"

hass.0
2021-08-11 16:40:45.224 warn Object of state "hass.0.entities.sensor.hacs.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:45.174 warn Object of state "hass.0.entities.device_tracker.aaaaa_cz.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:45.136 warn Object of state "hass.0.entities.device_tracker.bbbbb.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:45.092 warn Object of state "hass.0.entities.device_tracker.zzzzz_zzzzz.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:45.007 warn Object of state "hass.0.entities.device_tracker.xxxxx.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:45.004 info State value to set for "hass.0.entities.weather.kkkkk.forecast" has to be one of type "string", "number", "boolean" but received type "object"

hass.0
2021-08-11 16:40:44.980 warn Object of state "hass.0.entities.weather.kkkkk.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:44.947 warn Object of state "hass.0.entities.zone.home.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:44.931 warn Object of state "hass.0.entities.binary_sensor.updater.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:44.901 warn Object of state "hass.0.entities.zone.nnnnn.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:44.859 warn Object of state "hass.0.entities.zone.zzzzz.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:44.829 warn Object of state "hass.0.entities.zone.sssss.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:44.778 warn Object of state "hass.0.entities.sun.sun.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:44.735 warn Object of state "hass.0.entities.person.eeeee.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:44.686 warn Object of state "hass.0.entities.person.jurgen.state" is missing the required property "common.type"

hass.0
2021-08-11 16:40:44.130 info starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.hass, node: v12.22.4, js-controller: 3.3.15`

Solution for me is now to set log level to 'error' but I think this could and should be fixed.

Greetings, Jürgen

BUG: set number value not possible

It's not possible to set a number value.
When I enter a number in the object list at hass.0.entities.number.device.set_value it won't work.
Neither home assistant changes the value nor the value is set in IOBroker.
Also the entered number is displayed red.

I use the number entities with ESPHome on HA.

It work on previous versions of Home Assistant before. With an update of ha it stopped working.
Could be 2-4 month or so . Unfortunately I can't tell exactly which version worked.

Screenshots & Logfiles
Log of IOBroker: Cannot control hass.0.entities.number.mg_eingang_people_counter.set_value: true

Versions:

  • Adapter version: 1.2.0 (updated) & 1.1.2 (tested before)
  • JS-Controller version: 4.0.23
  • Node version: v14.19.3
  • npm: 6.14.17
  • Operating system: ubuntu 20.4 LXC Container

Thanks for your support

Rainbird Integration throws an error

Describe the bug
Since there is no working adapter for the Rainbird irrigation system and there is an integration in Home Assistant avaliable, I'm using the hass adapter to get my Rainbird irrigation system to work in IOBroker. The irrigation system works, but I get an error like:

Bildschirmfoto vom 2023-06-13 20-56-05

The Readme has a chapter about the stringified JSON, but the "Allowed field keys" are empty in the log. So I am not able to create a correct stringified JSON value.

To Reproduce
Steps to reproduce the behavior:
I'm using a blockly script for starting and stopping the irrigation of a specific zone.

  • To start the irrigation I set the "turn_on" object to "1" and than back to " " after the irrigation started:
    Bildschirmfoto vom 2023-06-13 21-10-03
    Bildschirmfoto vom 2023-06-13 21-10-30
  • To stop the irrigation the same with the "turn_off" object.

I am aware, that the JSON value is incorrect, but the error doesn't tell me the correct field key!

Expected behavior
Two options:

  1. The error yields the correct field key.
  2. Since the toogle object represents the switch behaviour in Home Assistant, it would be nice, if we had an button object. That would reduce the complexity of the script.

Screenshots & Logfiles
2023-06-13 20:34:27.323 - error: hass.0 (15684) Cannot control hass.0.entities.switch.rain_bird_sprinkler_4.turn_on: true
2023-06-13 20:34:27.334 - warn: hass.0 (15684) Please make sure to provide a stringified JSON as value to set relevant fields! Please refer to the Readme for details!
2023-06-13 20:34:27.334 - warn: hass.0 (15684) Allowed field keys are:

Versions:

  • Adapter version: v1.4.0
  • JS-Controller version: 4.0.24
  • Node version: v18.16.0
  • Operating system: Ubuntu server 22.04.2 LTS

support for self signed certificates

Is your feature request related to a problem? Please describe.
My homeassistant is using a self signed certificate, right now, I cannot connect to it as I get

2023-08-30 06:36:15.460  - error: hass.0 (35370) Error: self-signed certificate

Describe the solution you'd like
It would be great to have another checkbox to be able to ignore certificate errors
This should be quite easy to do via

const client = new WebSocket();
client.connect(WSSrvUrl, null, null, null, {rejectUnauthorized: false});

see https://stackoverflow.com/a/68750487

Describe alternatives you've considered
Otherwise I would need to setup HA to serve both http and https which is quite a hassle.

Error: connect EHOSTUNREACH

Describe the bug
HA is installed in a docker container, in host mode. Iobroker is also in a container, but in a VLAN. I created a token, I'm trying to connect - I get an error Error: connect EHOSTUNREACH 192.168.88.18:8123

Versions:

  • Adapter version: 1.0.1
  • JS-Controller version: 3.3.18
  • Node version: v12.22.5
  • Operating system: doicker

Since v1.1.0 password is in clear text

Describe the bug
Since updating this adapter to v1.1.0 today, the password in the admin UI is always shows as clear text. Other adapters display this as **** as this should not be clearly visible.

image

  • Adapter Version 1.1.0
  • js-controller 4.0.21
  • Host OS Ubuntu

seit Version 1.0.0 startet der Adapter nicht mehr

bekomme ihn nicht gestartet.
erste Version 0.1.0 hat funktioniert.
Hoffe man kann damit was anfangen.
wenn ich Adapter starte unter debug bringt er das gleiche, also keine mehr infos.

System ist: Unraid 6.9RC1 mit docker Image von buanet.

Plattform: linux
Betriebssystem: linux
Die Architektur: x64
CPUs: 8
Geschwindigkeit: 3653 MHz
Modell: Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz
RAM: 7.6 GB
System-Betriebszeit: 2 T. 20:11:02
Node.js: v12.20.0
NPM: 6.14.8
Datenträgergröße: 20.0 GiB
Datenträger verfügbar: 11.9 GiB
Adapter-Anzahl: 382
Betriebszeit: 00:22:41
Aktive Instanzen: 11
js-controller 3.16

und

Home Assistent im docker unter Unraid

Version 2020.12.0
Installation Type Home Assistant Container
Development false
Supervisor false
Docker true
Virtual Environment false
Python Version 3.8.6
Operating System Family Linux
Operating System Version 5.9.13-Unraid
CPU Architecture x86_64
Timezone Europe/Berlin
host.8abf9d670426 2020-12-14 16:43:08.848 error instance system.adapter.hass.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.8abf9d670426 2020-12-14 16:43:08.848 error Caught by controller[0]: at internal/main/run_main_module.js:17:47
host.8abf9d670426 2020-12-14 16:43:08.848 error Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:708:14)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:863:32)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:999:30)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.hass/main.js:399:5)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at startAdapter (/opt/iobroker/node_modules/iobroker.hass/main.js:18:56)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: ReferenceError: stop is not defined
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: ^
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: Object.assign(options, {name: adapterName, unload: stop});
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: /opt/iobroker/node_modules/iobroker.hass/main.js:18
host.8abf9d670426 2020-12-14 16:43:08.628 info instance system.adapter.hass.0 started with pid 491

Error: Unexpected server response: 403 with Home Assistant Core 2024.7

Hallo Zusammen,

der Adapter funktioniert mit Home Assistant Core 2024.7 nicht mehr. Im ioBroker Log erscheint nach dem Update folgende Fehlermeldung: "Error: Unexpected server response: 403"

Ich habe es bereits mit einem neu angelegten Langzeit-Token ausprobiert aber das hat leider nicht geholfen.

Ich nutze HA OS 12.4 und habe lediglich das updaten des Cores auf 2024.7 durchgeführt. Davor ging alles, danach nicht mehr.

Compatibility check and testing for Node.js 14 and 16

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Read only?

I try to send some states from ioBroker to Homeassistant. They won‘t change. Is it possible that this adapter is only to read states?

Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter hass for common errors and appropiate suggestions to keep this adapter up to date.

This check is based the current head revisions (master / main branch) of the adapter repository

Please see the result of the check below.

ioBroker.hass

Downloads Number of Installations (latest) Number of Installations (stable) - Test and Release

ERRORS:

  • ❗ [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommended
  • ❗ [E033] @iobroker/adapter-core 2.6.8 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
  • ❗ [E035] No devDependency declared for @iobroker/testing. Please add "@iobroker/testing":"4.1.3" to devDependencies at package.json
  • ❗ [E157] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.

WARNINGS:

  • 👀 [W172] "common.localLink" in io-package.json is deprecated. Please define object "common.localLinks": { "_default": "..." }
  • 👀 [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
  • 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
  • 👀 [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
  • 👀 [W953] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

  • 📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).
  • 📌 [S526] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.

Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.

You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:

@iobroker-bot recheck
@iobroker-bot recreate

Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

Last update at Fri, 13 Sep 2024 11:01:34 GMT based on commit 7bf04e4
ioBroker.repochecker 3.0.5

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.