GithubHelp home page GithubHelp logo

iobroker / iobroker.lovelace Goto Github PK

View Code? Open in Web Editor NEW
58.0 11.0 27.0 396.68 MB

Visualization with Lovelace-UI

License: Apache License 2.0

HTML 7.32% CSS 1.60% JavaScript 90.99% Batchfile 0.03% Shell 0.06%
iobroker home-assistant visualization lovelace-ui lovelace-card

iobroker.lovelace's People

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 avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar 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 avatar avatar avatar avatar

Forkers

smarthomefans scrounger asgothian ldittmar81 acidburn78 garfonso tw1nh34d algar42 marouanboulhir chah90 thost96 pstalljohann petervoronov xap-automation 5g7k elredef lgtm-migrator agross diemade julianschnell pafade89 smarthomejoey iobroker-archive lizardking mcm1957

iobroker.lovelace's Issues

RGB Beleuchtung hinzufügen bzw. möglich ?

Hallo,

ist es schon möglich RGB Lampen in Lovelace zu Steuern?
Ich habe es mit der Light Entity Card versucht, aber es gibt keine möglichkeit ein Color state zu bestimmen.
Wenn nicht, kommt es in nächster Zeit dazu ?

LG Marcus

Duplicate Entities for one iob state

I setup entity id manully for each state.
First time, I do not setup entityID manully, just leave those empty.

Then I got one state entity named switch.command
But I found this name is not unique, so I set entity name manully to switch.TC1_plug0
After that, I got two entity name for one state

image

Can't connect from Ariela app

I try to connect through the app for Android Ariela, all the stages of configuration are good, but when you need to download objects-an error occurs. Here is part of the Ariela program log:

01-08 19:43:37.046 29634 30227 D HA_HAConnectionTester: HAConnectionTester: final URL = http://192.168.1.100:8123/api/
01-08 19:43:37.075 29634 30228 D HA_HAConnectionTester: onResponse: called
01-08 19:43:37.077 29634 30228 E HA_HAConnectionTester: HAServerConnectionTester: JSON exception = org.json.JSONException: Value <!DOCTYPE of type java.lang.String cannot be converted to JSONObject
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: onResponse: message = <!DOCTYPE html>
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: <html lang="en">
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: <head>
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: <meta charset="utf-8">
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: <title>Error</title>
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: </head>
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: <body>
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: <pre>Cannot GET /api/</pre>
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: </body>
01-08 19:43:37.077 29634 30228 D HA_HAConnectionTester: </html>

http://192.168.1.100:8123/api/ - I think the problem is this address. it doesn't exist
JS-Controller - 2.7.7
Lovelace adapter 1.0.6 (from github) should be 1.0.7 I think

Zu wenig Datenpunkte

Hallo,
Bei mir wird nur das angezeigt, wie und wo holt er sich die Datenpunkte? Ich habe nur 4 DP?

Screenshot (3314)

Was ist eigentlich Entität?

lovelace.log

horizontal-stack: state wird nicht erkannt

Ich habe zwei Lichter in einem horizontalen stack. Der Status wird nicht erkannt.
hor-stack-not-working

Wenn ich jetzt die gleichen entity jetzt einzeln hinzfüge, funktionieren auch die Buttons in dem horizontal-stack.
hor-stack-working

hor-stack-working_2

Das gleiche verhalten tritt auch bei einem vertical-stack auf

"Reload of entities" nach Ändern eines DP Typs

Nach dem Ändern eines Datenpunkt Typs in der Objektstuktur, muss die Liste der Entities neu eingelesen werden.
Auch taucht die neue "Entity" erst nach dem "Reload" des GUI-Editors in den Listen dort auf.

Im Log Fehlermeldungen

Hallo zusammen,

ich bekomme immer im Log folgende Fehlermeldung
Cannot find view "custom" for search "state" : null

Diese erscheint ca. jede Minute

After I upload a custom card. ioBroker crashed.

I update a custom card by drop a js on web page.
Then admin start abnormal

issue logs shows

host.dockerhub-cn Cannot get view: ReplyError: ERR Error running script (call to f_47ca5e051ba19850d94c45a1fc8725ff04ae868f): @user_script:12: user_script:12: Expected value but found T_END at character 1

Then I restart ioBroker system. All adapters can not work

I delete lovelace adapter by commad line. This issue still can not fix.

I run iob list instances
An issue log shows

Cannot parse JSON cfg.o.system.adapter.lovelace.0:

every few minutes restart the Adapter new

Adapter startet alle Paar Minuten neu.
every few minutes restart the Adapter new

Log:

lovelace.0 2019-08-04 21:38:40.791 info http server listening on port 8091
lovelace.0 2019-08-04 21:38:40.695 info starting. Version 0.1.3 in /opt/iobroker/node_modules/iobroker.lovelace, node: v10.16.1
lovelace.0 2019-08-04 21:38:06.193 info cleaned everything up...
lovelace.0 2019-08-04 21:38:05.184 info cleaned everything up...
lovelace.0 2019-08-04 21:38:05.181 error at Timer.processTimers (timers.js:223:10)
lovelace.0 2019-08-04 21:38:05.181 error at listOnTimeout (timers.js:263:5)
lovelace.0 2019-08-04 21:38:05.181 error at tryOnTimeout (timers.js:300:5)
lovelace.0 2019-08-04 21:38:05.181 error at ontimeout (timers.js:436:11)
lovelace.0 2019-08-04 21:38:05.181 error at Timeout._updateTimer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:3146:22)
lovelace.0 2019-08-04 21:38:05.181 error at WebServer.onStateChange (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1646:22)
lovelace.0 2019-08-04 21:38:05.181 error at Array.forEach ()
lovelace.0 2019-08-04 21:38:05.181 error at entities.forEach.entity (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1685:76)
lovelace.0 2019-08-04 21:38:05.181 error at Date.toISOString ()
lovelace.0 2019-08-04 21:38:05.181 error RangeError: Invalid time value
lovelace.0 2019-08-04 21:38:05.180 error uncaught exception: Invalid time value
lovelace.0 2019-08-04 21:34:39.765 info http server listening on port 8091
lovelace.0 2019-08-04 21:34:39.667 info starting. Version 0.1.3 in /opt/iobroker/node_modules/iobroker.lovelace, node: v10.16.1
lovelace.0 2019-08-04 21:34:04.386 info terminating
lovelace.0 2019-08-04 21:34:03.810 info cleaned everything up...
lovelace.0 2019-08-04 21:34:03.807 error at Timer.processTimers (timers.js:223:10)
lovelace.0 2019-08-04 21:34:03.807 error at listOnTimeout (timers.js:263:5)
lovelace.0 2019-08-04 21:34:03.807 error at tryOnTimeout (timers.js:300:5)
lovelace.0 2019-08-04 21:34:03.807 error at ontimeout (timers.js:436:11)
lovelace.0 2019-08-04 21:34:03.807 error at Timeout._updateTimer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:3146:22)
lovelace.0 2019-08-04 21:34:03.807 error at WebServer.onStateChange (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1646:22)
lovelace.0 2019-08-04 21:34:03.807 error at Array.forEach ()
lovelace.0 2019-08-04 21:34:03.807 error at entities.forEach.entity (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1685:76)
lovelace.0 2019-08-04 21:34:03.807 error at Date.toISOString ()
lovelace.0 2019-08-04 21:34:03.807 error RangeError: Invalid time value
lovelace.0 2019-08-04 21:34:03.805 error uncaught exception: Invalid time value
lovelace.0 2019-08-04 21:32:28.698 info http server listening on port 8091
lovelace.0 2019-08-04 21:32:28.604 info starting. Version 0.1.3 in /opt/iobroker/node_modules/iobroker.lovelace, node: v10.16.1

Weather Card - keine Icons

Ich habe yr.no als Daten-Lieferant getestet und nutze derzeit Weatherunderground.
Bei beiden Daten-Quellen bekomme ich in der Weather Card keine Icons angezeigt.

type-detector error

Describe the bug
type-detector error

To Reproduce
Steps to reproduce the behavior:

  1. ham for homebridge-mi-aqara
  2. TemperatureAndHumiditySensor , Current Relative Humidity
{
  "from": "system.adapter.ham.0",
  "ts": 1560063966304,
  "common": {
    "name": "Current Relative Humidity",
    "type": "number",
    "unit": "%",
    "role": "value.humidity",
    "min": 0,
    "max": 100,
    "read": true,
    "write": false,
    "custom": {
      "lovelace.0": {
        "enabled": true,
        "entity": "",
        "name": ""
      }
    }
  },
  "native": {
    "UUID": "00000010-0000-1000-8000-0026BB765291",
    "displayName": "Current Relative Humidity"
  },
  "acl": {
    "object": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator",
    "state": 1636
  },
  "_id": "ham.0.TemperatureAndHumiditySensor2_HumiditySensor_ae27.TemperatureAndHumiditySensor2_HumiditySensor_ae27.Current-Relative-Humidity",
  "type": "state"
}

Object {states: Array(6), type: "info"}

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

  • Adapter version: lovelace (0.1)

websockets not closing correctly?

Describe the bug
Everything works fine until we close and re-open browser or open front-end from another device. In this case it looks like the previous ws client is not destroyed and server continue to broadcast to closed connections. As a result with each new connection we get increasing number of data sent to the clients and states update on page reload and/or on another device stop working...

To Reproduce

  1. Restart lovelace adapter and open front-end.. at this step everything should work fine even if we just reload the page.
  2. Close browser completely -> run browser -> open front-end again.
    At this stage
    a) on page reload we get old data (looks like connection with new client does not init correctly).
    b) we start getting duplicated state_updates from server, i.e. server sends data to the closed connection from point 1.
    Here at the picture only one front-end opened, but states are duplicated:
    image

If can't repeat the issue, try to re-load page/ re-open browser couple of times.. at some point you'll see it

Adapter startet nicht (Fehler im LOG)

Nabend zusammen, erstmal danke für den vielversprechenden Adapter.
Leider kommt bei mir nach der Installation sobald ich den Adapter starte ein Error mit folgendem Inhalt:

`

Caught 2019-09-22 20:26:37.444 error by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.lovelace/node_modules/ws/index.js:3:19)
Caught 2019-09-22 20:26:37.444 error by controller[0]: at require (internal/module.js:20:19)
Caught 2019-09-22 20:26:37.444 error by controller[0]: at Module.require (module.js:504:17)
Caught 2019-09-22 20:26:37.444 error by controller[0]: at Function.Module._load (module.js:445:3)
Caught 2019-09-22 20:26:37.443 error by controller[0]: at tryModuleLoad (module.js:453:12)
Caught 2019-09-22 20:26:37.443 error by controller[0]: at Module.load (module.js:494:32)
Caught 2019-09-22 20:26:37.443 error by controller[0]: at Object.Module._extensions..js (module.js:586:10)
Caught 2019-09-22 20:26:37.443 error by controller[0]: at Module._compile (module.js:549:28)
Caught 2019-09-22 20:26:37.443 error by controller[0]: at Object.runInThisContext (vm.js:97:10)
Caught 2019-09-22 20:26:37.443 error by controller[0]: at createScript (vm.js:56:10)
Caught 2019-09-22 20:26:37.443 error by controller[0]: SyntaxError: Unexpected token ...
Caught 2019-09-22 20:26:37.443 error by controller[0]: ^^^
Caught 2019-09-22 20:26:37.442 error by controller[0]: ...options
Caught 2019-09-22 20:26:37.442 error by controller[0]: /opt/iobroker/node_modules/iobroker.lovelace/node_modules/ws/lib/websocket.js:347
Caught 2019-09-22 20:26:06.657 error by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.lovelace/node_modules/ws/index.js:3:19)
Caught 2019-09-22 20:26:06.657 error by controller[0]: at require (internal/module.js:20:19)
Caught 2019-09-22 20:26:06.657 error by controller[0]: at Module.require (module.js:504:17)
Caught 2019-09-22 20:26:06.656 error by controller[0]: at Function.Module._load (module.js:445:3)
Caught 2019-09-22 20:26:06.656 error by controller[0]: at tryModuleLoad (module.js:453:12)
Caught 2019-09-22 20:26:06.656 error by controller[0]: at Module.load (module.js:494:32)
Caught 2019-09-22 20:26:06.656 error by controller[0]: at Object.Module._extensions..js (module.js:586:10)
Caught 2019-09-22 20:26:06.656 error by controller[0]: at Module._compile (module.js:549:28)
Caught 2019-09-22 20:26:06.656 error by controller[0]: at Object.runInThisContext (vm.js:97:10)
Caught 2019-09-22 20:26:06.656 error by controller[0]: at createScript (vm.js:56:10)
Caught 2019-09-22 20:26:06.653 error by controller[0]: SyntaxError: Unexpected token ...
Caught 2019-09-22 20:26:06.653 error by controller[0]: ^^^
Caught 2019-09-22 20:26:06.653 error by controller[0]: ...options
Caught 2019-09-22 20:26:06.652 error by controller[0]: /opt/iobroker/node_modules/iobroker.lovelace/node_modules/ws/lib/websocket.js:347

`

Ich hoffe jemand kann mir weiterhelfen.. Danke im Voraus

Gruß overfl0w

MarkDown card not working

Describe the bug
Markdown card only displays title, but ignores the main text:
image

if we look at the raw page code, the markdown text is no rendered at all
image

Pleeeease take a look at it

UI optimieren

Unter ioBroker Lovelace wird das "Hamburger" Menü nicht verwendet, daher wird dieses ausgeblendet. Für die angelegten Tabs sieht das dann aber blöd aus. Es wäre besser, wenn die Tabs linksbündig anfangen.
Ich hab ein Bild angehängt, dass es verdeutlichen soll (der Platz links neben dem Haus).

Außerdem wäre eine Touch Optimierung wünschenswert, sprich das swipen zwischen Tabs.

Lovelace UI will be reset ...

Hello,

it has happened to me several times that the theme and the password for alarm reset.

I am using the midnight Theme and I can not say exactly when, but the theme will be deleted. The same is with the Alarm Password, it will be reset to 1234.

Is it a Bug or something like a demo mode?

Lovelace UI: 1.0.5

Markdown state bindings only works with first opened connection

Describe the bug
State bindings to markdown only updated with first opened connection and does not change if second front-end page opened (or opened on another device)

To Reproduce
Create MarkDown with some binding. Open second instance of lovelace page (or open on mobile) and try to change state connected to markdown. Value will only be changed in markdown card in first page opened.

Entity type: binary_sensor nicht verfügbar

Welchen Typ soll man für Bewegungsmelder wählen, wenn 'binary_sensor' nicht verfügbar ist?
Ich habe schon ziemlich alle ausprobiert, aber keiner passt hunderprozentig. Beim 'sensor', wie bei den Meisten, bekomme ich den Status 'true/false' und die Graphen (history und mini-graph-card) funktionieren nicht.

2019-12-09_092640
2019-12-09_092653
2019-12-09_092704

Wenn ich 'input_boolean' wähle, dann sind die Graphen zwar richtig, aber ich kann mit dem Schalter den Zustand ändern, was nicht das Richtige ist.

2019-12-09_092926
2019-12-09_092955
2019-12-09_093010

Ideal wäre, den Typ 'binary_sensor' zu haben, den finde ich aber nicht in der Auswahl.

Danke im Voraus für die Hilfe!

TypeError: cannot read property of '0'

directly after start the adapter don't work

2019-08-27 06:14:03.448 - info: iobroker upgrade lovelace 2019-08-27 06:14:04.529 - info: iobroker Update lovelace from @0.1.4 to @0.1.5 2019-08-27 06:14:05.139 - info: iobroker npm install [email protected] --production --save --prefix "/opt/iobroker" (System call) 2019-08-27 06:14:35.203 - info: iobroker npm install --production (System call) in "/opt/iobroker/node_modules/iobroker.lovelace" 2019-08-27 06:15:33.611 - error: iobroker system.adapter.lovelace does not exist 2019-08-27 06:15:33.612 - info: iobroker got /opt/iobroker/node_modules/iobroker.lovelace/admin 2019-08-27 06:15:33.643 - info: iobroker upload [6] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/words.js words.js application/javascript 2019-08-27 06:15:33.717 - info: iobroker upload [5] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/tab_m.html tab_m.html text/html 2019-08-27 06:15:33.772 - info: iobroker upload [4] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/style.css style.css text/css 2019-08-27 06:15:33.841 - info: iobroker upload [3] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/lovelace.png lovelace.png image/png 2019-08-27 06:15:33.910 - info: iobroker upload [2] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/js-yaml.min.js js-yaml.min.js application/javascript 2019-08-27 06:15:33.988 - info: iobroker upload [1] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/index_m.html index_m.html text/html 2019-08-27 06:15:34.051 - info: iobroker upload [0] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/custom_m.html custom_m.html text/html 2019-08-27 06:15:34.107 - info: iobroker Adapter "lovelace" updated 2019-08-27 06:19:29.541 - info: iobroker upload lovelace 2019-08-27 06:19:29.884 - info: iobroker got /opt/iobroker/node_modules/iobroker.lovelace/admin 2019-08-27 06:19:29.911 - info: iobroker upload [6] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/words.js words.js application/javascript 2019-08-27 06:19:29.982 - info: iobroker upload [5] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/tab_m.html tab_m.html text/html 2019-08-27 06:19:30.046 - info: iobroker upload [4] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/style.css style.css text/css 2019-08-27 06:19:30.101 - info: iobroker upload [3] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/lovelace.png lovelace.png image/png 2019-08-27 06:19:30.169 - info: iobroker upload [2] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/js-yaml.min.js js-yaml.min.js application/javascript 2019-08-27 06:19:30.243 - info: iobroker upload [1] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/index_m.html index_m.html text/html 2019-08-27 06:19:30.303 - info: iobroker upload [0] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/custom_m.html custom_m.html text/html 2019-08-27 06:19:30.366 - error: iobroker system.adapter.lovelace does not exist 2019-08-27 06:19:36.483 - info: iobroker add lovelace --host iobroker 2019-08-27 06:19:36.843 - info: iobroker host.iobroker install adapter lovelace 2019-08-27 06:19:36.855 - info: iobroker got /opt/iobroker/node_modules/iobroker.lovelace/admin 2019-08-27 06:19:36.880 - info: iobroker upload [6] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/words.js words.js application/javascript 2019-08-27 06:19:36.948 - info: iobroker upload [5] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/tab_m.html tab_m.html text/html 2019-08-27 06:19:37.005 - info: iobroker upload [4] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/style.css style.css text/css 2019-08-27 06:19:37.066 - info: iobroker upload [3] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/lovelace.png lovelace.png image/png 2019-08-27 06:19:37.136 - info: iobroker upload [2] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/js-yaml.min.js js-yaml.min.js application/javascript 2019-08-27 06:19:37.210 - info: iobroker upload [1] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/index_m.html index_m.html text/html 2019-08-27 06:19:37.277 - info: iobroker upload [0] lovelace.admin /opt/iobroker/node_modules/iobroker.lovelace/admin/custom_m.html custom_m.html text/html 2019-08-27 06:19:37.441 - info: iobroker host.iobroker object system.adapter.lovelace created 2019-08-27 06:19:37.467 - info: iobroker host.iobroker create instance lovelace 2019-08-27 06:19:37.488 - info: iobroker host.iobroker object lovelace.0.notifications.clear created 2019-08-27 06:19:37.517 - info: iobroker host.iobroker object lovelace.0.notifications.add created 2019-08-27 06:19:37.545 - info: iobroker host.iobroker object lovelace.0.notifications.list created 2019-08-27 06:19:37.573 - info: iobroker host.iobroker object lovelace.0.notifications created 2019-08-27 06:19:37.602 - info: iobroker host.iobroker object lovelace.0.control.alarm created 2019-08-27 06:19:37.630 - info: iobroker host.iobroker object lovelace.0.control.shopping_list created 2019-08-27 06:19:37.661 - info: iobroker host.iobroker object lovelace.0.control.data created 2019-08-27 06:19:37.689 - info: iobroker host.iobroker object lovelace.0.control.command created 2019-08-27 06:19:37.718 - info: iobroker host.iobroker object lovelace.0.control.instance created 2019-08-27 06:19:37.746 - info: iobroker host.iobroker object lovelace.0.control created 2019-08-27 06:19:37.775 - info: iobroker host.iobroker object lovelace.0.session created 2019-08-27 06:19:37.803 - info: iobroker host.iobroker object lovelace.0.configuration created 2019-08-27 06:19:37.833 - info: iobroker host.iobroker object lovelace.0 created 2019-08-27 06:19:37.861 - info: iobroker host.iobroker object lovelace.0.info.entitiesUpdated created 2019-08-27 06:19:37.890 - info: iobroker host.iobroker object lovelace.0.connected created 2019-08-27 06:19:37.921 - info: iobroker host.iobroker object lovelace.0.info created 2019-08-27 06:19:37.949 - info: iobroker host.iobroker object system.adapter.lovelace.0.outputCount created 2019-08-27 06:19:37.978 - info: iobroker host.iobroker object system.adapter.lovelace.0.inputCount created 2019-08-27 06:19:38.007 - info: iobroker host.iobroker object system.adapter.lovelace.0.uptime created 2019-08-27 06:19:38.036 - info: iobroker host.iobroker object system.adapter.lovelace.0.memRss created 2019-08-27 06:19:38.071 - info: iobroker host.iobroker object system.adapter.lovelace.0.memHeapTotal created 2019-08-27 06:19:38.116 - info: iobroker host.iobroker object system.adapter.lovelace.0.memHeapUsed created 2019-08-27 06:19:38.145 - info: iobroker host.iobroker object system.adapter.lovelace.0.cputime created 2019-08-27 06:19:38.183 - info: iobroker host.iobroker object system.adapter.lovelace.0.cpu created 2019-08-27 06:19:38.388 - info: iobroker host.iobroker object system.adapter.lovelace.0.connected created 2019-08-27 06:19:38.415 - info: iobroker host.iobroker object system.adapter.lovelace.0.alive created 2019-08-27 06:19:39.738 - info: host.iobroker object change system.adapter.lovelace.0 2019-08-27 06:19:39.757 - info: host.iobroker instance system.adapter.lovelace.0 started with pid 32100 2019-08-27 06:19:39.808 - info: iobroker host.iobroker object system.adapter.lovelace.0 created 2019-08-27 06:19:41.012 - info: lovelace.0 starting. Version 0.1.5 in /opt/iobroker/node_modules/iobroker.lovelace, node: v10.16.2 2019-08-27 06:19:41.043 - info: lovelace.0 http server listening on port 8091 2019-08-27 06:19:44.248 - error: lovelace.0 uncaught exception: Cannot read property '0' of undefined 2019-08-27 06:19:44.249 - error: lovelace.0 TypeError: Cannot read property '0' of undefined at WebServer._iobState2EntityState (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1283:43) at ids.forEach (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1609:90) at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1603:29) 2019-08-27 06:19:44.249 - info: lovelace.0 cleaned everything up... 2019-08-27 06:19:45.252 - info: lovelace.0 cleaned everything up... 2019-08-27 06:19:45.271 - error: Caught by controller[0]: at WebServer._iobState2EntityState (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1283:43) 2019-08-27 06:19:45.271 - error: Caught by controller[0]: at ids.forEach (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1609:90) 2019-08-27 06:19:45.271 - error: Caught by controller[0]: at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1603:29) 2019-08-27 06:19:45.271 - error: host.iobroker instance system.adapter.lovelace.0 terminated with code 6 (uncaught exception) 2019-08-27 06:19:45.271 - info: host.iobroker Restart adapter system.adapter.lovelace.0 because enabled 2019-08-27 06:20:15.287 - info: host.iobroker instance system.adapter.lovelace.0 started with pid 439 2019-08-27 06:20:16.164 - info: lovelace.0 starting. Version 0.1.5 in /opt/iobroker/node_modules/iobroker.lovelace, node: v10.16.2 2019-08-27 06:20:16.195 - info: lovelace.0 http server listening on port 8091 2019-08-27 06:20:19.605 - error: lovelace.0 uncaught exception: Cannot read property '0' of undefined 2019-08-27 06:20:19.606 - error: lovelace.0 TypeError: Cannot read property '0' of undefined at WebServer._iobState2EntityState (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1283:43) at ids.forEach (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1609:90) at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1603:29) 2019-08-27 06:20:19.606 - info: lovelace.0 cleaned everything up... 2019-08-27 06:20:20.609 - info: lovelace.0 cleaned everything up... 2019-08-27 06:20:20.629 - error: Caught by controller[0]: at WebServer._iobState2EntityState (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1283:43) 2019-08-27 06:20:20.629 - error: Caught by controller[0]: at ids.forEach (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1609:90) 2019-08-27 06:20:20.629 - error: Caught by controller[0]: at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1603:29) 2019-08-27 06:20:20.629 - error: host.iobroker instance system.adapter.lovelace.0 terminated with code 6 (uncaught exception) 2019-08-27 06:20:20.629 - info: host.iobroker Restart adapter system.adapter.lovelace.0 because enabled 2019-08-27 06:20:50.646 - info: host.iobroker instance system.adapter.lovelace.0 started with pid 1545 2019-08-27 06:20:51.462 - info: lovelace.0 starting. Version 0.1.5 in /opt/iobroker/node_modules/iobroker.lovelace, node: v10.16.2 2019-08-27 06:20:51.496 - info: lovelace.0 http server listening on port 8091 2019-08-27 06:20:54.327 - error: lovelace.0 uncaught exception: Cannot read property '0' of undefined 2019-08-27 06:20:54.327 - error: lovelace.0 TypeError: Cannot read property '0' of undefined at WebServer._iobState2EntityState (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1283:43) at ids.forEach (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1609:90) at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1603:29) 2019-08-27 06:20:54.328 - info: lovelace.0 cleaned everything up... 2019-08-27 06:20:55.330 - info: lovelace.0 cleaned everything up... 2019-08-27 06:20:55.389 - error: Caught by controller[0]: at WebServer._iobState2EntityState (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1283:43) 2019-08-27 06:20:55.389 - error: Caught by controller[0]: at ids.forEach (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1609:90) 2019-08-27 06:20:55.389 - error: Caught by controller[0]: at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1603:29) 2019-08-27 06:20:55.389 - error: host.iobroker instance system.adapter.lovelace.0 terminated with code 6 (uncaught exception) 2019-08-27 06:20:55.389 - info: host.iobroker Restart adapter system.adapter.lovelace.0 because enabled 2019-08-27 06:20:58.979 - info: host.iobroker object change system.adapter.lovelace.0 2019-08-27 06:20:58.994 - info: host.iobroker instance system.adapter.lovelace.0 started with pid 1871 2019-08-27 06:20:59.833 - info: lovelace.0 starting. Version 0.1.5 in /opt/iobroker/node_modules/iobroker.lovelace, node: v10.16.2 2019-08-27 06:20:59.862 - info: lovelace.0 http server listening on port 8000 2019-08-27 06:21:02.885 - error: lovelace.0 uncaught exception: Cannot read property '0' of undefined 2019-08-27 06:21:02.885 - error: lovelace.0 TypeError: Cannot read property '0' of undefined at WebServer._iobState2EntityState (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1283:43) at ids.forEach (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1609:90) at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1603:29) 2019-08-27 06:21:02.886 - info: lovelace.0 cleaned everything up... 2019-08-27 06:21:03.889 - info: lovelace.0 cleaned everything up... 2019-08-27 06:21:03.911 - error: Caught by controller[0]: at WebServer._iobState2EntityState (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1283:43) 2019-08-27 06:21:03.911 - error: Caught by controller[0]: at ids.forEach (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1609:90) 2019-08-27 06:21:03.911 - error: Caught by controller[0]: at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1603:29) 2019-08-27 06:21:03.912 - error: host.iobroker instance system.adapter.lovelace.0 terminated with code 6 (uncaught exception) 2019-08-27 06:21:03.912 - info: host.iobroker Restart adapter system.adapter.lovelace.0 because enabled 2019-08-27 06:21:27.784 - info: host.iobroker object change system.adapter.lovelace.0 2019-08-27 06:21:27.784 - info: host.iobroker "system.adapter.lovelace.0" disabled 2019-08-27 06:21:34.888 - error: lovelace.0 adapter disabled 2019-08-27 06:21:34.993 - error: host.iobroker instance system.adapter.lovelace.0 terminated with code 3 (Adapter disabled or invalid config) 2019-08-27 06:21:34.994 - info: host.iobroker Do not restart adapter system.adapter.lovelace.0 because disabled or deleted

Thermostat Card shows old values

If i open lovelace in the Browser (Windows/Android) or reload the Page, the Thermostat Card shows me old values (Temperature). After a while (1-2 min) or if i change the Temperature (pe. via CCU) the correct value is loaded. If i reload the page again the old value appears.

1570709744972-lovelace3

Version 0.2.1 installed

Zweite Instance von einem Adapter wird nicht als Entität erkannt

Beispiel:
milight.0.zone1.state wird erkannt
milight.1.zone1.state wird dann nicht mehr erkannt

Steps to reproduce the behavior:

  1. milight.0.zone1.state schalte auf aktiviert im Objeckt und setze Name und Typ, weise einer Funktionien hinzu, starte Adapter neu, wird als Entität erkannt
  2. milight.1.zone1.state schalte auf aktiviert im Objeckt und setze Name und Typ, weise einer Funktionien hinzu, starte Adapter neu, wird nicht als Entität erkannt

Versions:

  • Adapter version: 0.1.1
  • JS-Controller version: 1.5.12
  • Node version: 8.16
  • Operating system: debian stretch

Duplicated device found when autocreate

Describe the bug
I have number of virtual thermostats which are created in iob like this:
image

Each device has the same name "датчик температуры" and from my point of view it is correct, because they are the same devices.
When lovelace autocreate devices it uses this name and as a result only one Thermostat is crated and all other are ignored because of duplicates.

Expected behavior
Is it possible to update code to generate unique entities in such cases? e.g. entity ID can be created using object._id and not the device name..
It is really weird to think of unique name for each identical device

HS100 Adapter lässt sich nicht als Entität hinzufügen

Beispiel:
hs100.0.IP.state wird nicht als Entität erkannt

Steps to reproduce the behavior:

  1. hs100.0.IP.state schalte auf aktiviert im Objeckt und setze Name und Typ, weise einer Funktionien hinzu, starte Adapter neu, wird nicht als Entität erkannt

Versions:

  • Adapter version: 0.1.1
  • JS-Controller version: 1.5.12
  • Node version: 8.16
  • Operating system: debian stretch

Darstellungsfehler bei Benachrichtigungen

In der neusten Version ist ein Darstellungsfehler, über ein Smartphone sind die Benachrichtigungen nach rechts verschoben (siehe Bild).
Ich habe es auf verschiedenen Browsern überprüft und auch Browserdaten gelöscht, Problem immernoch vorhanden.

In der Version 0.2.3 war dieses Problem noch nicht.

1574517665451-20191123_150023

Crashing after login with a new user

Describe the bug
Lovelace UI crasht after login with a new user.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new User in iobroker
  2. Login in Lovelace UI

Expected behavior
Expected to login in the Lovelace UI.

Screenshots & Logfiles

019-12-16 12:21:42.351 - error: lovelace.0 (21285) uncaught exception: Cannot read property 'common' of undefined 2019-12-16 12:21:42.352 - error: lovelace.0 (21285) TypeError: Cannot read property 'common' of undefined at WebServer.__getObjectName (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:2311:17) at WebServer._getObjectName (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:2332:30) at adapter.getForeignObject (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:3155:28) at objects.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2450:65) at _0x507b32.(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:64576) at checkObjectRights (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsUtils.js:602:16) at _0x2bea52.objects.getUserGroup (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsUtils.js:553:13) at _0x507b32.(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:21056) at objects.getObjectList (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsUtils.js:455:13) at (anonymous function).(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:92144) 2019-12-16 12:21:42.353 - info: lovelace.0 (21285) cleaned everything up... 2019-12-16 12:21:42.364 - info: lovelace.0 (21285) terminating 2019-12-16 12:21:42.365 - info: lovelace.0 (21285) Terminated (NO_ERROR): Without reason 2019-12-16 12:21:42.882 - error: host.raspberrypi Caught by controller[0]: TypeError: Cannot read property 'common' of undefined 2019-12-16 12:21:42.883 - error: host.raspberrypi Caught by controller[0]: at WebServer.__getObjectName (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:2311:17) 2019-12-16 12:21:42.883 - error: host.raspberrypi Caught by controller[0]: at WebServer._getObjectName (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:2332:30) 2019-12-16 12:21:42.883 - error: host.raspberrypi Caught by controller[0]: at adapter.getForeignObject (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:3155:28) 2019-12-16 12:21:42.883 - error: host.raspberrypi Caught by controller[0]: at objects.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2450:65) 2019-12-16 12:21:42.883 - error: host.raspberrypi Caught by controller[0]: at _0x507b32.(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:64576) 2019-12-16 12:21:42.884 - error: host.raspberrypi Caught by controller[0]: at checkObjectRights (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsUtils.js:602:16) 2019-12-16 12:21:42.884 - error: host.raspberrypi Caught by controller[0]: at _0x2bea52.objects.getUserGroup (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsUtils.js:553:13) 2019-12-16 12:21:42.884 - error: host.raspberrypi Caught by controller[0]: at _0x507b32.(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:21056) 2019-12-16 12:21:42.884 - error: host.raspberrypi Caught by controller[0]: at objects.getObjectList (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsUtils.js:455:13) 2019-12-16 12:21:42.884 - error: host.raspberrypi Caught by controller[0]: at (anonymous function).(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:92144) 2019-12-16 12:21:42.884 - info: host.raspberrypi instance system.adapter.lovelace.0 terminated with code 0 (NO_ERROR)

Versions:

  • Adapter version: 1.0.6
  • JS-Controller version: 2.1.1
  • Node version: v10.17.0
  • Operating system: debian buster raspi
  • ioBroker.admin 3.7.2

Please check ioBroker.lovelace 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.

Question: Lovelace support in devices like in the Homematic adapter

The Lovelace adapter finds all information (entity) for the homematic adapter by it self and the user has not add the entity by it self under objects.
What do I have to do to provide this options in my adapters too? I would like to add this features in the shelly and lupusec adapter.

Bildschirmfoto 2019-10-15 um 20 52 01

Anmeldezeitlimit deaktivieren?

Hallo,

es gibt ja leider keine App für die lovelace UI. Ich will daher für mein Smartphone die lovelace URL als App starten, mit "Zum Home-Bildschirm" via iOS.

Ich habe unter den Adapterkonfiguration: lovelace.0 den Anmeldezeitlimit auf 0 gesetzt, scheint aber leider nicht zu funktionieren. Ich muss mich weiterhin alle paar Male anmelden.
Auch das Passwort Speichern unter Safari scheint nicht zu funktionieren.

Hat da jemand eine Lösung für?

Node-RED Daten werden nicht mit Glance dargestellt

Objekte aus Node-Red

Können in Sensor-Card dargestellt werden
image

aber nicht in einer Glance-Card

mit Zigbee ausgelesene Sensorwert alleine, funktionieren einwandfrei. (selbe wie Bild 3 nur ohne Node-Red Wert)

How to access devices based on mqtt communication

I have a lot of equipment, they are mqtt communication, for example, climate, curtains. Its command is different from the status data point. . in the figure, 1 is the command topic and 2 is the status topic. What can I do to make them appear in Lovelace
1212

Problem bei Umlauten

Ich habe zwei Räume mit Umlauten (Büro und Gäste WC). Dadurch erhalte ich Fehlermeldungen.

Screenshot_20190602-152327

Verify Compact mode for your adapter

We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.

Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512

On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.

Thank you for your support.

adpater settings: theme editor not shown with Firefox 68.0.2 and admin 3.6.4

I updated the admin adpater from 3.6.2 to 3.6.4. Now the theme editor (new yaml editor) not shown anymore with Firefox 68.0.2.

With Admin 3.6.2 theme editor is shown - old layout (<textarea id="themes_fallback"></textarea>)

I tested it also with Edge 42.17134.1.0, theme editor (new yaml editor) is shown.

Light Card ohne Dimmfunktion

Hallo
Mein Adapter hab ich sowohl via Iobroker-Adapter, als auch via Github (Expertenmodus) installiert. Beim hinzufügen mit der Karte "Light" erscheint kein Einstellbogen über der Lampe. Im Datenpunkt number und light pobiert. Dimmen mithilfe eines normalen sliders funktioniert.

Alles mit Chrome (PC&Tablet) ausprobiert.

Noch jemand mit dem Problem oder gar einer Lösung hier?

Gruß Nelzon

Adapter Crash when interacting with ui

I just installed the latest version of the Lovelace adapter, but cannot get it to run stable. I have a number of lamps assigned to rooms, and they do show up on the ui, but as soon as i try to change the state, the adapter crashes with the following log.


2019-08-26 17:48:07.108 - error: Caught by controller[0]: TypeError: Cannot read property 'brightness_pct' of undefined
--
2019-08-26 17:48:07.108 - error: Caught by controller[0]: at Socket.adapter.setForeignState (/opt/iobroker/node_modules/iobroker.lovelace/lib/server.js:1046:52)
2019-08-26 17:48:07.109 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
2019-08-26 17:48:07.109 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)
2019-08-26 17:48:07.109 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2019-08-26 17:48:07.110 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
2019-08-26 17:48:07.110 - error: Caught by controller[0]: at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
2019-08-26 17:48:07.110 - error: Caught by controller[0]: at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2019-08-26 17:48:07.110 - error: Caught by controller[0]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
2019-08-26 17:48:07.111 - error: Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
2019-08-26 17:48:07.111 - error: Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
2019-08-26 17:48:07.111 - error: host.ioTinker instance system.adapter.lovelace.0 terminated with code 6 (uncaught exception)

Note - the lights i am trying to switch are using the deconz adapter.

My system is:
Asus Tinkerboard with Raspbian
Node 8.15
NPM 6.5.0
Admin 3.6.0
JS Controller 1.5.7

Adapter Rot V 0.0.2 und 0.0.3

Edit: Er wird Grün und nach 2-3 Sekunden Rot......
Neustart das selben Problem.

Screenshots & Logfiles
`

lovelace.0 2019-06-03 09:08:34.839 info cleaned everything up...
lovelace.0 2019-06-03 09:08:33.829 info cleaned everything up...
lovelace.0 2019-06-03 09:08:33.829 error at Manager.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
lovelace.0 2019-06-03 09:08:33.829 error at Manager. (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\component-bind\index.js:21:15)
lovelace.0 2019-06-03 09:08:33.829 error at Socket.onpacket (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:236:12)
lovelace.0 2019-06-03 09:08:33.829 error at Socket.onack (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:312:9)
lovelace.0 2019-06-03 09:08:33.829 error at Socket. (C:\ioBroker\node_modules\iobroker.js-controller\lib\states\statesInMemClient.js:157:27)
lovelace.0 2019-06-03 09:08:33.829 error at that.states.getStates (C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:4540:25)
lovelace.0 2019-06-03 09:08:33.829 error at adapter.getForeignStates (C:\ioBroker\node_modules\iobroker.lovelace\lib\server.js:1562:29)
lovelace.0 2019-06-03 09:08:33.829 error at Array.forEach ()
lovelace.0 2019-06-03 09:08:33.829 error at ids.forEach (C:\ioBroker\node_modules\iobroker.lovelace\lib\server.js:1570:33)
lovelace.0 2019-06-03 09:08:33.829 error at setJsonAttribute (C:\ioBroker\node_modules\iobroker.lovelace\lib\server.js:109:24)
lovelace.0 2019-06-03 09:08:33.829 error TypeError: Cannot read property 'split' of undefined
lovelace.0 2019-06-03 09:08:33.829 error uncaught exception: Cannot read property 'split' of undefined

`

Versions:
Platform: Windows
Architecture: x64
CPUs: 4
Speed: 3912 MHz
Model: Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz
RAM: 7.9 GB
Node.js: v8.16.0
NPM: 6.4.1
ioBroker.js-controller: 1.5.12
Admin: 3.6.3

Additional context
Add any other context about the problem here.

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.