Giter VIP home page Giter VIP logo

iobroker.hydrawise's Introduction

Logo

ioBroker.hydrawise

NPM version Downloads node-lts Libraries.io dependency status for latest release

GitHub GitHub repo size GitHub commit activity GitHub last commit GitHub issues GitHub Workflow Status

Versions

Beta Stable Installed

Integrate your Hydrawise controller into iobroker. You can see all controller information, schedules and sensors. It is also possible to suspend planned watering by x seconds.

Documentation

Note
After updating from 0.0.15 you have to re-enter your API key

Changelog

0.3.3 (2024-04-22)

  • (SentiQ) updated dependencies

0.3.2 (2024-04-19)

  • (SentiQ) added default value to parameter apiInterval
  • (SentiQ) added translations

0.3.1 (2024-04-18)

  • (SentiQ) removed parameter apiKey in method call

0.3.0 (2024-04-18)

  • (SentiQ) added api interval to settings
  • (SentiQ) changed interval of schedule endpoint from 5 minutes to 1 minute

0.2.8 (2024-04-08)

  • (SentiQ) fixed tier and license

0.2.7 (2024-04-08)

  • (SentiQ) fixed type of runDefault object

0.2.6 (2024-04-08)

  • (SentiQ) fixed type of runDefault

0.2.5 (2024-04-07)

  • (SentiQ) NodeJS >= 18.x and js-controller >= 5 is required

0.2.4 (2024-02-01)

  • (SentiQ) updated dependencies

0.2.3 (2023-10-28)

  • (SentiQ) NodeJS 16.x is required
  • (SentiQ) updated dependencies

0.2.2 (2023-09-22)

  • (SentiQ) fixed versions

0.2.0 (2023-09-22)

  • (SentiQ) added button to run zone for default runtime

0.1.2 (2023-08-22)

  • (SentiQ) added link to api docu

0.1.1 (2023-08-22)

  • (SentiQ) fixed random crash, when api domain can't be resolved by dns
  • (SentiQ) added time string of last api call

0.0.19 (2023-08-05)

  • (SentiQ) fixed button roles

0.0.18 (2023-08-05)

  • (SentiQ) fixed timeout

0.0.17 (2023-08-03)

  • (SentiQ) fixed adapter crash

0.0.16 (2023-08-02)

  • (SentiQ) added more information to README
  • (SentiQ) encrypted apiKey
  • (SentiQ) removed logging of apiKey
  • (SentiQ) added filtering of invalid characters in ids
  • (SentiQ) added check of ack flag
  • (SentiQ) fixed roles
  • (SentiQ) fixed error message
  • (SentiQ) removed usage of clearTimeout

0.0.15 (2023-06-29)

  • (SentiQ) updated dependencies

0.0.14 (2023-06-29)

  • (SentiQ) fixing version

0.0.12 (2023-06-29)

  • (SentiQ) changed value of last_contact to date string format

0.0.11 (2023-06-28)

  • (SentiQ) raised timeouts
  • (SentiQ) fixed types

0.0.10 (2023-06-27)

  • (SentiQ) fixed adapter crash
  • (SentiQ) changed value of timestr to date string format

0.0.9 (2023-05-25)

  • (SentiQ) added more translations

0.0.8 (2023-05-25)

  • (SentiQ) improved log messages

0.0.7 (2023-05-25)

  • (SentiQ) fixed author

0.0.6 (2023-05-24)

  • (SentiQ) lowered min node version to 14.5.0

0.0.5 (2023-05-24)

  • (SentiQ) updated packages

0.0.4 (2023-05-24)

  • (SentiQ) testing

0.0.3 (2023-05-24)

  • (SentiQ) added zone controls and Ukrainian language

0.0.2 (2023-05-23)

  • (SentiQ) refactoring code

0.0.1 (2023-01-26)

  • (aDabbelju) Initial commit by adapter creator

License

MIT License

Copyright (c) 2024 SentiQ [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.hydrawise's People

Contributors

adabbelju avatar dependabot[bot] avatar sentiq avatar

Stargazers

avatar avatar avatar avatar avatar

Watchers

avatar

Forkers

iobroker-archive

iobroker.hydrawise's Issues

Update stable version in repo from 0.0.0 to 0.2.2

Think about adding version 0.2.2 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=0.2.2 (30 days old)
Installs: stable=0 (0%), latest=22 (39.29%), total=56

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

Update stable version in repo from 0.0.0 to 0.1.2

Think about adding version 0.1.2 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=0.1.2 (30 days old)
Installs: stable=0 (0%), latest=20 (40.82%), total=49

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

Enhancement - Datenpunkt für das Starten eines Kreises mit der Default-Laufzeit

Erst einmal Danke für deine Mühe und Zeit.
Einen Vorschlag zur Verbesserung hätte ich jedoch, da die API dahingehend etwas starr ist. Letztendlich besitzt jede Zone eine konfigurierte Zeit (Datenpunkt "run" in s) für die Sprengung eines Kreises. Wenn ich jedoch einen Kreis mit der bereits konfigurierten Zeit starten möchte, muss man sich ein Script/Blockly basteln. Dies liest die Zeit ("run") in Sekunden aus und setzt diese in den Datenpunkt "runZone". Hier wünschte ich mir eine elegantere Lösung, beispielsweise einen extra Datenpunkt (Switch), der den Kreis direkt starten und stoppen kann.

switch to "true" -> starte Kreis mit X Sekunden (X=Wert aus "run") -> danach Wechsel auf false
switch to "false" -> stoppe den Kreis

Damit ließe sich der Adapter direkt in eine Visualisierung einbinden. Hoffentlich ist mein Vorschlag verständlich 🙂

Grüße

Dummy question

sorry ... ich stelle mich möglicherweise nicht besonders schlau an ... aber ich wollte den hydrawise adapter in Iobroker einbinden und habe ihn mittels nmp -i .... installiert. Ich sehen aber keinen hydrawise adapter in der Iobroker oberfläche. Ich habe sicher einen "Denkfehler" oder ? Danke schon mal

Adapter stürzt ab - Mehrere Fehler im Log

hydrawise.0 2023-09-03 12:39:21.516 info starting. Version 0.1.2 in /opt/iobroker/node_modules/iobroker.hydrawise, node: v18.17.1, js-controller: 5.0.12
host.raspberrypi 2023-09-03 12:39:18.751 info instance system.adapter.hydrawise.0 started with pid 16738
host.raspberrypi 2023-09-03 12:38:48.494 info Restart adapter system.adapter.hydrawise.0 because enabled
host.raspberrypi 2023-09-03 12:38:48.493 error instance system.adapter.hydrawise.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
hydrawise.0 2023-09-03 12:38:48.369 error DB closed
hydrawise.0 2023-09-03 12:38:48.369 error Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at ObjectsInRedisClient._getObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:2416:37) at Immediate. (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:2463:33) at process.processImmediate (node:internal/timers:478:21)
hydrawise.0 2023-09-03 12:38:48.367 error unhandled promise rejection: DB closed
hydrawise.0 2023-09-03 12:38:48.367 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
hydrawise.0 2023-09-03 12:38:48.363 error Connection is closed.
hydrawise.0 2023-09-03 12:38:48.362 error Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at TCP. (node:net:323:12)
hydrawise.0 2023-09-03 12:38:48.361 error unhandled promise rejection: Connection is closed.
hydrawise.0 2023-09-03 12:38:48.361 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
hydrawise.0 2023-09-03 12:38:48.349 info terminating
hydrawise.0 2023-09-03 12:38:48.333 info State value to set for "hydrawise.0.customer.51" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.322 info State value to set for "hydrawise.0.customer.50" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.318 info State value to set for "hydrawise.0.customer.49" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.300 info State value to set for "hydrawise.0.customer.48" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.284 info State value to set for "hydrawise.0.customer.47" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.236 info State value to set for "hydrawise.0.customer.46" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.226 info State value to set for "hydrawise.0.customer.45" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.218 info State value to set for "hydrawise.0.customer.44" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.161 info State value to set for "hydrawise.0.customer.43" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.147 info State value to set for "hydrawise.0.customer.42" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.092 info State value to set for "hydrawise.0.customer.41" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.082 info State value to set for "hydrawise.0.customer.40" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.072 info State value to set for "hydrawise.0.customer.39" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.063 info State value to set for "hydrawise.0.customer.38" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.053 info State value to set for "hydrawise.0.customer.37" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:48.044 info State value to set for "hydrawise.0.customer.36" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.997 info State value to set for "hydrawise.0.customer.35" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.988 info State value to set for "hydrawise.0.customer.34" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.979 info State value to set for "hydrawise.0.customer.33" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.969 info State value to set for "hydrawise.0.customer.32" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.959 info State value to set for "hydrawise.0.customer.31" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.949 info State value to set for "hydrawise.0.customer.30" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.938 info State value to set for "hydrawise.0.customer.29" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.928 info State value to set for "hydrawise.0.customer.28" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.918 info State value to set for "hydrawise.0.customer.27" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.863 info State value to set for "hydrawise.0.schedule.57" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.851 info State value to set for "hydrawise.0.customer.26" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.847 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
hydrawise.0 2023-09-03 12:38:47.846 info terminating
hydrawise.0 2023-09-03 12:38:47.839 error content.relays is not iterable
hydrawise.0 2023-09-03 12:38:47.839 error TypeError: content.relays is not iterable at /opt/iobroker/node_modules/iobroker.hydrawise/build/main.js:161:39
hydrawise.0 2023-09-03 12:38:47.837 error unhandled promise rejection: content.relays is not iterable
hydrawise.0 2023-09-03 12:38:47.836 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
hydrawise.0 2023-09-03 12:38:47.828 info State value to set for "hydrawise.0.schedule.56" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.817 info State value to set for "hydrawise.0.customer.25" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.805 info State value to set for "hydrawise.0.schedule.55" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.797 info State value to set for "hydrawise.0.customer.24" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.743 info State value to set for "hydrawise.0.schedule.54" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.727 info State value to set for "hydrawise.0.customer.23" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.725 info State value to set for "hydrawise.0.schedule.53" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.712 info State value to set for "hydrawise.0.customer.22" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.698 info State value to set for "hydrawise.0.schedule.52" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.640 info State value to set for "hydrawise.0.customer.21" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.637 info State value to set for "hydrawise.0.schedule.51" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.625 info State value to set for "hydrawise.0.customer.20" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.617 info State value to set for "hydrawise.0.schedule.50" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.603 info State value to set for "hydrawise.0.customer.19" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.602 info State value to set for "hydrawise.0.schedule.49" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.588 info State value to set for "hydrawise.0.customer.18" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.581 info State value to set for "hydrawise.0.schedule.48" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.523 info State value to set for "hydrawise.0.customer.17" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.520 info State value to set for "hydrawise.0.schedule.47" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.515 info State value to set for "hydrawise.0.customer.16" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.511 info State value to set for "hydrawise.0.schedule.46" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.494 info State value to set for "hydrawise.0.customer.15" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.487 info State value to set for "hydrawise.0.schedule.45" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.434 info State value to set for "hydrawise.0.customer.14" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.423 info State value to set for "hydrawise.0.schedule.44" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.419 info State value to set for "hydrawise.0.customer.13" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.402 info State value to set for "hydrawise.0.schedule.43" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.393 info State value to set for "hydrawise.0.customer.12" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.381 info State value to set for "hydrawise.0.schedule.42" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.379 info State value to set for "hydrawise.0.customer.11" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.362 info State value to set for "hydrawise.0.schedule.41" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.350 info State value to set for "hydrawise.0.customer.10" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.349 info State value to set for "hydrawise.0.schedule.40" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.336 info State value to set for "hydrawise.0.customer.9" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.327 info State value to set for "hydrawise.0.schedule.39" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.318 info State value to set for "hydrawise.0.customer.8" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.276 info State value to set for "hydrawise.0.schedule.38" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.275 info State value to set for "hydrawise.0.customer.7" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.270 info State value to set for "hydrawise.0.schedule.37" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.250 info State value to set for "hydrawise.0.customer.6" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.241 info State value to set for "hydrawise.0.schedule.36" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.230 info State value to set for "hydrawise.0.customer.5" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.226 info State value to set for "hydrawise.0.schedule.35" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.178 info State value to set for "hydrawise.0.customer.4" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.106 info State value to set for "hydrawise.0.schedule.34" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.094 info State value to set for "hydrawise.0.customer.3" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.092 info State value to set for "hydrawise.0.schedule.33" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.079 info State value to set for "hydrawise.0.customer.2" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.072 info State value to set for "hydrawise.0.schedule.32" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.063 info State value to set for "hydrawise.0.customer.1" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.053 info State value to set for "hydrawise.0.schedule.31" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.044 info State value to set for "hydrawise.0.customer.0" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:47.029 info State value to set for "hydrawise.0.schedule.30" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.944 info State value to set for "hydrawise.0.schedule.29" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.934 info State value to set for "hydrawise.0.schedule.28" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.923 info State value to set for "hydrawise.0.schedule.27" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.911 info State value to set for "hydrawise.0.schedule.26" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.848 info State value to set for "hydrawise.0.schedule.25" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.815 info State value to set for "hydrawise.0.schedule.24" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.801 info State value to set for "hydrawise.0.schedule.23" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.754 info State value to set for "hydrawise.0.schedule.22" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.744 info State value to set for "hydrawise.0.schedule.21" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.731 info State value to set for "hydrawise.0.schedule.20" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.720 info State value to set for "hydrawise.0.schedule.19" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.665 info State value to set for "hydrawise.0.schedule.18" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.650 info State value to set for "hydrawise.0.schedule.17" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.639 info State value to set for "hydrawise.0.schedule.16" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.585 info State value to set for "hydrawise.0.schedule.15" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.575 info State value to set for "hydrawise.0.schedule.14" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.566 info State value to set for "hydrawise.0.schedule.13" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.550 info State value to set for "hydrawise.0.schedule.12" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.535 info State value to set for "hydrawise.0.schedule.11" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.487 info State value to set for "hydrawise.0.schedule.10" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.478 info State value to set for "hydrawise.0.schedule.9" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.466 info State value to set for "hydrawise.0.schedule.8" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.456 info State value to set for "hydrawise.0.schedule.7" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.447 info State value to set for "hydrawise.0.schedule.6" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.435 info State value to set for "hydrawise.0.schedule.5" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.386 info State value to set for "hydrawise.0.schedule.4" has to be type "number" but received type "string"
hydrawise.0 2023-09-03 12:38:46.370 warn Object of state "hydrawise.0.schedule.3" is missing the required property "common.type"
hydrawise.0 2023-09-03 12:38:46.354 warn Object of state "hydrawise.0.schedule.2" is missing the required property "common.type"
hydrawise.0 2023-09-03 12:38:46.349 warn Object of state "hydrawise.0.schedule.1" is missing the required property "common.type"
hydrawise.0 2023-09-03 12:38:46.308 info State value to set for "hydrawise.0.schedule.0" has to be type "number" but received type "string"

Update stable version in repo from 0.0.0 to 0.2.3

Think about adding version 0.2.3 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=0.2.3 (30 days old)
Installs: stable=0 (0%), latest=18 (30%), total=60

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

No bug - just a question

Hallo Yves,

Danke für die Bereitstellung des Adapters! Ich habe nur eine kurze Frage - in welchen Zeitabständen werden die Daten gezogen? Ich habe irgendwo eine 60 gefunden - sind das Sekunden?
Ich hatte bisher die API direkt per http abgefragt und das in Abständen von 60 Sekunden. Hab darüber berechnet, wann die Brunnenpumpe angeworfen werden muss. Ich würde natürlich gern auf deinen Adapter umsteigen und muss dann nur schauen, wie die Parameter zusammen passen.

Danke schon mal vorab für die Info!

Update stable version in repo from 0.0.0 to 0.2.4

Think about adding version 0.2.4 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=0.2.4 (30 days old)
Installs: stable=0 (0%), latest=18 (27.69%), total=65

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!
Do not close this issue manually as a new issue will be created if condition for update still exists
@mcm1957 for evidence

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.