Giter Site home page Giter Site logo

iobroker.mihome-cloud's People

Contributors

ta2k avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

iobroker.mihome-cloud's Issues

Bugs in Kombination mit einem Xiaomi Air Purifier 2H

Ich möchte an dieser Stelle mehrere Bugs in Kombination mit meinem Xiaomi Air Purifier 2H melden.

  1. Der Datenpunkt "mihome-cloud.0.314913106.remote.fan-level" zeigt bei mir Werte an, die eher zu dem Datenpunkt "mihome-cloud.0.314913106.remote.mode" gehören. Normal wäre eine Auswahl der Stufen von 0 bis 16.

  2. Wenn der Adapter startet erhalte ich hin und wieder die Warnmeldung "slow connection to objects DB. Still waiting ...". Möglicherweise liegt dies an meinem AdGuard Home DNS Server. Jedoch startet die Xiaomi Home App ohne Probleme und verbindet sich zügig. Bei den geblockten Einträgen im AdGuard Home ist bei dem besagten Zeitstempel nichts zu sehen.

  3. Wenn ich den Air Purifier über die Xiaomi Home App starte, wird der Datenpunkt "mihome-cloud.0.314913106.remote.on" nicht auf true gesetzt. Dabei habe ich auch den Aktualisierungsintervall (10min) abgewartet.
    Auch bie Datenpunkte der Funktionen "Kindersicherung", "Licht" und "Benachrichtigungston" werden nicht aktualisiert.

  4. Wenn ich die Datenpunkte ("Kindersicherung", "Licht" und "Benachrichtigungston") unter ioBroker von Hand setze, werden diese am Gerät nicht übernommen.

  5. Der Datenpunkt "mihome-cloud.0.314913106.remote.on" springt nach dem setzen auf "true" nach kurzer Zeit wieder auf "false". Dabei wird der Air Purifier nicht ausgeschaltet. Zum ausschalten muss der Datenpunkt nochmals von Hand auf "false" gesetzt werden.

  6. Unter den Status Datenpunkten ist ein kleine Fehler. Der Datenpunkt "mihome-cloud.0.314913106.status.pm2.5-density" sollte eher "mihome-cloud.0.314913106.status.pm25-density" oder "mihome-cloud.0.314913106.status.pm-density" heißen.

  7. Der Datenpunkt "mihome-cloud.0.314913106.status.filter-left-time" zeigt keine Daten an.

Anbei ein Export der Objekte-Struktur und ein Log aus meinem ioBroker:
mihome-cloud.zip
Adapter.zip

Invalid or unsupported zip format.

Describe the bug
mihome-cloud adapter throws errors.

Screenshots & Logfiles

mihome-cloud.0 | 2024-03-27 06:38:03.146 | error | Error: Invalid or unsupported zip format. No END header found at readMainHeader (/opt/iobroker/node_modules/adm-zip/zipFile.js:101:32) at new module.exports (/opt/iobroker/node_modules/adm-zip/zipFile.js:19:9) at new module.exports (/opt/iobroker/node_modules/adm-zip/adm-zip.js:62:18) at /opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:356:27 at processTicksAndRejections (node:internal/process/task_queues:95:5) at MihomeCloud.fetchPlugins (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:349:9) at /opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:270:11 at MihomeCloud.getDeviceList (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:211:5) at MihomeCloud.onReady (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:96:7) -- | -- | -- | -- mihome-cloud.0 | 2024-03-27 06:38:03.141 | error | Error: Invalid or unsupported zip format. No END header found mihome-cloud.0 | 2024-03-27 06:37:49.402 | error | Error: Invalid or unsupported zip format. No END header found at readMainHeader (/opt/iobroker/node_modules/adm-zip/zipFile.js:101:32) at new module.exports (/opt/iobroker/node_modules/adm-zip/zipFile.js:19:9) at new module.exports (/opt/iobroker/node_modules/adm-zip/adm-zip.js:62:18) at /opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:356:27 at processTicksAndRejections (node:internal/process/task_queues:95:5) at MihomeCloud.fetchPlugins (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:349:9) at /opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:270:11 at MihomeCloud.getDeviceList (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:211:5) at MihomeCloud.onReady (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:96:7) mihome-cloud.0 | 2024-03-27 06:37:49.393 | error | Error: Invalid or unsupported zip format. No END header found

Versions:
Admin Version: 6.13.16
MiHome-Cloud Version: 0.1.0
Node.js: v18.20.0
NPM: 10.5.0

Update stable version in repo from 0.1.0 to 0.1.1

Think about update stable version to 0.1.1

Version: stable=0.1.0 (199 days old) => latest=0.1.1 (15 days old)
Installs: stable=417 (82.41%), latest=56 (11.07%), total=506

Click to use developer portal
Click to edit

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

Mi Switch without status

Ich habe eine M iSwitch 2. Es gint für das Gerät eine Eintrag in dem Objektbaum. Jedoch fehlt der Status, der ausgibt, ob der Schalter gedrückt, doppeltgedrückt oder lange gedrückt wurde.

Unter dem Ordern mit der Objekt-ID sind die beiden Odern gerneral und remote Plugins vorhaben. Der Eintrag status fehlt.

Z.B. bei einem Bewegungsmelder ist der Objektbaum vollständig.

Warnung im Log des iobroker:
No properties for lumi.sensor_switch.v2 Switch Sensor cannot extract information

Mi Air Purifier 2 + favorite-fan-level

Ich möchte einen Fehler in Verbindung mit dem favorite-fan-level unter remote melden.

Der favorite-fan-level kann in der App etc. bis auf Stufe 16 (Maximalstufe) erhöht werden. Im Adapter ist dies leider nur bis Stufe 10 möglich, alles was darüber hinausgeht wird mit einem Fehler quittiert.

axios time out erhöhen?

Ich bekomme regelmäßig nachstehende Meldungen im Log. Kann man ggf. das timeout an der Stelle erhöhen?

2023-04-02 04:23:28.489  - error: mihome-cloud.0 (618526) /miotspec/prop/get
2023-04-02 04:23:28.490  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
2023-04-02 04:23:28.659  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
    at Function.AxiosError.from (/opt/iobroker/node_modules/axios/lib/core/AxiosError.js:89:14)
    at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/axios/lib/adapters/http.js:577:25)
    at RedirectableRequest.emit (node:events:512:28)
    at RedirectableRequest.emit (node:domain:489:12)
    at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
    at ClientRequest.emit (node:events:524:35)
    at ClientRequest.emit (node:domain:489:12)
    at ClientRequest.req.emit (/opt/iobroker/node_modules/iobroker.mihome-cloud/node_modules/http-cookie-agent/dist/http/create_cookie_agent.js:84:16)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:512:28)
2023-04-02 05:53:49.955  - error: mihome-cloud.0 (618526) /miotspec/prop/get
2023-04-02 05:53:49.956  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
2023-04-02 05:53:49.958  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
    at Function.AxiosError.from (/opt/iobroker/node_modules/axios/lib/core/AxiosError.js:89:14)
    at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/axios/lib/adapters/http.js:577:25)
    at RedirectableRequest.emit (node:events:512:28)
    at RedirectableRequest.emit (node:domain:489:12)
    at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
    at ClientRequest.emit (node:events:524:35)
    at ClientRequest.emit (node:domain:489:12)
    at ClientRequest.req.emit (/opt/iobroker/node_modules/iobroker.mihome-cloud/node_modules/http-cookie-agent/dist/http/create_cookie_agent.js:84:16)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:512:28)
2023-04-02 06:35:01.122  - error: mihome-cloud.0 (618526) /miotspec/prop/get
2023-04-02 06:35:01.123  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
2023-04-02 06:35:01.125  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
    at Function.AxiosError.from (/opt/iobroker/node_modules/axios/lib/core/AxiosError.js:89:14)
    at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/axios/lib/adapters/http.js:577:25)
    at RedirectableRequest.emit (node:events:512:28)
    at RedirectableRequest.emit (node:domain:489:12)
    at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
    at ClientRequest.emit (node:events:524:35)
    at ClientRequest.emit (node:domain:489:12)
    at ClientRequest.req.emit (/opt/iobroker/node_modules/iobroker.mihome-cloud/node_modules/http-cookie-agent/dist/http/create_cookie_agent.js:84:16)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:512:28)
2023-04-02 06:36:24.322  - error: mihome-cloud.0 (618526) /miotspec/prop/get
2023-04-02 06:36:24.323  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
2023-04-02 06:36:24.324  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
    at Function.AxiosError.from (/opt/iobroker/node_modules/axios/lib/core/AxiosError.js:89:14)
    at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/axios/lib/adapters/http.js:577:25)
    at RedirectableRequest.emit (node:events:512:28)
    at RedirectableRequest.emit (node:domain:489:12)
    at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
    at ClientRequest.emit (node:events:524:35)
    at ClientRequest.emit (node:domain:489:12)
    at ClientRequest.req.emit (/opt/iobroker/node_modules/iobroker.mihome-cloud/node_modules/http-cookie-agent/dist/http/create_cookie_agent.js:84:16)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:512:28)
2023-04-02 07:00:00.259  - error: mihome-cloud.0 (618526) /miotspec/prop/get
2023-04-02 07:00:00.259  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
2023-04-02 07:00:00.262  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
    at Function.AxiosError.from (/opt/iobroker/node_modules/axios/lib/core/AxiosError.js:89:14)
    at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/axios/lib/adapters/http.js:577:25)
    at RedirectableRequest.emit (node:events:512:28)
    at RedirectableRequest.emit (node:domain:489:12)
    at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
    at ClientRequest.emit (node:events:524:35)
    at ClientRequest.emit (node:domain:489:12)
    at ClientRequest.req.emit (/opt/iobroker/node_modules/iobroker.mihome-cloud/node_modules/http-cookie-agent/dist/http/create_cookie_agent.js:84:16)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:512:28)
2023-04-02 08:13:15.001  - error: mihome-cloud.0 (618526) /miotspec/prop/get
2023-04-02 08:13:15.002  - error: mihome-cloud.0 (618526) Error: socket hang up
2023-04-02 08:13:15.004  - error: mihome-cloud.0 (618526) Error: socket hang up
    at Function.AxiosError.from (/opt/iobroker/node_modules/axios/lib/core/AxiosError.js:89:14)
    at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/axios/lib/adapters/http.js:577:25)
    at RedirectableRequest.emit (node:events:512:28)
    at RedirectableRequest.emit (node:domain:489:12)
    at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
    at ClientRequest.emit (node:events:524:35)
    at ClientRequest.emit (node:domain:489:12)
    at ClientRequest.req.emit (/opt/iobroker/node_modules/iobroker.mihome-cloud/node_modules/http-cookie-agent/dist/http/create_cookie_agent.js:84:16)
    at TLSSocket.socketOnEnd (node:_http_client:519:9)
    at TLSSocket.emit (node:events:524:35)
2023-04-02 08:22:59.420  - warn: mihome-cloud.0 (618526) Error getting Status of the device via Plugin for Ventilator (90211825) with {"id":0,"method":"get_prop","accessKey":"IOS00026747c5acafc2","params":[]}
2023-04-02 08:22:59.421  - warn: mihome-cloud.0 (618526) {"code":-3,"error":{"code":-3,"message":"timeout"},"exe_time":0,"id":8195745,"message":"timeout","net_cost":0,"ot_cost":0}
2023-04-02 08:36:00.089  - info: host.chet instance system.adapter.iceroad.0 started with pid 642883
2023-04-02 08:36:02.327  - info: iceroad.0 (642883) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.iceroad, node: v19.8.1, js-controller: 5.0.1-alpha.0-20230330-e0b409fe
2023-04-02 08:36:03.071  - info: iceroad.0 (642883) Terminated (NO_ERROR): Without reason
2023-04-02 08:36:03.617  - info: host.chet instance system.adapter.iceroad.0 terminated with code 0 (NO_ERROR)
2023-04-02 10:23:58.596  - error: mihome-cloud.0 (618526) /miotspec/prop/get
2023-04-02 10:23:58.597  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
2023-04-02 10:23:58.600  - error: mihome-cloud.0 (618526) Error: read ETIMEDOUT
    at Function.AxiosError.from (/opt/iobroker/node_modules/axios/lib/core/AxiosError.js:89:14)
    at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/axios/lib/adapters/http.js:577:25)
    at RedirectableRequest.emit (node:events:512:28)
    at RedirectableRequest.emit (node:domain:489:12)
    at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
    at ClientRequest.emit (node:events:524:35)
    at ClientRequest.emit (node:domain:489:12)
    at ClientRequest.req.emit (/opt/iobroker/node_modules/iobroker.mihome-cloud/node_modules/http-cookie-agent/dist/http/create_cookie_agent.js:84:16)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:512:28)

Various error messages

In the log there are various error messages:

Node.js: v18.18.2
NPM: 9.8.1
js-controller 5.0.12

mihome-cloud.0 2023-11-12 17:55:12.206 error Error: Invalid or unsupported zip format. No END header found at readMainHeader (/opt/iobroker/node_modules/adm-zip/zipFile.js:101:32) at new module.exports (/opt/iobroker/node_modules/adm-zip/zipFile.js:19:9) at new module.exports (/opt/iobroker/node_modules/adm-zip/adm-zip.js:62:18) at /opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:356:27 at processTicksAndRejections (node:internal/process/task_queues:95:5) at MihomeCloud.fetchPlugins (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:349:9) at /opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:270:11 at MihomeCloud.getDeviceList (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:211:5) at MihomeCloud.onReady (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:96:7)
mihome-cloud.0 2023-11-12 17:55:12.198 error Error: Invalid or unsupported zip format. No END header found

Please consider fixing issues found by adapter checker

Adapter Checker (https://www.iobroker.dev/adapter-check) reports several issues for this adapter. Please consider fixing them.

In addition no release tags and no release are visible at guithub. Please consider using the iobroker release script environment.

[E120] Unknown type found in io-package.json
[E402] Types of adapter in latest repository and in io-package.json are different "iot-systems" !== "it-systems"
[E405] Icon must be in the following path: https://raw.githubusercontent.com/TA2k/ioBroker.mihome-cloud/main/
[E407] Meta URL (latest) must be equal to https://raw.githubusercontent.com/TA2k/ioBroker.mihome-cloud/main/io-package.json
[E422] Types of adapter in stable repository and in io-package.json are different "iot-systems" !== "it-systems"
[E426] Icon (stable) must be in the following path: https://raw.githubusercontent.com/TA2k/ioBroker.mihome-cloud/main/
[E428] Meta URL (stable) must be equal to https://raw.githubusercontent.com/TA2k/ioBroker.mihome-cloud/main/io-package.json
[E606] Current adapter version 0.0.5 not found in README.md
[E605] No actual year found in copyright. Please add "Copyright (c) 2023 TA2k [email protected]" at the end of README.md
[E701] No actual year found in LICENSE. Please add "Copyright (c) 2023 TA2k [email protected]" at the start of LICENSE

[W171] "common.title" is deprecated in io-package.json
[W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[W515] Why you decided to disable i18n support?

Please use english language for Readme.md

As confirmed by @appollon77 the main Readme.md should be written in english.
Please rewrite Readme.md to use english langauge for the next release of the adapter.

Additional Readme's using differnet language are a good servie, so please feel free to keep the german version too.

Crash vom Adapter

miio.0
2024-01-12 08:54:39.897 error Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at Miio._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5448:49) at Miio.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5409:21) at Miio.miioAdapterUpdateState (/opt/iobroker/node_modules/iobroker.miio/build/main.js:142:18) at Controller. (/opt/iobroker/node_modules/iobroker.miio/build/main.js:441:30) at Controller.emit (node:events:517:28) at DeviceClass. (/opt/iobroker/node_modules/iobroker.miio/build/lib/miio.js:181:22) at DeviceClass.emit (node:events:517:28) at DeviceClass.attributeUpdate (/opt/iobroker/node_modules/iobroker.miio/build/lib/Devices/device.js:169:14) at DeviceClass.propertyUpdated (/opt/iobroker/node_modules/iobroker.miio/build/lib/Devices/device.js:292:22)

miio.0
2024-01-12 08:54:39.891 error unhandled promise rejection: undefined is not a valid state value

miio.0
2024-01-12 08:54:39.890 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().

Adapter uses Sentry but standard info is missing at Readme.md

This adapter uses setntry but no Sentry infomation for users is visible at Readme.md. Users should be informed about data transfer and th epossibility to disable this feature.

Please add the suggested Sentry infomation listed at https://github.com/ioBroker/plugin-sentry#how-can-i-get-my-sentry-account-as-a-developer:

**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](https://github.com/ioBroker/plugin-sentry#plugin-sentry)! Sentry reporting is used starting with js-controller 3.0.

Messsages in Log File

Every sync with the cloud I get this information in the log:

2022-11-14 23:22:13.915  - info: mihome-cloud.0 (182947) undefined is not a valid state value for id "mihome-cloud.0.63722155.remote.time-watermark"
2022-11-14 23:22:20.089  - info: mihome-cloud.0 (182947) undefined is not a valid state value for id "mihome-cloud.0.78328901.remote.guard-mode"
2022-11-14 23:22:20.089  - info: mihome-cloud.0 (182947) undefined is not a valid state value for id "mihome-cloud.0.78328901.remote.on"
2022-11-14 23:22:25.189  - info: mihome-cloud.0 (182947) Error getting  for Wassersensor (lumi.158d0002150d0a) with {"type":3,"accessKey":"IOSKeyDeleted","params":[]}
2022-11-14 23:22:25.189  - info: mihome-cloud.0 (182947) {"code":-8,"message":"params is invalid","result":null}
2022-11-14 23:22:30.628  - info: mihome-cloud.0 (182947) Error getting  for Schalter (lumi.158d000201afb5) with {"type":3,"accessKey":"IOSKeyDeleted","params":[]}
2022-11-14 23:22:30.629  - info: mihome-cloud.0 (182947) {"code":-8,"message":"params is invalid","result":null}
2022-11-14 23:22:31.938  - info: mihome-cloud.0 (182947) Error getting  for Wassersensor (lumi.158d00021126f7) with {"type":3,"accessKey":"IOSKeyDeleted","params":[]}
2022-11-14 23:22:31.938  - info: mihome-cloud.0 (182947) {"code":-8,"message":"params is invalid","result":null}
2022-11-14 23:22:34.624  - info: mihome-cloud.0 (182947) Error getting Status of the device via Plugin for Klima WZ (blt.3.rauh1qas4400) with {"id":0,"method":"nnerF","accessKey":"IOSKeyDeleted","params":[]}
2022-11-14 23:22:34.625  - info: mihome-cloud.0 (182947) {"code":-1,"message":"bluetooth device does not support sending rpc"}
2022-11-14 23:22:46.184  - info: mihome-cloud.0 (182947) Error getting Status of the device via Plugin for Klima SZ (blt.3.raujllfo4000) with {"id":0,"method":"nnerF","accessKey":"IOSKeyDeleted","params":[]}
2022-11-14 23:22:46.184  - info: mihome-cloud.0 (182947) {"code":-1,"message":"bluetooth device does not support sending rpc"}

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.