Git Product home page Git Product logo

iobroker.meross's Introduction

Logo

ioBroker.meross

Number of Installations Number of Installations NPM version

Test and Release Translation status Downloads

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

Disclaimer

All product and company names or logos are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them or any associated subsidiaries! This personal project is maintained in spare time and has no business goal. MEROSS is a trademark of Chengdu Meross Technology Co., Ltd.

Description

This adapter allows to control Meross devices by connecting to the Meross cloud servers.

You need to provide your Cloud login credentials. The adapter connects to your cloud account and subscribe to all device data via MQTT. Because of this the devices need to be connected to their cloud. Currently no way is known to control the devices locally.

One Adapter instance will show all devices from one Meross Cloud account and allows to control them.

Note when using MFA

The adapter allows to enter the current MFA code in the settings. Please be aware that a code is only valid 30s, so enter and save fast :-)

The adapter tries to remember the token but this token runs out after some time! So when using MFA this means that no new login can be done when the adapter is restarted because the token is invalid and the MFA code too! In this case the adapter will stay offline until you enter a new MFA code.

Known working devices

All devices should work from my current knowledge. But please check the logs or report any feature or new devices types that are not creating states (new device types needs to be added manually by me, so an issue is important).

How to report issues and feature requests

Please use GitHub issues for this.

Best is to set the adapter to Debug log mode (Instances -> Expert mode -> Column Log level). Then please get the logfile from disk (subdirectory "log" in ioBroker installation directory and not from Admin because Admin cuts the lines). If you do not like providing it in GitHub issue you can also send it to me via email ([email protected]). Please add a reference to the relevant GitHub issue AND also describe what I see in the log at which time.

Changelog

1.17.0 (2023-12-30)

  • (Apollon77) Adjust Signin API and add support for MFA
  • (Apollon77) Store login token and try to reuse it for reconnections, but also do not log out anymore
  • (Apollon77) Add support for DoorWindow Sensor MS200HK

1.16.1 (2023-11-27)

  • (Apollon77) Fixes initial Temperature/Humidity/Voltage values of MS100 sensors

1.16.0 (2023-11-25)

  • IMPORTANT: Node.js 16.x or higher is required
  • (Apollon77) Prevented crash case reported by Sentry

1.15.1 (2023-05-15)

  • (Apollon77) Fix an issue when committing devices delayed

1.15.0 (2023-01-03)

  • (Apollon77) Add support for MAP100 air purifier
  • (Apollon77) Add Energy Consumption states

1.14.0 (2022-08-12)

  • (Apollon77) Add Smoke Sensor

1.13.0 (2022-07-12)

  • (Apollon77) Add new option to prevent the Cloud communication fallback when the device is not available locally for data queries (enabled by default).

1.12.2 (2022-06-27)

  • (Apollon7) prevent crash case reported by Sentry

1.12.1 (2022-06-27)

  • (Apollon7) prevent crash case reported by Sentry

1.12.0 (2022-06-24)

  • (Apollon77) Add new state to allow controlling whether to connect locally first or not for each device (but global setting takes precedence if set there to never use local connection!)
  • (Apollon77) Detect reconnection issues to Meross Cloud and try to handle them better

1.11.0 (2022-06-02)

  • (Apollon77) Add online status configuration to show online status in Admin UI
  • (Apollon77) Optimize device initialization to make sure it finishes also whe not all devices are initialized successfully

1.10.5 (2022-04-14)

  • (Apollon77) Adjust to recent API changes from Meross services

1.10.4 (2022-03-15)

  • (Apollon77) Add battery value for ms100 devices in hub if supported

1.10.3 (2022-03-11)

  • (Apollon77) Fix switch state for thermostats

1.10.2 (2022-02-19)

  • (Apollon77) Correctly set the garageDoorWorking flag after starting a control action

1.10.1 (2022-01-26)

  • (Apollon77) Fix pot. crash case

1.10.0 (2022-01-20)

  • (Apollon77) Optimize Meross Communication to first try to communicate with the device locally before sending data to MQTT - enabled by default, you can disable it in settings!
  • (Apollon77) Optimize Meross Communication by using only one MQTT connection instead of one per device when cloud is used
  • (Apollon77) Add new state "disabled" to ignore connection error of a device; reconnections are still tried, but no error are logged if not successful
  • (Apollon77) Add support for Online status reports from MTS100 hub devices
  • (Apollon77) Automatically logout from meross cloud on adapter end; next start will do a new Login
  • (Apollon77) Automatically delete old devices if no longer existing (when js-controller >=2.2)
  • (Apollon77) Optimize MTS200 handling

1.8.0 (2022-01-05)

  • (Apollon77) Add support for MTS200 Wifi Thermostat

1.7.1 (2021-11-13)

  • (Apollon77) Allow to enter passwords with more than 15 characters

1.7.0 (2021-11-13)

  • (Apollon77) Add support for MTS150 Thermostats
  • (Apollon77) Add support for MRS100 RollerShutter devices

1.6.3 (2021-06-04)

  • (Apollon77) Update translations

1.6.2 (2021-05-07)

  • (Apollon77) optimize for js-controller 3.3

1.6.1 (2021-04-23)

  • (Apollon77) prevent crash case (Sentry IOBROKER-MEROSS-Z)

1.6.0 (2021-04-18)

  • (Apollon77) add MOD100 Diffuser Spray device

1.5.1 (2020-12-05)

  • (Apollon77) generate an unique uuid for each connection, fixes the "Server not available"

1.5.0 (2020-06-25)

  • (Apollon77) Prevent crash cases (Sentry IOBROKER-MEROSS-G, IOBROKER-MEROSS-F)
  • (Apollon77) Add warning about poll interval and cloud deactivation and reset poll interval to 30s for now

1.4.1 (2020-06-12)

  • (Apollon77) Fix Admin finally

1.4.0 (2020-06-12)

  • (Apollon77) Fix Admin
  • (Apollon77) Remove the automatic cutting of passwords to 15 characters, but log info message

1.3.13 (2020.04.12)

  • (Apollon77) add auto decryption handling with js-controller 3.0
  • (Apollon77) update meross library to prevent some crash cases

1.3.12 (2020.03.08)

  • (Apollon77) update dependencies

1.3.11 (2020.02.05)

  • (Apollon77) optimize error handling
  • (Apollon77) Switch Sentry to iobroker own instance hosted in germany

1.3.9 (2019.12.18)

  • (Apollon77) Prevent some error cases on disconnects

1.3.8 (2019.12.07)

  • (Apollon77) update dependencies

1.3.7 (2019.12.01)

  • (Apollon77) Prevent some error cases on disconnects

1.3.6 (2019.11.28)

  • (Apollon77) Prevent some error cases on disconnects

1.3.5 (2019.11.28)

  • (Apollon77) Prevent some error cases on disconnects

1.3.4 (2019.11.26)

  • (Apollon77) Add Temperature/Humidity support for MTS100

1.3.1 (2019.11.25)

  • (Apollon77) Add names to hub sub devices

1.3.0 (2019.11.25)

  • (Apollon77) Add msg100 with Garage Door Reed contact
  • (Apollon77) Add reconnection handling
  • (Apollon77) Add light support (e.g. MSL120 RGB bulb)
  • (Apollon77) Add units and roles for electricity
  • (Apollon77) Add support for MSXH0 (Air Purifyer)
  • (Apollon77) Add support for Hub and Thermostates
  • (Apollon77) Allow to control DND mode (LED) - be aware then if controlled via meross app it my get out of sync!
  • (Apollon77) Integrate sentry.io for automated error/exception reporting
  • (Apollon77) Add support for mts100v3
  • (Apollon77) add Compact mode
  • (Apollon77) add control option for (rgb) lights

1.0.0 (2018.12.16)

  • (Apollon77) finalize and move to 1.0.0

0.4.1 (2018.11.26)

  • (Apollon77) finalize version and allow electricity polling interval to be configured

0.3.0 (2018.11.16)

  • (Apollon77) add support for mss310 devices

0.1.0 (2018.11.14)

  • (Apollon77) First release to support ToggleX devices

License

The MIT License (MIT)

Copyright (c) 2018-2023 Apollon77 [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.meross's People

Contributors

apollon77 avatar dependabot-preview[bot] avatar dependabot[bot] avatar germanbluefox avatar greenkeeper[bot] avatar johnnybyzhang avatar ldittmar81 avatar mcm1957 avatar medjaiiii avatar unclesamswiss avatar

Stargazers

 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

iobroker.meross's Issues

No reconnect after network loss

After network loss there is no reconnect of the adapter.
The connection status is "false" and the adapter is yellow.

After manual restart of the adapter all is fine.
A watchdog of the connection status should be implemented and the adapter should do an automatic restart.

Check and Add Schedules (devices that have it incl mts100)

Hub New: Schedule with Temperatures

meross.0	2019-09-09 22:14:05.153	debug	Device Raw: 1811066942862429086034298f17ccfd - data: {"header":{"messageId":"e587c7af28ae2a84533297fe9e086f35","namespace":"Appliance.Hub.Mts100.ScheduleB","method":"PUSH","payloadVersion":1,"from":"/
meross.0	2019-09-09 22:14:05.153	info	Please send full line from logfile on disk to developer
meross.0	2019-09-09 22:14:05.153	info	Received unknown data Appliance.Hub.Mts100.ScheduleB: {"schedule":[{"id":"01001D55","tue":[[315,200],[765,250],[240,220],[120,200]]}]}
meross.0	2019-09-09 22:14:05.152	debug	Device: 1811066942862429086034298f17ccfd Appliance.Hub.Mts100.ScheduleB - data: {"schedule":[{"id":"01001D55","tue":[[315,200],[765,250],[240,220],[120,200]]}]}
meross.0	2019-09-09 22:14:04.104	debug	Device Raw: 1811066942862429086034298f17ccfd - data: {"header":{"messageId":"65909e808a2d2910cc0429ed0b6bf8f8","namespace":"Appliance.Hub.Mts100.ScheduleB","method":"PUSH","payloadVersion":1,"from":"/
meross.0	2019-09-09 22:14:04.104	info	Please send full line from logfile on disk to developer
meross.0	2019-09-09 22:14:04.104	info	Received unknown data Appliance.Hub.Mts100.ScheduleB: {"schedule":[{"id":"01001D55","tue":[[315,200],[765,250],[240,220],[120,200]]}]}
meross.0	2019-09-09 22:14:04.104	debug	Device: 1811066942862429086034298f17ccfd Appliance.Hub.Mts100.ScheduleB - data: {"schedule":[{"id":"01001D55","tue":[[315,200],[765,250],[240,220],[120,200]]}]}
meross.0	2019-09-09 22:11:01.577	debug	Device Raw: 1811066942862429086034298f17ccfd - data: {"header":{"messageId":"a8d87b59c5db01d0cb6c6274f835fdff","namespace":"Appliance.Hub.Mts100.ScheduleB","method":"PUSH","payloadVersion":1,"from":"/
meross.0	2019-09-09 22:11:01.577	info	Please send full line from logfile on disk to developer
meross.0	2019-09-09 22:11:01.577	info	Received unknown data Appliance.Hub.Mts100.ScheduleB: {"schedule":[{"id":"01001D55","wed":[[450,200],[630,185],[240,220],[120,200]]}]}
meross.0	2019-09-09 22:11:01.576	debug	Device: 1811066942862429086034298f17ccfd Appliance.Hub.Mts100.ScheduleB - data: {"schedule":[{"id":"01001D55","wed":[[450,200],[630,185],[240,220],[120,200]]}]}
meross.0	2019-09-09 22:07:59.981	debug	Device Raw: 1811066942862429086034298f17ccfd - data: {"header":{"messageId":"18677b0621e94aa42c74aafa3ab70e2a","namespace":"Appliance.Hub.Mts100.ScheduleB","method":"PUSH","payloadVersion":1,"from":"/
meross.0	2019-09-09 22:07:59.981	info	Please send full line from logfile on disk to developer
meross.0	2019-09-09 22:07:59.980	info	Received unknown data Appliance.Hub.Mts100.ScheduleB: {"schedule":[{"id":"01001D55","mon":[[450,200],[630,180],[240,220],[120,200]]}]}
meross.0	2019-09-09 22:07:59.980	debug	Device: 1811066942862429086034298f17ccfd Appliance.Hub.Mts100.ScheduleB - data: {"schedule":[{"id":"01001D55","mon":[[450,200],[630,180],[240,220],[120,200]]}]}

An in-range update of @sentry/node is breaking the build 🚨

The dependency @sentry/node was updated from 5.12.1 to 5.12.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@sentry/node is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).
  • continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Release Notes for 5.12.2
  • [apm] ref: Check if Tracing integration is enabled before dropping transaction
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

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

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

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

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

An in-range update of @sentry/node is breaking the build 🚨

The dependency @sentry/node was updated from 5.12.2 to 5.12.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@sentry/node is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).
  • continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Release Notes for 5.12.3
  • [apm] fix: Remove undefined keys from trace.context
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @sentry/integrations is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The dependency @sentry/integrations was updated from 5.14.2 to 5.15.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@sentry/integrations is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 5.15.0
  • [apm] fix: Sampling of traces work now only depending on the client option tracesSampleRate (#2500)
  • [apm] fix: Remove internal forceNoChild parameter from hub.startSpan (#2500)
  • [apm] fix: Made constructor of Span internal, only use hub.startSpan (#2500)
  • [apm] ref: Remove status from tags in transaction (#2497)
  • [browser] fix: Respect breadcrumbs sentry:false option (#2499)
  • [node] ref: Skip body parsing for GET/HEAD requests (#2504)
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of meross-cloud is breaking the build 🚨

The dependency meross-cloud was updated from 1.3.1 to 1.3.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

meross-cloud is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
  • continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 1 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Server nicht verfügbar

Hallo Apollon,
erstmal vielen herzlichen Dank für deine großartige Arbeit die du immer wieder an den Tag legst.
Leider hat sich bei mir jetzt ein Fehler eingeschlichen den ich bisher nicht lösen konnte. Ich hab nun bereits schon einiges probiert... den Stecker MSS310 aus meiner Meross App herausgelöscht und wieder neu eingebunden, einen neuen Account angelgt. Adapter in ioBroker mehrfach neuinstalliert aber leider alles ohne Erfolg.

Das Problem ist: Es meldet das der Server nicht verfügbar sei. Wie aber aus dem Log herauszulesen ist wird schon eine Verbindung zum Server hergestellt, nur zum Stecker MSS310 sei keine Verbindung möglich.

Hier mal der LOG / DEBUG: - Achtung von Unten nach Oben zu lesen :)

meross.0 2020-06-15 05:16:56.437 info (21973) Device: 19011848516887251h0334298f1a2b11 closed: null
meross.0 2020-06-15 05:16:56.434 info (21973) Device: 19011848516887251h0334298f1a2b11 error: Error: Connection refused: Server unavailable
meross.0 2020-06-15 05:16:56.265 info (21973) Device: 19011848516887251h0334298f1a2b11 reconnected
meross.0 2020-06-15 05:16:51.265 info (21973) Device: 19011848516887251h0334298f1a2b11 closed: null
meross.0 2020-06-15 05:16:51.261 info (21973) Device: 19011848516887251h0334298f1a2b11 error: Error: Connection refused: Server unavailable
meross.0 2020-06-15 05:16:51.088 info (21973) Device: 19011848516887251h0334298f1a2b11 reconnected
meross.0 2020-06-15 05:16:46.087 info (21973) Device: 19011848516887251h0334298f1a2b11 closed: null
meross.0 2020-06-15 05:16:46.083 info (21973) Device: 19011848516887251h0334298f1a2b11 error: Error: Connection refused: Server unavailable
meross.0 2020-06-15 05:16:45.863 info (21973) Device: 19011848516887251h0334298f1a2b11 reconnected
meross.0 2020-06-15 05:16:40.863 info (21973) Device: 19011848516887251h0334298f1a2b11 closed: null
meross.0 2020-06-15 05:16:40.857 info (21973) Device: 19011848516887251h0334298f1a2b11 error: Error: Connection refused: Server unavailable
meross.0 2020-06-15 05:16:40.666 info (21973) Device: 19011848516887251h0334298f1a2b11 reconnected
meross.0 2020-06-15 05:16:35.665 info (21973) Device: 19011848516887251h0334298f1a2b11 closed: null
meross.0 2020-06-15 05:16:35.660 info (21973) Device: 19011848516887251h0334298f1a2b11 error: Error: Connection refused: Server unavailable
meross.0 2020-06-15 05:16:35.482 info (21973) Device: 19011848516887251h0334298f1a2b11 reconnected
meross.0 2020-06-15 05:16:30.481 info (21973) Device: 19011848516887251h0334298f1a2b11 closed: null
meross.0 2020-06-15 05:16:30.477 info (21973) Device: 19011848516887251h0334298f1a2b11 error: Error: Connection refused: Server unavailable
meross.0 2020-06-15 05:16:30.235 debug (21973) {"uuid":"19011848516887251h0334298f1a2b11","onlineStatus":1,"devName":"Waschmaschine","devIconId":"device024","bindTime":1591930951,"deviceType":"mss310","subType":"eu","channels":[{}],"region
meross.0 2020-06-15 05:16:30.234 info (21973) Device 19011848516887251h0334298f1a2b11 initialized
meross.0 2020-06-15 05:16:30.231 debug (21973) HTTP-Response OK: {"apiStatus":0,"sysStatus":0,"data":[{"uuid":"19011848516887251h0334298f1a2b11","onlineStatus":1,"devName":"Waschmaschine","devIconId":"device024","bindTime":1591930951,"devi
meross.0 2020-06-15 05:16:30.087 debug (21973) HTTP-Call: {"url":"https://iot.meross.com/v1/Device/devList","method":"POST","headers":{"Authorization":"Basic 0a6e86182d6aa4d7ba9ecc70bba06a7702ade9639459f5e5b2425ea73e4e002c","vender":"Meros
meross.0 2020-06-15 05:16:30.086 debug (21973) HTTP-Response OK: {"apiStatus":0,"sysStatus":0,"data":{"token":"0a6e86182d6aa4d7ba9ecc70bba06a7702ade9639459f5e5b2425ea73e4e002c","key":"b00bcf513cd85708ad72ebd04aaa6cf6","userid":"651885","em
meross.0 2020-06-15 05:16:29.827 debug (21973) connected set to false
meross.0 2020-06-15 05:16:29.738 debug (21973) HTTP-Call: {"url":"https://iot.meross.com/v1/Auth/Login","method":"POST","headers":{"Authorization":"Basic ","vender":"Meross","AppVersion":"1.3.0","AppLanguage":"EN","User-Agent":"okhttp/3.6.
meross.0 2020-06-15 05:16:29.631 info (21973) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.meross, node: v10.21.0, js-controller: 3.1.5
meross.0 2020-06-15 05:16:29.450 debug (21973) Plugin sentry Initialize Plugin (enabled=true)

PS: Der Verbindungsaufbau wird die ganze Zeit weiterversucht.

Vielleicht können Sie mir bitte helfen?
Vielen Dank schon mal!

Auswertung Reedkontakt Garagentoröffner

Könnte man neber dem Switch-State zusätzlich noch den Reedstatus mit in den Adapter aufnehmen? Das wäre eine Super Geschichte...
`

meross.0 2019-06-06 18:55:42.433 info Please send full line from logfile on disk to developer
meross.0 2019-06-06 18:55:42.417 info Received unknown data Appliance.GarageDoor.State: {"state":[{"channel":0,"open":1,"lmTime":1559840331}]}
meross.0 2019-06-06 18:55:28.372 info Please send full line from logfile on disk to developer
meross.0 2019-06-06 18:55:28.372 info Received unknown data Appliance.GarageDoor.State: {"state":[{"channel":0,"open":0,"lmTime":1559840317}]}
meross.0 2019-06-06 18:55:12.308 info Please send full line from logfile on disk to developer
meross.0 2019-06-06 18:55:12.308 info Received unknown data Appliance.GarageDoor.State: {"state":[{"channel":0,"open":1,"lmTime":1559840301}]}
meross.0 2019-06-06 18:54:57.230 info Please send full line from logfile on disk to developer
meross.0 2019-06-06 18:54:57.230 info Received unknown data Appliance.GarageDoor.State: {"state":[{"channel":0,"open":0,"lmTime":1559840286}]}
meross.0 2019-06-06 18:54:50.085 info Please send full line from logfile on disk to developer
meross.0 2019-06-06 18:54:50.069 info Received unknown data Appliance.GarageDoor.State: {"state":[{"channel":0,"open":1,"lmTime":1559840279}]}

`

meross.0 Received unknown data Appliance.Control.ConsumptionX

Das ist mehrmals heute Nacht im Log aufgetaucht :

2018-12-09 03:31:02.093 - info: meross.0 Please send full line from logfile on disk to developer

2018-12-09 03:31:02.092 - info: meross.0 Received unknown data Appliance.Control.ConsumptionX: {"consumptionx":[{"date":"2018-11-27","time":1543363018,"value":199},{"date":"2018-11-28","time":1543448954,"value":186},{"date":"2018-11-29","time":1543535129,"value":192},{"date":"2018-11-30","time":1543621183,"value":186},{"date":"2018-12-01","time":1543707720,"value":193},{"date":"2018-12-02","time":1543793895,"value":204},{"date":"2018-12-03","time":1543881511,"value":188},{"date":"2018-12-04","time":1543967205,"value":186},{"date":"2018-12-05","time":1544053381,"value":190},{"date":"2018-12-06","time":1544140278,"value":192},{"date":"2018-12-07","time":1544226453,"value":231},{"date":"2018-12-08","time":1544313229,"value":254},{"date":"2018-12-09","time":1544321751,"value":192},{"date":"2018-11-10","time":1541893212,"value":186},{"date":"2018-11-11","time":1541979615,"value":186},{"date":"2018-11-12","time":1542067169,"value":186},{"date":"2018-11-13","time":1542153572,"value":185},{"date":"2018-11-14","time":1542239375,"value":185},{"date":"2018-11-15","time":1542325657,"value":187},{"date":"2018-11-16","time":1542411940,"value":205},{"date":"2018-11-17","time":1542498882,"value":190},{"date":"2018-11-18","time":1542585165,"value":188},{"date":"2018-11-19","time":1542671483,"value":191},{"date":"2018-11-20","time":1542757765,"value":348},{"date":"2018-11-21","time":1542843928,"value":274},{"date":"2018-11-22","time":1542930100,"value":265},{"date":"2018-11-23","time":1543016517,"value":192},{"date":"2018-11-24","time":1543102931,"value":185},{"date":"2018-11-25","time":1543189466,"value":185},{"date":"2018-11-26","time":1543275761,"value":184}]}

Compatibility check and testing for Node.js 14 and 16

Dear Adapter develop,

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

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

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

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

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

Please close the issue after you checked it.

Thank you very much for your support!

Meross Steckdosen de/aktivieren

Hallo Apollon,

Ich habe einige Meross Steckdosen die ich für Weihnachtsbeleuchtung verwende (10Stück) die Weihnachtsbeleuchtung ist aber abgebaut, da Weihnachten ja schon vorbei ist. Nun werden die Meross Steckdosen nicht mehr erreicht, was klar ist und meine logs gehen über mit Fehlermeldungen:

meross.0 2020-03-21 16:21:56.668 warn Can not get Abilities for Device 1811303935030425182134298f187dde: Error: Timeout / undefined

Gibt es eine Möglichkeit diese Meldungen, bzw. die Steckdosen als deaktiviert zu flaggen ?

thx u. lg Rudi

An in-range update of mocha is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency mocha was updated from 7.1.0 to 7.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v7.1.1

7.1.1 / 2020-03-18

🔒 Security Fixes

  • #4204: Update dependencies mkdirp, yargs-parser and yargs (@juergba)

🐛 Fixes

📖 Documentation

Commits

The new version differs by 6 commits.

  • 7c09e63 Release v7.1.1
  • 7599535 update CHANGELOG for v7.1.1 [ci skip]
  • 3bf650c security: update mkdirp, yargs, yargs-parser (#4204)
  • e1389ef Fix: runner listening to 'start' and 'end' events (#3660)
  • 9cbb6f6 upgrade assetgraph-builder
  • 4dc3cd1 docs: show netlify badge on footer (#4190)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of meross-cloud is breaking the build 🚨

The dependency meross-cloud was updated from 1.0.0 to 1.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

meross-cloud is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Think about to fix the issues found by adapter checker

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

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

  • [E154] common.dependencies must contain{"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
  • [E140] width and height of logo are not equal

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Add Option to control the LED

I would like to have an option, to control the LED.
I want to be able to control the LED of my meross over iobroker.
Example: turn off the LED autmaticly at night, so i dont have to go in the app for it.

Meross Smart Hub (MSH300) bzw. Smart ThermoStat (MTS100)

Wie gewünscht hier das Log vom Start des Adapters:

2019-02-03 00:24:10.673 - debug: meross.0 statesDB connected
2019-02-03 00:24:10.814 - info: meross.0 starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.meross, node: v8.15.0
2019-02-03 00:24:11.174 - debug: meross.0 connected set to false
2019-02-03 00:24:11.915 - info: meross.0 Device 1811068309697929086034298f17cdb2 initialized
2019-02-03 00:24:11.916 - debug: meross.0 {"uuid":"1811068309697929086034298f17cdb2","onlineStatus":1,"devName":"Smart Hub","devIconId":"device028_eu","bindTime":1548770143,"deviceType":"msh300","subType":"un","channels":[{}],"region":"eu","fmwareVersion":"2.1.7","hdwareVersion":"2.0.0","userDevIcon":"","iconType":1,"skillNumber":"","domain":"eu-iot.meross.com","reservedDomain":"eu-smart.meross.com"}
2019-02-03 00:24:12.093 - info: meross.0 Device 1812186040406729088534298f19e309 initialized
2019-02-03 00:24:12.093 - debug: meross.0 {"uuid":"1812186040406729088534298f19e309","onlineStatus":1,"devName":"Küche Licht","devIconId":"device028_eu","bindTime":1548448441,"deviceType":"mss510h","subType":"eu","channels":[{}],"region":"eu","fmwareVersion":"3.1.1","hdwareVersion":"3.0.0","userDevIcon":"","iconType":1,"skillNumber":"","domain":"eu-iot.meross.com","reservedDomain":"eu-smart.meross.com"}
2019-02-03 00:24:12.512 - info: meross.0 Device: 1811068309697929086034298f17cdb2 connected
2019-02-03 00:24:12.530 - info: meross.0 Device: 1812186040406729088534298f19e309 connected
2019-02-03 00:24:12.536 - debug: meross.0 connected set to true
2019-02-03 00:24:12.606 - debug: meross.0 1811068309697929086034298f17cdb2 Abilities: {"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"Appliance.System.All":{},"Appliance.System.Hardware":{},"Appliance.System.Firmware":{},"Appliance.System.Debug":{},"Appliance.System.Online":{},"Appliance.System.Time":{},"Appliance.System.Ability":{},"Appliance.System.Runtime":{},"Appliance.System.Report":{},"Appliance.System.Position":{},"Appliance.Control.Multiple":{"maxCmdNum":5},"Appliance.Control.Bind":{},"Appliance.Control.Unbind":{},"Appliance.Control.Upgrade":{},"Appliance.Digest.Hub":{},"Appliance.Hub.Bind":{},"Appliance.Hub.Unbind":{},"Appliance.Hub.Online":{},"Appliance.Hub.ToggleX":{},"Appliance.Hub.Exception":{},"Appliance.Hub.Mts100.All":{},"Appliance.Hub.Mts100.TimeSync":{},"Appliance.Hub.Mts100.Mode":{},"Appliance.Hub.Mts100.Temperature":{},"Appliance.Hub.Mts100.Schedule":{"scheduleUnitTime":30}}}
2019-02-03 00:24:12.609 - debug: meross.0 Device Raw: 1811068309697929086034298f17cdb2 - data: {"header":{"messageId":"322c7425f11648f830d7cf824b2a8aca","namespace":"Appliance.System.Ability","method":"GETACK","payloadVersion":1,"from":"/appliance/1811068309697929086034298f17cdb2/publish","timestamp":1549149852,"timestampMs":144,"sign":"52b1a4d6a78864bc3d2018b6f5dde3ac"},"payload":{"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"Appliance.System.All":{},"Appliance.System.Hardware":{},"Appliance.System.Firmware":{},"Appliance.System.Debug":{},"Appliance.System.Online":{},"Appliance.System.Time":{},"Appliance.System.Ability":{},"Appliance.System.Runtime":{},"Appliance.System.Report":{},"Appliance.System.Position":{},"Appliance.Control.Multiple":{"maxCmdNum":5},"Appliance.Control.Bind":{},"Appliance.Control.Unbind":{},"Appliance.Control.Upgrade":{},"Appliance.Digest.Hub":{},"Appliance.Hub.Bind":{},"Appliance.Hub.Unbind":{},"Appliance.Hub.Online":{},"Appliance.Hub.ToggleX":{},"Appliance.Hub.Exception":{},"Appliance.Hub.Mts100.All":{},"Appliance.Hub.Mts100.TimeSync":{},"Appliance.Hub.Mts100.Mode":{},"Appliance.Hub.Mts100.Temperature":{},"Appliance.Hub.Mts100.Schedule":{"scheduleUnitTime":30}}}}
2019-02-03 00:24:12.747 - debug: meross.0 1812186040406729088534298f19e309 Abilities: {"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"Appliance.System.All":{},"Appliance.System.Hardware":{},"Appliance.System.Firmware":{},"Appliance.System.Debug":{},"Appliance.System.Online":{},"Appliance.System.Time":{},"Appliance.System.Ability":{},"Appliance.System.Runtime":{},"Appliance.System.Report":{},"Appliance.System.Position":{},"Appliance.System.DNDMode":{},"Appliance.Control.Multiple":{"maxCmdNum":5},"Appliance.Control.ToggleX":{},"Appliance.Control.TimerX":{"sunOffsetSupport":1},"Appliance.Control.TriggerX":{},"Appliance.Control.Bind":{},"Appliance.Control.Unbind":{},"Appliance.Control.Upgrade":{},"Appliance.Digest.TriggerX":{},"Appliance.Digest.TimerX":{}}}
2019-02-03 00:24:12.748 - debug: meross.0 Device Raw: 1812186040406729088534298f19e309 - data: {"header":{"messageId":"07fc3b3f5caa110e78d1050e40d42901","namespace":"Appliance.System.Ability","method":"GETACK","payloadVersion":1,"from":"/appliance/1812186040406729088534298f19e309/publish","timestamp":1549149852,"timestampMs":126,"sign":"f489213dc8950ae96b6a375acb7458d2"},"payload":{"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"Appliance.System.All":{},"Appliance.System.Hardware":{},"Appliance.System.Firmware":{},"Appliance.System.Debug":{},"Appliance.System.Online":{},"Appliance.System.Time":{},"Appliance.System.Ability":{},"Appliance.System.Runtime":{},"Appliance.System.Report":{},"Appliance.System.Position":{},"Appliance.System.DNDMode":{},"Appliance.Control.Multiple":{"maxCmdNum":5},"Appliance.Control.ToggleX":{},"Appliance.Control.TimerX":{"sunOffsetSupport":1},"Appliance.Control.TriggerX":{},"Appliance.Control.Bind":{},"Appliance.Control.Unbind":{},"Appliance.Control.Upgrade":{},"Appliance.Digest.TriggerX":{},"Appliance.Digest.TimerX":{}}}}
2019-02-03 00:24:12.821 - debug: meross.0 1811068309697929086034298f17cdb2 All-Data: {"all":{"system":{"hardware":{"type":"msh300","subType":"un","version":"2.0.0","chipType":"mt7682","uuid":"1811068309697929086034298f17cdb2","macAddress":"xx:xx:xx:xx:xx:xx"},"firmware":{"version":"2.1.7","compileTime":"2018/11/16 15:08:44 GMT +08:00","wifiMac":"xx:xx:xx:xx:xx:xx","innerIp":"192.168.xxx.xxx","server":"iot.meross.com","port":2001,"userId":1xxxxx},"time":{"timestamp":1549149852,"timezone":"Europe/Berlin","timeRule":[[1540688400,3600,0],[1553994000,7200,1],[1572138000,3600,0],[1585443600,7200,1],[1603587600,3600,0],[1616893200,7200,1],[1635642000,3600,0],[1648342800,7200,1],[1667091600,3600,0],[1679792400,7200,1],[1698541200,3600,0],[1711846800,7200,1],[1729990800,3600,0],[1743296400,7200,1],[1761440400,3600,0],[1774746000,7200,1],[1792890000,3600,0],[1806195600,7200,1],[1824944400,3600,0],[1837645200,7200,1]]},"online":{"status":1}},"digest":{"hub":{"hubId":52658,"mode":0,"subdevice":[{"id":"000013CD","status":1,"onoff":1,"lastActiveTime":1549149687,"mts100":{"mode":3}},{"id":"0000132D","status":1,"onoff":1,"lastActiveTime":1549149848,"mts100":{"mode":1}}]}}}}
2019-02-03 00:24:12.822 - info: meross.0 Ability Toggle/ToggleX not supported by Device 1811068309697929086034298f17cdb2: send next line from disk to developer
2019-02-03 00:24:12.822 - info: meross.0 {"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"Appliance.System.All":{},"Appliance.System.Hardware":{},"Appliance.System.Firmware":{},"Appliance.System.Debug":{},"Appliance.System.Online":{},"Appliance.System.Time":{},"Appliance.System.Ability":{},"Appliance.System.Runtime":{},"Appliance.System.Report":{},"Appliance.System.Position":{},"Appliance.Control.Multiple":{"maxCmdNum":5},"Appliance.Control.Bind":{},"Appliance.Control.Unbind":{},"Appliance.Control.Upgrade":{},"Appliance.Digest.Hub":{},"Appliance.Hub.Bind":{},"Appliance.Hub.Unbind":{},"Appliance.Hub.Online":{},"Appliance.Hub.ToggleX":{},"Appliance.Hub.Exception":{},"Appliance.Hub.Mts100.All":{},"Appliance.Hub.Mts100.TimeSync":{},"Appliance.Hub.Mts100.Mode":{},"Appliance.Hub.Mts100.Temperature":{},"Appliance.Hub.Mts100.Schedule":{"scheduleUnitTime":30}}}
2019-02-03 00:24:12.825 - debug: meross.0 Device Raw: 1811068309697929086034298f17cdb2 - data: {"header":{"messageId":"32af35fa8639247db89dde98dea6de41","namespace":"Appliance.System.All","method":"GETACK","payloadVersion":1,"from":"/appliance/1811068309697929086034298f17cdb2/publish","timestamp":1549149852,"timestampMs":230,"sign":"d92271db0069158a37f22837c1d69346"},"payload":{"all":{"system":{"hardware":{"type":"msh300","subType":"un","version":"2.0.0","chipType":"mt7682","uuid":"1811068309697929086034298f17cdb2","macAddress":"xx:xx:xx:xx:xx:xx"},"firmware":{"version":"2.1.7","compileTime":"2018/11/16 15:08:44 GMT +08:00","wifiMac":"xx:xx:xx:xx:xx:xx","innerIp":"192.168.xxx.xxx","server":"iot.meross.com","port":2001,"userId":1xxxxx},"time":{"timestamp":1549149852,"timezone":"Europe/Berlin","timeRule":[[1540688400,3600,0],[1553994000,7200,1],[1572138000,3600,0],[1585443600,7200,1],[1603587600,3600,0],[1616893200,7200,1],[1635642000,3600,0],[1648342800,7200,1],[1667091600,3600,0],[1679792400,7200,1],[1698541200,3600,0],[1711846800,7200,1],[1729990800,3600,0],[1743296400,7200,1],[1761440400,3600,0],[1774746000,7200,1],[1792890000,3600,0],[1806195600,7200,1],[1824944400,3600,0],[1837645200,7200,1]]},"online":{"status":1}},"digest":{"hub":{"hubId":52658,"mode":0,"subdevice":[{"id":"000013CD","status":1,"onoff":1,"lastActiveTime":1549149687,"mts100":{"mode":3}},{"id":"0000132D","status":1,"onoff":1,"lastActiveTime":1549149848,"mts100":{"mode":1}}]}}}}}
2019-02-03 00:24:13.011 - debug: meross.0 1812186040406729088534298f19e309 All-Data: {"all":{"system":{"hardware":{"type":"mss510h","subType":"us","version":"3.0.0","chipType":"mt7682","uuid":"1812186040406729088534298f19e309","macAddress":"xx:xx:xx:xx:xx:xx"},"firmware":{"version":"3.1.1","compileTime":"2018/12/13 16:37:11 GMT +08:00","wifiMac":"xx:xx:xx:xx:xx:xx","innerIp":"192.168.xxx.xxx","server":"iot.meross.com","port":2001,"userId":1xxxxx},"time":{"timestamp":1549149852,"timezone":"Europe/Berlin","timeRule":[[1540688400,3600,0],[1553994000,7200,1],[1572138000,3600,0],[1585443600,7200,1],[1603587600,3600,0],[1616893200,7200,1],[1635642000,3600,0],[1648342800,7200,1],[1667091600,3600,0],[1679792400,7200,1],[1698541200,3600,0],[1711846800,7200,1],[1729990800,3600,0],[1743296400,7200,1],[1761440400,3600,0],[1774746000,7200,1],[1792890000,3600,0],[1806195600,7200,1],[1824944400,3600,0],[1837645200,7200,1]]},"online":{"status":1}},"digest":{"togglex":[{"channel":0,"onoff":0,"lmTime":1549146823}],"triggerx":[],"timerx":[]}}}
2019-02-03 00:24:13.017 - debug: meross.0 Device Raw: 1812186040406729088534298f19e309 - data: {"header":{"messageId":"43e9682a105497cfa7d70aad2011c72a","namespace":"Appliance.System.All","method":"GETACK","payloadVersion":1,"from":"/appliance/1812186040406729088534298f19e309/publish","timestamp":1549149852,"timestampMs":334,"sign":"19421ca9078f2b6ed34f54b14894529a"},"payload":{"all":{"system":{"hardware":{"type":"mss510h","subType":"us","version":"3.0.0","chipType":"mt7682","uuid":"1812186040406729088534298f19e309","macAddress":"34:29:8f:19:e3:09"},"firmware":{"version":"3.1.1","compileTime":"2018/12/13 16:37:11 GMT +08:00","wifiMac":"34:81:c4:bf:f2:4b","innerIp":"192.168.178.52","server":"iot.meross.com","port":2001,"userId":165277},"time":{"timestamp":1549149852,"timezone":"Europe/Berlin","timeRule":[[1540688400,3600,0],[1553994000,7200,1],[1572138000,3600,0],[1585443600,7200,1],[1603587600,3600,0],[1616893200,7200,1],[1635642000,3600,0],[1648342800,7200,1],[1667091600,3600,0],[1679792400,7200,1],[1698541200,3600,0],[1711846800,7200,1],[1729990800,3600,0],[1743296400,7200,1],[1761440400,3600,0],[1774746000,7200,1],[1792890000,3600,0],[1806195600,7200,1],[1824944400,3600,0],[1837645200,7200,1]]},"online":{"status":1}},"digest":{"togglex":[{"channel":0,"onoff":0,"lmTime":1549146823}],"triggerx":[],"timerx":[]}}}}
2019-02-03 00:24:13.620 - info: meross.0 Devices initialized
2019-02-03 00:24:13.701 - debug: meross.0 Online: {"online":{"status":1}}
2019-02-03 00:24:13.703 - debug: meross.0 Device Raw: 1811068309697929086034298f17cdb2 - data: {"header":{"messageId":"972685bc10ffa26476294591e4fbdca8","namespace":"Appliance.System.Online","method":"GETACK","payloadVersion":1,"from":"/appliance/1811068309697929086034298f17cdb2/publish","timestamp":1549149853,"timestampMs":237,"sign":"72755232acb9957f4d56893193838d93"},"payload":{"online":{"status":1}}}
2019-02-03 00:24:13.714 - debug: meross.0 stateChange meross.0.1811068309697929086034298f17cdb2.online {"val":true,"ack":true,"ts":1549149853707,"q":0,"from":"system.adapter.meross.0","lc":1549149853707}
2019-02-03 00:24:13.753 - debug: meross.0 Online: {"online":{"status":1}}
2019-02-03 00:24:13.755 - debug: meross.0 Device Raw: 1812186040406729088534298f19e309 - data: {"header":{"messageId":"53023ed075b2266c42f049269a6640bb","namespace":"Appliance.System.Online","method":"GETACK","payloadVersion":1,"from":"/appliance/1812186040406729088534298f19e309/publish","timestamp":1549149853,"timestampMs":217,"sign":"71fb41852700477c541fc63162e2e5f7"},"payload":{"online":{"status":1}}}
2019-02-03 00:24:13.762 - debug: meross.0 stateChange meross.0.1812186040406729088534298f19e309.online {"val":true,"ack":true,"ts":1549149853759,"q":0,"from":"system.adapter.meross.0","lc":1549149853759}

Meross 1.0 Adapter startet nicht

Debug Log:

meross.0 | 2019-07-17 12:14:21.190 | debug | system.adapter.admin.0: logging true
meross.0 | 2019-07-17 12:14:18.344 | debug | connected set to false
meross.0 | 2019-07-17 12:14:18.214 | info | starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.meross, node: v8.16.0
meross.0 | 2019-07-17 12:14:18.093 | debug | statesDB connected
meross.0 | 2019-07-17 12:14:18.025 | debug | objectDB connected

node.js 8.16.0 installiert

MSL120 nicht bedienbar

Hi,

ich habe die MSL120 und unter der 1.0.0 konnte ich zumindest an und aus schalten.
Seit der 1.1.2 funktioniert das nicht mehr und der Adapter kommt auch nicht mehr auf grün.
Folgende Fehlermeldung wird dann im Log angezeigt.

host.ioBroker-RasPi 2019-08-27 18:31:19.722 info Restart adapter system.adapter.meross.0 because enabled
host.ioBroker-RasPi 2019-08-27 18:31:19.721 error instance system.adapter.meross.0 terminated with code 6 (uncaught exception)
host.ioBroker-RasPi 2019-08-27 18:31:19.721 error Caught by controller[0]: at doWrite (/opt/iobroker/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:428:64)
host.ioBroker-RasPi 2019-08-27 18:31:19.720 error Caught by controller[0]: at Writable.writable._write (/opt/iobroker/node_modules/mqtt/lib/client.js:294:5)
host.ioBroker-RasPi 2019-08-27 18:31:19.720 error Caught by controller[0]: at work (/opt/iobroker/node_modules/mqtt/lib/client.js:283:12)
host.ioBroker-RasPi 2019-08-27 18:31:19.720 error Caught by controller[0]: at MqttClient._handlePacket (/opt/iobroker/node_modules/mqtt/lib/client.js:351:12)
host.ioBroker-RasPi 2019-08-27 18:31:19.719 error Caught by controller[0]: at MqttClient._handlePublish (/opt/iobroker/node_modules/mqtt/lib/client.js:1162:12)
host.ioBroker-RasPi 2019-08-27 18:31:19.719 error Caught by controller[0]: at MqttClient.emit (events.js:217:7)
host.ioBroker-RasPi 2019-08-27 18:31:19.718 error Caught by controller[0]: at emitThree (events.js:136:13)
host.ioBroker-RasPi 2019-08-27 18:31:19.718 error Caught by controller[0]: at MqttClient.client.on (/opt/iobroker/node_modules/meross-cloud/index.js:239:66)
host.ioBroker-RasPi 2019-08-27 18:31:19.717 error Caught by controller[0]: at Object.device.getSystemAllData [as callback] (/opt/iobroker/node_modules/iobroker.meross/main.js:396:17)
host.ioBroker-RasPi 2019-08-27 18:31:19.717 error Caught by controller[0]: at initDeviceObjects (/opt/iobroker/node_modules/iobroker.meross/main.js:304:27)
host.ioBroker-RasPi 2019-08-27 18:31:19.716 error Caught by controller[0]: ReferenceError: val is not defined
meross.0 2019-08-27 18:31:18.676 debug connected set to false
meross.0 2019-08-27 18:31:18.675 debug connected set to false
meross.0 2019-08-27 18:31:18.674 debug connected set to false
meross.0 2019-08-27 18:31:18.669 info Device: 1812147137869029088434298f19810f closed: null
meross.0 2019-08-27 18:31:18.668 info Device: 1812011278931829087334298f1894ae closed: null
meross.0 2019-08-27 18:31:18.667 warn Exception: ReferenceError: val is not defined
meross.0 2019-08-27 18:31:18.667 error ReferenceError: val is not defined at initDeviceObjects (/opt/iobroker/node_modules/iobroker.meross/main.js:304:27) at Object.device.getSystemAllData [as callback] (/opt/iobroker/node_modules/
meross.0 2019-08-27 18:31:18.666 error uncaught exception: val is not defined
meross.0 2019-08-27 18:31:18.665 debug 1812147137869029088434298f19810f: initDeviceObjects with channels = [{}] and data = {"togglex":[{"channel":0,"onoff":0,"lmTime":1566923303}],"triggerx":[],"timerx":[],"light":{"capacity":6,"channel":0
meross.0 2019-08-27 18:31:18.664 debug 1812147137869029088434298f19810f All-Data: {"all":{"system":{"hardware":{"type":"msl120","subType":"us","version":"2.0.0","chipType":"mt7682","uuid":"1812147137869029088434298f19810f","macAddress":"34
meross.0 2019-08-27 18:31:18.430 debug Device Raw: 1812011278931829087334298f1894ae - data: {"header":{"messageId":"a140f1e2f1da66d1eccd8083acc6bce2","namespace":"Appliance.System.Ability","method":"GETACK","payloadVersion":1,"from":"/appl
meross.0 2019-08-27 18:31:18.430 debug Device Send Raw: 1812011278931829087334298f1894ae - data: {"header":{"from":"/app/222050-61bd821bb49039165a484a55f74cac9c/subscribe","messageId":"30746ed02ec6416ed691e23a2d8be8c1","method":"GET","name
meross.0 2019-08-27 18:31:18.429 debug 1812011278931829087334298f1894ae Abilities: {"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"Appliance.Sy
meross.0 2019-08-27 18:31:18.399 debug Device Raw: 1812147137869029088434298f19810f - data: {"header":{"messageId":"c02ebd28629cee2188bafde7b105370f","namespace":"Appliance.System.Ability","method":"GETACK","payloadVersion":1,"from":"/appl
meross.0 2019-08-27 18:31:18.397 debug Device Send Raw: 1812147137869029088434298f19810f - data: {"header":{"from":"/app/222050-ac991d0d4736287578bacd666b936f04/subscribe","messageId":"bb9afb18d5c455c9f5eb584c1d42cd73","method":"GET","name
meross.0 2019-08-27 18:31:18.396 debug 1812147137869029088434298f19810f Abilities: {"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"Appliance.Sy
meross.0 2019-08-27 18:31:18.276 debug Device Send Raw: 1812147137869029088434298f19810f - data: {"header":{"from":"/app/222050-ac991d0d4736287578bacd666b936f04/subscribe","messageId":"c02ebd28629cee2188bafde7b105370f","method":"GET","name
meross.0 2019-08-27 18:31:18.275 info Device: 1812147137869029088434298f19810f connected
meross.0 2019-08-27 18:31:18.215 debug connected set to true
meross.0 2019-08-27 18:31:18.211 debug Device Send Raw: 1812011278931829087334298f1894ae - data: {"header":{"from":"/app/222050-61bd821bb49039165a484a55f74cac9c/subscribe","messageId":"a140f1e2f1da66d1eccd8083acc6bce2","method":"GET","name
meross.0 2019-08-27 18:31:18.209 info Device: 1812011278931829087334298f1894ae connected
meross.0 2019-08-27 18:31:17.854 debug {"uuid":"1812011278931829087334298f1894ae","onlineStatus":1,"devName":"Schlafzimmer Licht","devIconId":"device028_eu","bindTime":1557343421,"deviceType":"mss510h","subType":"eu","channels":[{}],"regio
meross.0 2019-08-27 18:31:17.847 info Device 1812011278931829087334298f1894ae initialized
meross.0 2019-08-27 18:31:17.843 debug {"uuid":"1812147137869029088434298f19810f","onlineStatus":1,"devName":"Büro Lampe","devIconId":"device036","bindTime":1566835294,"deviceType":"msl120","subType":"eu","channels":[{}],"region":"eu","fmw
meross.0 2019-08-27 18:31:17.842 info Device 1812147137869029088434298f19810f initialized
meross.0 2019-08-27 18:31:16.771 debug connected set to false
meross.0 2019-08-27 18:31:16.653 info starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.meross, node: v8.15.0
host.ioBroker-RasPi 2019-08-27 18:31:12.198 info instance system.adapter.meross.0 started with pid 24240
host.ioBroker-RasPi 2019-08-27 18:31:12.171 info object change system.adapter.meross.0
host.ioBroker-RasPi 2019-08-27 18:31:01.204 info instance system.adapter.meross.0 terminated with code 3 (Adapter disabled or invalid config)
meross.0 2019-08-27 18:31:01.141 error adapter disabled
meross.0 2019-08-27 18:31:01.023 info States connected to redis: 127.0.0.1:6379
meross.0 2019-08-27 18:31:01.009 debug statesDB connected
meross.0 2019-08-27 18:31:00.935 debug objectDB connected
host.ioBroker-RasPi 2019-08-27 18:30:59.364 info stopInstance system.adapter.meross.0 killing pid 23763
host.ioBroker-RasPi 2019-08-27 18:30:59.363 info stopInstance system.adapter.meross.0
host.ioBroker-RasPi 2019-08-27 18:30:59.362 info "system.adapter.meross.0" disabled
host.ioBroker-RasPi 2019-08-27 18:30:59.359 info object change system.adapter.meross.0
host.ioBroker-RasPi 2019-08-27 18:30:56.717 info instance system.adapter.meross.0 started with pid 23763
host.ioBroker-RasPi 2019-08-27 18:30:56.685 info object change system.adapter.meross.0
host.ioBroker-RasPi 2019-08-27 18:30:37.893 info Restart adapter system.adapter.meross.0 because enabled

An in-range update of gulp is breaking the build 🚨

The devDependency gulp was updated from 4.0.0 to 4.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gulp is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v4.0.1

Fix

Docs

  • Fix error in ES2015 usage example (a4e8d48) - Closes #2099 #2100
  • Add temporary notice for 4.0.0 vs 3.9.1 documentation (126423a) - Closes #2121
  • Improve recipe for empty glob array (45830cf) - Closes #2122
  • Reword standard to default (b065a13)
  • Fix recipe typo (86acdea) - Closes #2156
  • Add front-matter to each file (d693e49) - Closes #2109
  • Rename "Getting Started" to "Quick Start" & update it (6a0fa00)
  • Add "Creating Tasks" documentation (21b6962)
  • Add "JavaScript and Gulpfiles" documentation (31adf07)
  • Add "Working with Files" documentation (50fafc6)
  • Add "Async Completion" documentation (ad8b568)
  • Add "Explaining Globs" documentation (f8cafa0)
  • Add "Using Plugins" documentation (233c3f9)
  • Add "Watching Files" documentation (f3f2d9f)
  • Add Table of Contents to "Getting Started" directory (a43caf2)
  • Improve & fix parts of Getting Started (84b0234)
  • Create and link-to a "docs missing" page for LINK_NEEDED references (2bd75d0)
  • Redirect users to new Getting Started guides (53e9727)
  • Temporarily reference gulp@next in Quick Start (2cecf1e)
  • Fixed a capitalization typo in a heading (3d051d8) - Closes #2242
  • Use h2 headers within Quick Start documentation (921312c) - Closes #2241
  • Fix for nested directories references (4c2b9a7)
  • Add some more cleanup for Docusaurus (6a8fd8f)
  • Temporarily point LINK_NEEDED references to documentation-missing.md (df7cdcb)
  • API documentation improvements based on feedback (0a68710)
  • Update API Table of Contents (d6dd438)
  • Add API Concepts documentation (8dd3361)
  • Add Vinyl.isCustomProp() documentation (40ee801)
  • Add Vinyl.isVinyl() documentation (25a22bf)
  • Add Vinyl documentation (fc09067)
  • Update watch() documentation (69c22f0)
  • Update tree() documentation (ebb9818)
  • Update task() documentation (b636a9c)
  • Update symlink() documentation (d580efa)
  • Update src() documentation (d95b457)
  • Update series() documentation (4169cb6)
  • Update registry() documentation (d680487)
  • Update parallel() documentation (dc3cba7)
  • Update lastRun() documentation (363df21)
  • Update dest() documentation (e447d81)
  • Split API docs into separate markdown files (a3b8ce1)
  • Fix hash link (af4bd51)
  • Replace some links in Getting Started (c433c70)
  • Remove temporary workaround for facebook/Docusaurus#257 (5c07954) - Closes facebook/Docusaurus#257
  • Added code ticks to "null" where missing (cb67319) - Closes #2243
  • Fix broken link in lastRun (d35653e)
  • Add front-matter to documentation-missing page (a553cfd)
  • Improve grammar on Concepts (01cfcc5) - Closes #2247
  • Remove spaces around
    (c960c1d)
  • Improve grammar in src (eb493a2) - Closes #2248
  • Fix formatting error (ca6ba35) - Closes #2250
  • Fix formatting of lastRun (8569f85) - Closes #2251
  • Add missing link in watch (e35bdac) - Closes #2252
  • Fix broken link in tasks (6d43750) - Closes #2253
  • Improve punctuation in tree (8e9fd70) - Closes #2254
  • Fix mistake in "Splitting a gulpfile" (96c353d) - Closes #2255
  • Remove front-matter from outdated pages (c5af6f1)
  • Fix broken link in Table of Contents (c641369) - Closes #2260
  • Update the babel dependencies to install & configuration needed (7239cf1) - Closes #2136
  • Add "What's new in 4.0" section (75ea634) - Closes #2089 #2267
  • Cleanup README for "latest" bump (24e202b) - Closes #2268
  • Revert "next" reference now that 4.0 is latest (ed27cbe)
  • Add Azure Pipelines badge (f3f0548) - Closes #2310
  • Add note about transpilation to "Splitting a Gulpfile" section (53b9037) - Closes #2311 #2312
  • Improve wording of file rename (88437f2) - Closes #2314

Upgrade

  • Update glob-watcher, gulp-cli, and undertaker dependencies & rimraf devDep (d3734d3)

Build

  • Add node 10 to CI matrices (a5eac1c)
  • Remove jscs & update eslint for code formatting rules (ad8a2f7)
  • Fix Azure comment (34a6d53) - Closes #2307
  • Add Azure Pipelines CI (b2c6c7e) - Closes #2299

Scaffold

  • Mark *.png and *.jpg as binary files to git (a010db6)
  • Update some links and license year (1027236)
  • Add tidelift configuration (49b5aca)
  • Add new expense policy (9819957)
  • Add support-bot template (9078c49)
Commits

The new version differs by 77 commits.

  • ea3bba4 Release: 4.0.1
  • d3734d3 Upgrade: Update glob-watcher, gulp-cli, and undertaker dependencies & rimraf devDep
  • 88437f2 Docs: Improve wording of file rename (#2314)
  • 53b9037 Docs: Add note about transpilation to "Splitting a Gulpfile" section (closes #2311) (#2312)
  • f3f0548 Docs: Add Azure Pipelines badge (#2310)
  • 34a6d53 Build: Fix Azure comment (#2307)
  • b2c6c7e Build: Add Azure Pipelines CI (#2299)
  • ed27cbe Docs: Revert "next" reference now that 4.0 is latest
  • 24e202b Docs: Cleanup README for "latest" bump (#2268)
  • 75ea634 Docs: Add "What's new in 4.0" section (closes #2089) (#2267)
  • 9078c49 Scaffold: Add support-bot template
  • 7239cf1 Docs: Update the babel dependencies to install & configuration needed (closes #2136)
  • c641369 Docs: Fix broken link in Table of Contents (#2260)
  • 9819957 Scaffold: Add new expense policy
  • c5af6f1 Docs: Remove front-matter from outdated pages

There are 77 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Password length

Hi there :-),

I tried to connect to the meross cloud by this adapter.
I got the following error in the log:
Meross Connection Error: Error: 1004: Add Login Token failed, code: 1004, reason:Username is not exist or password is wrong email: [email protected]

I wondered, why this happened and double-checked my password. It was the right one.
Then i checked your source code and found the following part:

// Maximum password length supported by cloud is 15 characters if (adapter.config.password.length > 15) { adapter.config.password = adapter.config.password.substring(0, 15);

I noticed that my password length is above 15. That means, that it's possible to register a password with more than 15 characters at the meross cloud.
After changing my password to the size of 15 the adapter worked fine.

Please add a error message or log entry if the password is longer than 15 characters.

Thanks,
Hamsterrennen

Benutzer lässt sich nicht speichern

Hallo Apollo.
Ich habe den Adapter Meross über die Instanz gelöscht.
Beim erneuten Installieren des Adapters ist es nicht möglich die Anmeldedaten zu speichern.
Wenn alles eingegeben wurden und ich auf Speichern oder Speichern und schließen klicke passiert nichts. Wenn ich auf Abbrechen klicken wird abgefragt ob man die Eingaben verwerfen möchte.
Unter Log kommt nur der Fehler:
(2901) Meross Connection Error: Error: 1000: Lack user

Js-Controller 3.1.4
Node.js v12.16.3
NPM6.14.4
ioBroker fix ist ausgeführt

An in-range update of meross-cloud is breaking the build 🚨

The dependency meross-cloud was updated from 1.3.0 to 1.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

meross-cloud is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
  • continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Garage Door opener MSG100 noStatus from DoorSensor

Hello i`bought the Meross MSG100 door Opener it looks good.
But i see nothing from the DoorSensor in this adapter , in the app froma meross i can see the staus from the DoorSensor
is there a way to integrate it in a Datapoint ???
wirh best regards
mikewolf

An in-range update of @sentry/node is breaking the build 🚨


🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io


The dependency @sentry/node was updated from 5.15.5 to 5.16.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@sentry/node is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for 5.16.0

If you are a @sentry/apm and did manual instrumentation using hub.startSpan please be aware of the changes we did to the API. The recommended entry point for manual instrumentation now is Sentry.startTransaction and creating child Span by calling startChild on it. We have internal workarounds in place so the old code should still work but will be removed in the future. If you are only using the Tracing integration there is no need for action.

  • [core] feat: Send transactions in envelopes (#2553)
  • [core] fix: Send event timestamp (#2575)
  • [browser] feat: Allow for configuring TryCatch integration (#2601)
  • [browser] fix: Call wrapped RequestAnimationFrame with correct context (#2570)
  • [node] fix: Prevent reading the same source file multiple times (#2569)
  • [integrations] feat: Vue performance monitoring (#2571)
  • [apm] fix: Use proper type name for op (#2584)
  • [core] fix: sent_at for envelope headers to use same clock (#2597)
  • [apm] fix: Improve bundle size by moving span status to @sentry/apm (#2589)
  • [apm] feat: No longer discard transactions instead mark them deadline exceeded (#2588)
  • [apm] feat: Introduce Sentry.startTransaction and Transaction.startChild (#2600)
  • [apm] feat: Transactions no longer go through beforeSend (#2600)
  • [browser] fix: Emit Sentry Request breadcrumbs from inside the client (#2615)
  • [apm] fix: No longer debounce IdleTransaction (#2618)
  • [apm] feat: Add pageload transaction option + fixes (#2623)
  • [minimal/core] feat: Allow for explicit scope through 2nd argument to captureException/captureMessage (#2627)
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

MTS100 Heizkörperthermostat mit Hub MTS100H keine Datenpunkte verfügbar

Ich nutze Adapterversion 1.20, der Hub wird erkannt, aber kein Thermostat dazu.
Es wäre schön, wenn die Thermostate ansprechbar wären.

übernommen aus :
https://forum.iobroker.net/topic/23641/test-adapter-meross-v1-1-x/39

`
meross.0 2019-11-04 18:42:13.500 info (27070) Devices initialized

  | meross.0 2019-11-04 18:42:13.500 debug (27070) Device Send Raw: 19082963309123251h1248e1e900a721 - data: {"header":{"from":"/app/328853-9a3cfe5bcfe13f5865e95923072b0d64/subscribe","messageId":"fd3665b71ee8026d6721f857bf8ca0c1","method":"G
  | meross.0 2019-11-04 18:42:13.499 debug (27070) Device Send Raw: 19082912831870251h1248e1e900a04e - data: {"header":{"from":"/app/328853-2398aa9c10b3ccc44462b78d40c88480/subscribe","messageId":"e8e94b7e91dbf16d5d562661b08285ad","method":"G
  | meross.0 2019-11-04 18:42:13.456 debug (27070) Device Raw: 19082963309123251h1248e1e900a721 - data: {"header":{"messageId":"f70d491ec3841f53cd2f8b60d67f1ff6","namespace":"Appliance.Control.Electricity","method":"GETACK","payloadVersion":1
  | meross.0 2019-11-04 18:42:13.455 debug (27070) 19082963309123251h1248e1e900a721: initDeviceObjects with channels = [{}] and data = {"electricity":{"channel":0,"current":0,"voltage":2274,"power":0,"config":{"voltageRatio":188,"electricityR
  | meross.0 2019-11-04 18:42:13.454 debug (27070) 19082963309123251h1248e1e900a721 Electricity: {"electricity":{"channel":0,"current":0,"voltage":2274,"power":0,"config":{"voltageRatio":188,"electricityRatio":100}}}
  | meross.0 2019-11-04 18:42:13.452 debug (27070) Device Raw: 19082912831870251h1248e1e900a04e - data: {"header":{"messageId":"98b9170ff987e8ce43b563158f1db20f","namespace":"Appliance.Control.Electricity","method":"GETACK","payloadVersion":1
  | meross.0 2019-11-04 18:42:13.450 debug (27070) 19082912831870251h1248e1e900a04e: initDeviceObjects with channels = [{}] and data = {"electricity":{"channel":0,"current":0,"voltage":2237,"power":0,"config":{"voltageRatio":188,"electricityR
  | meross.0 2019-11-04 18:42:13.450 debug (27070) 19082912831870251h1248e1e900a04e Electricity: {"electricity":{"channel":0,"current":0,"voltage":2237,"power":0,"config":{"voltageRatio":188,"electricityRatio":100}}}
  | meross.0 2019-11-04 18:42:11.971 debug (27070) Device Raw: 19082912831870251h1248e1e900a04e - data: {"header":{"messageId":"1a95b3439b6d1295e15aaeae952d8318","namespace":"Appliance.System.All","method":"GETACK","payloadVersion":1,"from":"
  | meross.0 2019-11-04 18:42:11.971 debug (27070) 19082912831870251h1248e1e900a04e Electricity scheduled in : 20s
  | meross.0 2019-11-04 18:42:11.970 debug (27070) Device Send Raw: 19082912831870251h1248e1e900a04e - data: {"header":{"from":"/app/328853-2398aa9c10b3ccc44462b78d40c88480/subscribe","messageId":"98b9170ff987e8ce43b563158f1db20f","method":"G
  | meross.0 2019-11-04 18:42:11.969 debug (27070) 19082912831870251h1248e1e900a04e: initDeviceObjects with channels = [{}] and data = {"togglex":[{"channel":0,"onoff":0,"lmTime":1572709018}],"triggerx":[],"timerx":[]}
  | meross.0 2019-11-04 18:42:11.968 debug (27070) 19082912831870251h1248e1e900a04e All-Data: {"all":{"system":{"hardware":{"type":"mss310","subType":"un","version":"2.0.0","chipType":"mt7682","uuid":"19082912831870251h1248e1e900a04e","macAdd
  | meross.0 2019-11-04 18:42:11.933 debug (27070) Device Raw: 19082963309123251h1248e1e900a721 - data: {"header":{"messageId":"79854c7814f996da93058bcc1ffe4001","namespace":"Appliance.System.All","method":"GETACK","payloadVersion":1,"from":"
  | meross.0 2019-11-04 18:42:11.932 debug (27070) 19082963309123251h1248e1e900a721 Electricity scheduled in : 20s
  | meross.0 2019-11-04 18:42:11.932 debug (27070) Device Send Raw: 19082963309123251h1248e1e900a721 - data: {"header":{"from":"/app/328853-9a3cfe5bcfe13f5865e95923072b0d64/subscribe","messageId":"f70d491ec3841f53cd2f8b60d67f1ff6","method":"G
  | meross.0 2019-11-04 18:42:11.929 debug (27070) 19082963309123251h1248e1e900a721: initDeviceObjects with channels = [{}] and data = {"togglex":[{"channel":0,"onoff":0,"lmTime":1572028129}],"triggerx":[],"timerx":[]}
  | meross.0 2019-11-04 18:42:11.928 debug (27070) 19082963309123251h1248e1e900a721 All-Data: {"all":{"system":{"hardware":{"type":"mss310","subType":"un","version":"2.0.0","chipType":"mt7682","uuid":"19082963309123251h1248e1e900a721","macAdd
  | meross.0 2019-11-04 18:42:11.926 debug (27070) Device Raw: 1811069847989629086034298f17d056 - data: {"header":{"messageId":"b06e95236ee26370b34e476023bd832a","namespace":"Appliance.System.Online","method":"GETACK","payloadVersion":1,"from
  | meross.0 2019-11-04 18:42:11.925 debug (27070) Online: {"online":{"status":1}}
  | meross.0 2019-11-04 18:42:11.827 debug (27070) Device Send Raw: 1811069847989629086034298f17d056 - data: {"header":{"from":"/app/328853-f51ad779afcbe07a29af06bb1834ca04/subscribe","messageId":"b06e95236ee26370b34e476023bd832a","method":"G
  | meross.0 2019-11-04 18:42:11.756 debug (27070) Device Raw: 1811069847989629086034298f17d056 - data: {"header":{"messageId":"315371004881461212ea7cf7dc752658","namespace":"Appliance.System.All","method":"GETACK","payloadVersion":1,"from":"
  | meross.0 2019-11-04 18:42:11.752 debug (27070) 1811069847989629086034298f17d056: initDeviceObjects with channels = [{}] and data = {"hub":{"hubId":53334,"mode":0,"subdevice":[{"id":"0100224E","status":1,"onoff":1,"lastActiveTime":15728893
  | meross.0 2019-11-04 18:42:11.748 debug (27070) 1811069847989629086034298f17d056 All-Data: {"all":{"system":{"hardware":{"type":"msh300","subType":"un","version":"2.0.0","chipType":"mt7682","uuid":"1811069847989629086034298f17d056","macAdd
  | meross.0 2019-11-04 18:42:11.613 debug (27070) Device Raw: 19082912831870251h1248e1e900a04e - data: {"header":{"messageId":"b0d43f4f2ee92fa227ab22ef87531d3c","namespace":"Appliance.System.Ability","method":"GETACK","payloadVersion":1,"fro
  | meross.0 2019-11-04 18:42:11.612 debug (27070) Device Send Raw: 19082912831870251h1248e1e900a04e - data: {"header":{"from":"/app/328853-2398aa9c10b3ccc44462b78d40c88480/subscribe","messageId":"1a95b3439b6d1295e15aaeae952d8318","method":"G
  | meross.0 2019-11-04 18:42:11.611 debug (27070) 19082912831870251h1248e1e900a04e Abilities: {"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"App
  | meross.0 2019-11-04 18:42:11.610 debug (27070) Device Raw: 19082963309123251h1248e1e900a721 - data: {"header":{"messageId":"16effd4dca1083631559d2761e079fff","namespace":"Appliance.System.Ability","method":"GETACK","payloadVersion":1,"fro
  | meross.0 2019-11-04 18:42:11.610 debug (27070) Device Send Raw: 19082963309123251h1248e1e900a721 - data: {"header":{"from":"/app/328853-9a3cfe5bcfe13f5865e95923072b0d64/subscribe","messageId":"79854c7814f996da93058bcc1ffe4001","method":"G
  | meross.0 2019-11-04 18:42:11.609 debug (27070) 19082963309123251h1248e1e900a721 Abilities: {"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"App
  | meross.0 2019-11-04 18:42:11.542 debug (27070) Device Raw: 1811069847989629086034298f17d056 - data: {"header":{"messageId":"16d390cd3d4ecdb15f7e3f78c86cbc31","namespace":"Appliance.System.Ability","method":"GETACK","payloadVersion":1,"fro
  | meross.0 2019-11-04 18:42:11.542 debug (27070) Device Send Raw: 1811069847989629086034298f17d056 - data: {"header":{"from":"/app/328853-f51ad779afcbe07a29af06bb1834ca04/subscribe","messageId":"315371004881461212ea7cf7dc752658","method":"G
  | meross.0 2019-11-04 18:42:11.540 debug (27070) 1811069847989629086034298f17d056 Abilities: {"payloadVersion":1,"ability":{"Appliance.Config.Key":{},"Appliance.Config.WifiList":{},"Appliance.Config.Wifi":{},"Appliance.Config.Trace":{},"App
  | meross.0 2019-11-04 18:42:11.348 debug (27070) connected set to true
  | meross.0 2019-11-04 18:42:11.345 debug (27070) Device Send Raw: 19082912831870251h1248e1e900a04e - data: {"header":{"from":"/app/328853-2398aa9c10b3ccc44462b78d40c88480/subscribe","messageId":"b0d43f4f2ee92fa227ab22ef87531d3c","method":"G
  | meross.0 2019-11-04 18:42:11.344 info (27070) Device: 19082912831870251h1248e1e900a04e connected
  | meross.0 2019-11-04 18:42:11.342 debug (27070) Device Send Raw: 19082963309123251h1248e1e900a721 - data: {"header":{"from":"/app/328853-9a3cfe5bcfe13f5865e95923072b0d64/subscribe","messageId":"16effd4dca1083631559d2761e079fff","method":"G
  | meross.0 2019-11-04 18:42:11.341 info (27070) Device: 19082963309123251h1248e1e900a721 connected
  | meross.0 2019-11-04 18:42:11.336 debug (27070) Device Send Raw: 1811069847989629086034298f17d056 - data: {"header":{"from":"/app/328853-f51ad779afcbe07a29af06bb1834ca04/subscribe","messageId":"16d390cd3d4ecdb15f7e3f78c86cbc31","method":"G
  | meross.0 2019-11-04 18:42:11.332 info (27070) Device: 1811069847989629086034298f17d056 connected
  | meross.0 2019-11-04 18:42:11.141 debug (27070) {"uuid":"19082912831870251h1248e1e900a04e","onlineStatus":1,"devName":"Sidewinder","devIconId":"device024","bindTime":1569591975,"deviceType":"mss310","subType":"eu","channels":[{}],"region":
  | meross.0 2019-11-04 18:42:11.141 info (27070) Device 19082912831870251h1248e1e900a04e initialized
  | meross.0 2019-11-04 18:42:11.139 debug (27070) {"uuid":"19082963309123251h1248e1e900a721","onlineStatus":1,"devName":"Ender","devIconId":"device024","bindTime":1569592704,"deviceType":"mss310","subType":"eu","channels":[{}],"region":"eu",
  | meross.0 2019-11-04 18:42:11.139 info (27070) Device 19082963309123251h1248e1e900a721 initialized
  | meross.0 2019-11-04 18:42:11.070 debug (27070) {"uuid":"1811069847989629086034298f17d056","onlineStatus":1,"devName":"Smart Hub","devIconId":"device024","bindTime":1570464512,"deviceType":"msh300","subType":"un","channels":[{}],"region":"
  | meross.0 2019-11-04 18:42:11.069 info (27070) Device 1811069847989629086034298f17d056 initialized
  | meross.0 2019-11-04 18:42:10.616 debug (27070) connected set to false
  | meross.0 2019-11-04 18:42:10.574 debug (27070) States connected to redis: 0.0.0.0:9000
  | meross.0 2019-11-04 18:42:10.560 info (27070) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.meross, node: v10.17.0
  | meross.0 2019-11-04 18:42:10.490 debug (27070) statesDB connected
  | meross.0 2019-11-04 18:42:10.486 debug (27070) Objects connected to redis: 0.0.0.0:9001
  | meross.0 2019-11-04 18:42:10.485 debug (27070) Redis States: Use Redis connection: 0.0.0.0:9000
  | meross.0 2019-11-04 18:42:10.483 debug (27070) objectDB connected
  | meross.0 2019-11-04 18:42:10.244 debug (27070) Redis Objects: Use Redis connection: 0.0.0.0:9001
  | {1}
`

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

An in-range update of @sentry/integrations is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The dependency @sentry/integrations was updated from 5.14.1 to 5.14.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@sentry/integrations is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 5.14.2
  • [apm] fix: Use Performance API for timings when available, including Web Workers (#2492)
  • [apm] fix: Remove Performance references (#2495)
  • [apm] fix: Set op in node http.server transaction (#2496)
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

How to run?

Hi,

I try to run your application but no information are showed, in log file I found

2019-11-25 22:39:28.642  - error: undefined Cannot find directory of adapter meross
2019-11-25 22:39:28.645  - warn: undefined Terminated (CANNOT_FIND_ADAPTER_DIR): Without reason
2019-11-25 22:39:42.171  - error: undefined Cannot find directory of adapter meross
2019-11-25 22:39:42.174  - warn: undefined Terminated (CANNOT_FIND_ADAPTER_DIR): Without reason
2019-11-25 22:41:01.195  - error: undefined Cannot find directory of adapter meross
2019-11-25 22:41:01.197  - warn: undefined Terminated (CANNOT_FIND_ADAPTER_DIR): Without reason
2019-11-25 22:44:43.774  - error: undefined Cannot find directory of adapter meross
2019-11-25 22:44:43.776  - warn: undefined Terminated (CANNOT_FIND_ADAPTER_DIR): Without reason
2019-11-25 21:57:24.196  - error: undefined Cannot find directory of adapter meross
2019-11-25 21:57:24.199  - warn: undefined Terminated (CANNOT_FIND_ADAPTER_DIR): Without reason

My step:

  • npm install package.json
  • node main.js

Meross Luftbefeuchter lässt sich nicht steuern

Hallo,
ich weiß jetzt nicht genau welche Infos benötigt werden um sowas evtl noch mit rein zunehmen, hab mal ein paar Screenshots gemacht ich hoffe die helfen.

Vielen Dank schon mal hoff das klappt :-)

Amazon Link:
https://www.amazon.de/Luftbefeuchter-Ultraschall-Humidifier-Arbeitszeit-Nachtlicht/dp/B07T9HL5QN/ref=sr_1_1?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&crid=1Z19KVTX0472A&keywords=meross+luftbefeuchter&qid=1567450607&s=gateway&sprefix=meross+luft%2Caps%2C159&sr=8-1

Bilder:
IMG_4136
IMG_4137
IMG_4138
IMG_4139

Please add your adapter to ioBroker.discovery

I am an automatic service from ioBroker that searches adapters and makes suggestions.

I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.

Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.

Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.

Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.

On questions, the other developers will support in the forum or via GitHub issues too.

If no detection is possible, simply close this issue and I won't bother you again. ;-)

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Meross Connection Error: Error: 1004: A

2020-04-21 20:37:53.514 - info: meross.0 (19955) starting. Version 1.3.13 in /opt/iobroker/node_modules/iobroker.meross, node: v12.16.2, js-controller: 3.0.14
2020-04-21 20:37:54.159 - error: meross.0 (19955) Meross Connection Error: Error: 1004: A

Since the update to the new js-controller from 2.x (latest) I am getting this error on start.

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.0.2 to 6.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v6.1.0

6.1.0 / 2019-04-07

🔒 Security Fixes

  • #3845: Update dependency "js-yaml" to v3.13.0 per npm security advisory (@plroebuck)

🎉 Enhancements

  • #3766: Make reporter constructor support optional options parameter (@plroebuck)
  • #3760: Add support for config files with .jsonc extension (@sstephant)

📠 Deprecations

These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:

🐛 Fixes

  • #3829: Use cwd-relative pathname to load config file (@plroebuck)
  • #3745: Fix async calls of this.skip() in "before each" hooks (@juergba)
  • #3669: Enable --allow-uncaught for uncaught exceptions thrown inside hooks (@givanse)

and some regressions:

📖 Documentation

🔩 Other

  • #3830: Replace dependency "findup-sync" with "find-up" for faster startup (@cspotcode)
  • #3799: Update devDependencies to fix many npm vulnerabilities (@XhmikosR)
Commits

The new version differs by 28 commits.

  • f4fc95a Release v6.1.0
  • bd29dbd update CHANGELOG for v6.1.0 [ci skip]
  • aaf2b72 Use cwd-relative pathname to load config file (#3829)
  • b079d24 upgrade deps as per npm audit fix; closes #3854
  • e87c689 Deprecate this.skip() for "after all" hooks (#3719)
  • 81cfa90 Copy Suite property "root" when cloning; closes #3847 (#3848)
  • 8aa2fc4 Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
  • 586bf78 Update JS-YAML to address security issue (#3845)
  • d1024a3 Update doc examples "tests.html" (#3811)
  • 1d570e0 Delete "/docs/example/chai.js"
  • ade8b90 runner.js: "self.test" undefined in Browser (#3835)
  • 0098147 Replace findup-sync with find-up for faster startup (#3830)
  • d5ba121 Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
  • a3089ad update package-lock
  • 75430ec Upgrade yargs-parser dependency to avoid loading 2 copies of yargs

There are 28 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Meross schaltet den Service ab

Hallo zusammen,
Meross hat mir gerade eine Mail geschrieben. Der Adapter ist jetzt auf GELB und nichts läßt sich mehr steuern. Habt Ihr das auch?
Siehe Mail:

Dear Customer,

This is meross cloud security team contacting you.
First of all, thanks for purchasing meross and we hope that you enjoy life with our smart products.
Recently our cloud security system has noticed that your devices are communicating with the could server at an extremely high frequency. We consider these behaviors abnormal and are concerned about the security of your devices.
Due to the security concerns and the intent to avoid any further potential damage, we will terminate the cloud services of these devices for now.
If you are sure that your devices are safe, NOT hacked, and are performing as expected. Please first lower your periodic request rate to no more than one message every ten seconds and then send an email to [email protected]. We will resume cloud service for you within 24 hours. Please note that any abnormal high cloud request frequency will cause cloud service termination again.
Should you have any information you would like to provide us with or would like to offer us any clarification, please contact us within 24 hours.

Thanks!
meross Cloud Security Team

support mss110 Smart Plug Mini

Hallo Apollon77,
zu aller erst möchte ich für den iobrocker Adapter ein großes Dankeschön aussprechen, mir ist es dadurch möglich geworden einige Home Steuerung in Zusammenhang mit iobrocker und node-red zu realisieren.

Describe the solution you'd like

Bis jetzt habe ich nur mit den Meross mss310 gearbeitet, nun habe ich mir auch die mss110 mini gekauft und bin vll. auch blauäugig davon ausgegangen das diese unterstützt wird.
Die mss110 wird im iobrocker Adapter zwar erkannt und die Eigenschaftsfelder wie Switch sind auch vorhanden. Ändert man aber hier den Wert wird die Steckdose nicht in ihrem Zustand verändert, was sehr schade ist.

Falls es sich hier nur um einen geringen Aufwand handelt die Funktionalität Switch true/false zu integrieren wäre es toll dieses Feature in eine der nächsten Releases einzubauen.

Nichts geht mehr nach Update zu 1.1

Hallo Apollon77,
nach dem update wurde der nicht mehr Grün.
Nach komplettem runterschmeißen ist jedesmal der Update.adapter von vorher 2.0.0 auf 1.3.0 und der Admin.adapter von 3.6.3 auf 2.0.9
Nach update der 2 Adapter....Install Meross-adapert 1.1.0 install.... wird wieder nicht grün
Nach deinstall das gleiche Spiel mit den anderen 2 Adaptern

Ich schicke gleich mal neen Log hinterher

An in-range update of @iobroker/testing is breaking the build 🚨

The devDependency @iobroker/testing was updated from 1.1.5 to 1.1.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@iobroker/testing is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

  • 6ac7aad Release v1.1.6
  • b7f424b Remove hashbangs from code in the unit test loader

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Think about to fix the issues found by adapter checker

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

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

  • [E140] width and height of logo are not equal
  • [E605] No actual year found in copyright. Please add "Copyright (c) 2018-2021 Apollon77 [email protected]" at the end of README.md
  • [E701] No actual year found in LICENSE. Please add "Copyright (c) 2018-2021 Apollon77 [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

What node.js version is needed?

My Adapter shows no error but doesn't start properly (yellow indicator).
What node.js is required?
I have v8.16.0 installed

This is the debug log:
`

meross.0 2019-07-17 12:14:21.190 debug system.adapter.admin.0: logging true
meross.0 2019-07-17 12:14:18.344 debug connected set to false
meross.0 2019-07-17 12:14:18.214 info starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.meross, node: v8.16.0
meross.0 2019-07-17 12:14:18.093 debug statesDB connected
meross.0 2019-07-17 12:14:18.025 debug objectDB connected

`

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.