For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

Think about update stable version to 2.0.0

Version: stable=1.2.2 (428 days old) => latest=2.0.0 (293 days old)
Installs: stable=160 (53.16%), latest=105 (34.88%), total=301
Click to edit

mySensors instance continuously connects/disconnects every few seconds, as can be seen below. I have all latest updates installed - Linux, Node.js, adapter, controller, etc.

mySensors nodes and serial gateway are based on latest 2.3.2 code

I was thinking that it could be normal when instance times out and gets disconnected when no nodes are reporting status change. I modified one of the nodes, forcing it to send update every 2 seconds, but adapter still keeps connecting and disconnecting every few seconds leading to loss of data.

2020-07-17 17:11:24.965 - info: mysensors.0 (19106) Connected
2020-07-17 17:11:32.981 - info: mysensors.0 (19106) disconnected
2020-07-17 17:11:33.291 - info: mysensors.0 (19106) Connected
2020-07-17 17:11:45.418 - info: mysensors.0 (19106) disconnected
2020-07-17 17:11:46.990 - info: mysensors.0 (19106) Connected
2020-07-17 17:12:09.659 - info: mysensors.0 (19106) disconnected
2020-07-17 17:12:09.748 - info: mysensors.0 (19106) Connected
2020-07-17 17:12:23.381 - info: mysensors.0 (19106) disconnected
2020-07-17 17:12:23.453 - info: mysensors.0 (19106) Connected
2020-07-17 17:12:29.454 - info: mysensors.0 (19106) disconnected
2020-07-17 17:12:32.527 - info: mysensors.0 (19106) Connected
2020-07-17 17:12:43.093 - info: mysensors.0 (19106) disconnected
2020-07-17 17:12:46.217 - info: mysensors.0 (19106) Connected
2020-07-17 17:12:49.004 - info: mysensors.0 (19106) Received INTERNAL message: I_DISCOVER_RESPONSE: 0
2020-07-17 17:12:53.717 - info: mysensors.0 (19106) disconnected
2020-07-17 17:12:57.241 - info: mysensors.0 (19106) Connected
2020-07-17 17:13:12.391 - info: mysensors.0 (19106) disconnected
2020-07-17 17:13:12.400 - info: mysensors.0 (19106) Connected
2020-07-17 17:13:19.915 - info: mysensors.0 (19106) disconnected
2020-07-17 17:13:19.950 - info: mysensors.0 (19106) Connected
2020-07-17 17:13:31.980 - info: mysensors.0 (19106) disconnected
2020-07-17 17:13:35.051 - info: mysensors.0 (19106) Connected
2020-07-17 17:13:41.052 - info: mysensors.0 (19106) disconnected
2020-07-17 17:13:42.610 - info: mysensors.0 (19106) Connected
2020-07-17 17:13:48.609 - info: mysensors.0 (19106) disconnected
2020-07-17 17:13:50.150 - info: mysensors.0 (19106) Connected
2020-07-17 17:14:15.846 - info: mysensors.0 (19106) disconnected
2020-07-17 17:14:15.876 - info: mysensors.0 (19106) Connected

I have looked in the mysensors/getmeta.js

line 10 'S_WIND': {index: 9, role: 'direction', vars: ['V_WIND', 'V_GUST']},

Is V_DIRECTION supposed to be included here?

Hi all,
In my opinion, the ack flag is not processed correctly. Currently the messages are sent with ack request and the ack flag is set in the iobroker as soon as the ack confirmation arrives.
However, the IOB ack is normally set as soon as an actuator has performed an action and not as soon as the data transmission was successful. Therefore ideally the Mysensors ack should be used to retrigger the data transfer if it fails but in no way to set the IOB ack flag.

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

hi my god made mqtt communication mysensor gateway, can you make an adapter

Hallo
Das Einbinden meiner MySensor Temperatur Sensoren in ioBroker funktioniert leider nicht.
Ich verwende ein MySensor WLAN Gateway. Die Sensoren verbinden sich mit dem Gateway.
In ioBroker kann ich das WLAN Gateway dann per TCP-Client einbinden.
Den Anlernmodus habe ich aktiviert und im debug Modus kommen folgende Werte an.

Die Sensoren werden allerdings nicht eingebunden.
Ich habe das Ganze mittlerweile auch mit einem per USB angebundenen MySeonsors Gateway probiert. Auch hier kommen die Werte der Sensoren an werden aber nicht in ioBroker angelegt.
Kann mir jemand sagen, was ich machen muss damit die Sensoren angelegt werden ?
Vielen Dank im Voraus.

I set up an ethernet GW with following sketch

/*
 * The MySensors Arduino library handles the wireless radio link and protocol
 * between your home built sensors/actuators and HA controller of choice.
 * The sensors forms a self healing radio network with optional repeaters. Each
 * repeater and gateway builds a routing tables in EEPROM which keeps track of the
 * network topology allowing messages to be routed to nodes.
 *
 * Created by Henrik Ekblad <[email protected]>
 * Copyright (C) 2013-2018 Sensnology AB
 * Full contributor list: https://github.com/mysensors/MySensors/graphs/contributors
 *
 * Documentation: http://www.mysensors.org
 * Support Forum: http://forum.mysensors.org
 *
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU General Public License
 * version 2 as published by the Free Software Foundation.
 *
 *******************************
 *
 * REVISION HISTORY
 * Version 1.0 - Henrik EKblad
 * Contribution by a-lurker and Anticimex,
 * Contribution by Norbert Truchsess <[email protected]>
 * Contribution by Tomas Hozza <[email protected]>
 *
 *
 * DESCRIPTION
 * The EthernetGateway sends data received from sensors to the ethernet link.
 * The gateway also accepts input on ethernet interface, which is then sent out to the radio network.
 *
 * The GW code is designed for Arduino 328p / 16MHz.  ATmega168 does not have enough memory to run this program.
 *
 * LED purposes:
 * - To use the feature, uncomment MY_DEFAULT_xxx_LED_PIN in the sketch below
 * - RX (green) - blink fast on radio message received. In inclusion mode will blink fast only on presentation received
 * - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
 * - ERR (red) - fast blink on error during transmission error or receive crc error
 *
 * See http://www.mysensors.org/build/ethernet_gateway for wiring instructions.
 *
 */

// Enable debug prints to serial monitor
#define MY_DEBUG

// Enable and select radio type attached
#define MY_RADIO_RF24
//#define MY_RADIO_NRF5_ESB
//#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95

// Enable gateway ethernet module type
#define MY_GATEWAY_W5100

// W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
//#define MY_W5100_SPI_EN 4

// Enable Soft SPI for NRF radio (note different radio wiring is required)
// The W5100 ethernet module seems to have a hard time co-operate with
// radio on the same spi bus.
#if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
#define MY_SOFTSPI
#define MY_SOFT_SPI_SCK_PIN 14
#define MY_SOFT_SPI_MISO_PIN 16
#define MY_SOFT_SPI_MOSI_PIN 15
#endif

// When W5100 is connected we have to move CE/CSN pins for NRF radio
#ifndef MY_RF24_CE_PIN
#define MY_RF24_CE_PIN 5
#endif
#ifndef MY_RF24_CS_PIN
#define MY_RF24_CS_PIN 6
#endif

// Enable UDP communication
//#define MY_USE_UDP  // If using UDP you need to set MY_CONTROLLER_IP_ADDRESS below

// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
#define MY_IP_ADDRESS 192,168,000,233

// If using static ip you can define Gateway and Subnet address as well
#define MY_IP_GATEWAY_ADDRESS 192,168,0,100
#define MY_IP_SUBNET_ADDRESS 255,255,255,0

// Renewal period if using DHCP
//#define MY_IP_RENEWAL_INTERVAL 60000

// The port to keep open on node server mode / or port to contact in client mode
#define MY_PORT 5003

// Controller ip address. Enables client mode (default is "server" mode).
// Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 0, 230

// The MAC address can be anything you want but should be unique on your network.
// Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
// Note that most of the Arduino examples use  "DEAD BEEF FEED" for the MAC address.
#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED

// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
//#define MY_INCLUSION_BUTTON_FEATURE
// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN  3

// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300

// Flash leds on rx/tx/err
// Uncomment to override default HW configurations
//#define MY_DEFAULT_ERR_LED_PIN 7  // Error led pin
//#define MY_DEFAULT_RX_LED_PIN  8  // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN  9  // Transmit led pin

#if defined(MY_USE_UDP)
#include <EthernetUdp.h>
#endif
#include <Ethernet.h>
#include <MySensors.h>

void setup()
{
	// Setup locally attached sensors
}

void presentation()
{
	// Present locally attached sensors here
}

void loop()
{
	// Send locally attached sensors data here
}

the adapter is set to be server listenig to all ports,

But I dont get any or wrong readings, on the serial monitor teh messages receiving look fine.

Think about update stable version to 2.0.3

Version: stable=2.0.1 (542 days old) => latest=2.0.3 (15 days old)
Installs: stable=234 (71.56%), latest=29 (8.87%), total=327
Click to edit

Think about update stable version to 3.0.0

Version: stable=2.0.3 (146 days old) => latest=3.0.0 (15 days old)
Installs: stable=120 (40.27%), latest=24 (8.05%), total=298
Click to edit

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

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

• [E154] common.dependencies must contain{"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
• [E604] No "## License" found in README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2016-2022 bluefox [email protected]" at the start of LICENSE

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

• [W801] .npmignore not found

Thanks,
your automatic adapter checker.

Think about update stable version to 2.0.1

Version: stable=2.0.0 (398 days old) => latest=2.0.1 (15 days old)
Installs: stable=168 (54.72%), latest=51 (16.61%), total=307
Click to edit

Hello,
I have two sensors with a temperatue sensor and a pressure sensor.
I init the sensor with
present(CHILD_ID_Temp, S_TEMP, "Ausentemperatur");
present(CHILD_ID_Baro, S_BARO, "Luftdruck");
in ioBroker I only get V_PRESSURE value for S_BARO and
V_TEMP for S_TEMP.
But S_TEMP has two variables V_TEMP and V_ID and S_BARO has two variables too
V_PRESSURE ans V_FORECAST

Additional V_Pressure has max of 100 and unit of % ans thats wrong.

Are there a possibillity to correct this ?

Thank you very much
Best regards

Dear Adapter developer,

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

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

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

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

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

Please close the issue after you checked it.

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

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.

why i got suddly this error? i changed nothing!

2019-11-10 22:44:08.883 - debug: mysensors.0 Message type: internal
2019-11-10 22:44:08.883 - debug: mysensors.0 Log :103976045 TSF:MSG:READ,1-1-0,s=1,c=1,t=16,pt=2,l=2,sg=0:1
2019-11-10 22:44:08.884 - debug: mysensors.0 Serial data received: 1;1;1;0;16;1
2019-11-10 22:44:08.884 - debug: mysensors.0 Got: {"id":"1","childId":"1","type":"set","ack":false,"payload":"1","subType":"V_TRIPPED"}
2019-11-10 22:44:08.884 - debug: mysensors.0 Message type: set
2019-11-10 22:44:08.884 - debug: mysensors.0 Set value 1.1_DOOR.V_TRIPPED 1: true boolean
2019-11-10 22:44:08.888 - silly: mysensors.0 inMem message mysensors.0.* mysensors.0.1.1_DOOR.V_TRIPPED val=true, ack=true, ts=1573422248885, q=0, from=system.adapter.mysensors.0, user=system.user.admin, lc=1573422248885
2019-11-10 22:44:09.003 - debug: mysensors.0 Serial data received: 0;255;3;0;9;103976165 TSF:MSG:READ,1-1-0,s=1,c=1,t=16,pt=2,l=2,sg=0:0
2019-11-10 22:44:09.003 - debug: mysensors.0 Got: {"id":"0","childId":"255","type":"internal","ack":false,"payload":"103976165 TSF:MSG:READ,1-1-0,s=1,c=1,t=16,pt=2,l=2,sg=0:0","subType":"I_LOG_MESSAGE"}
2019-11-10 22:44:09.003 - debug: mysensors.0 Message type: internal
2019-11-10 22:44:09.003 - debug: mysensors.0 Log :103976165 TSF:MSG:READ,1-1-0,s=1,c=1,t=16,pt=2,l=2,sg=0:0
2019-11-10 22:44:09.003 - debug: mysensors.0 Serial data received: 1;1;1;0;16;0
2019-11-10 22:44:09.004 - debug: mysensors.0 Got: {"id":"1","childId":"1","type":"set","ack":false,"payload":"0","subType":"V_TRIPPED"}
2019-11-10 22:44:09.004 - debug: mysensors.0 Message type: set
2019-11-10 22:44:09.004 - debug: mysensors.0 Set value 1.1_DOOR.V_TRIPPED 1: false boolean
2019-11-10 22:44:09.012 - silly: mysensors.0 inMem message mysensors.0.* mysensors.0.1.1_DOOR.V_TRIPPED val=false, ack=true, ts=1573422249011, q=0, from=system.adapter.mysensors.0, user=system.user.admin, lc=1573422249011
2019-11-10 22:45:05.792 - info: mysensors.0 disconnected
2019-11-10 22:45:05.794 - silly: mysensors.0 inMem message mysensors.0.* mysensors.0.info.connection val=false, ack=true, ts=1573422305793, q=0, from=system.adapter.mysensors.0, user=system.user.admin, lc=1573422305793
2019-11-10 22:46:11.275 - silly: mysensors.0 inMem message mysensors.0.* mysensors.0.info.connection val=false, ack=true, ts=1573422371246, q=0, from=system.adapter.mysensors.0, user=system.user.admin, lc=1573422305793
2019-11-10 22:46:49.572 - debug: mysensors.0 objectDB connected
2019-11-10 22:46:49.644 - debug: mysensors.0 statesDB connected
2019-11-10 22:46:49.723 - info: mysensors.0 starting. Version 1.2.2 in /opt/iobroker/node_modules/iobroker.mysensors, node: v10.17.0
2019-11-10 22:46:49.847 - info: mysensors.0 Serial port opened
2019-11-10 22:46:49.848 - debug: mysensors.0 Send raw data: 0;0;3;0;14;Gateway startup complete
2019-11-10 22:46:51.368 - info: mysensors.0 Connected
2019-11-10 22:46:51.371 - debug: mysensors.0 Send raw data: 0;0;3;0;6;get metric
2019-11-10 22:46:51.371 - debug: mysensors.0 Send raw data: 0;0;3;0;19;force presentation
2019-11-10 22:46:51.372 - warn: mysensors.0 Wrong serial data:
2019-11-10 22:46:51.372 - warn: mysensors.0 Wrong serial data: __ __ ____
2019-11-10 22:46:51.373 - warn: mysensors.0 Wrong serial data: | / |_ / | ___ _ __ ___ ___ _ __ ___
2019-11-10 22:46:51.377 - warn: mysensors.0 Wrong serial data: | |/| | | | _ \ / _ \ _ \/ __|/ _ \| _/ __|
2019-11-10 22:46:51.377 - warn: mysensors.0 Wrong serial data: | | | | || || | / | | _ \ _ | | _
2019-11-10 22:46:51.380 - silly: mysensors.0 inMem message mysensors.0.* mysensors.0.info.connection val=true, ack=true, ts=1573422411372, q=0, from=system.adapter.mysensors.0, user=system.user.admin, lc=1573422411372
2019-11-10 22:46:51.383 - warn: mysensors.0 Wrong serial data: || ||_, |/ ___|| ||/_/|| |/
2019-11-10 22:46:51.384 - warn: mysensors.0 Wrong serial data: |__/ 2.3.0
2019-11-10 22:46:51.384 - warn: mysensors.0 Wrong serial data:
2019-11-10 22:46:51.385 - warn: mysensors.0 Wrong serial data: 16 MCO:BGN:INIT NODE,CP=RNNNA---,VER=2.3.0
2019-11-10 22:46:51.393 - warn: mysensors.0 Wrong serial data: 25 TSM:INIT
2019-11-10 22:46:51.393 - warn: mysensors.0 Wrong serial data: 26 TSF:WUR:MS=0
2019-11-10 22:46:51.397 - warn: mysensors.0 Wrong serial data: 33 TSM:INIT:TSP OK
2019-11-10 22:46:51.399 - warn: mysensors.0 Wrong serial data: 35 TSF:SID:OK,ID=3
2019-11-10 22:46:51.399 - warn: mysensors.0 Wrong serial data: 37 TSM:FPAR
2019-11-10 22:46:51.440 - warn: mysensors.0 Wrong serial data: 73 TSF:MSG:SEND,3-3-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2019-11-10 22:46:52.043 - warn: mysensors.0 Wrong serial data: 679 TSF:MSG:READ,0-0-3,s=255,c=3,t=8,pt=1,l=1,sg=0:0
2019-11-10 22:46:52.063 - warn: mysensors.0 Wrong serial data: 685 TSF:MSG:FPAR OK,ID=0,D=1
2019-11-10 22:46:52.664 - info: host.server instance system.adapter.node-red.0 started with pid 3747
2019-11-10 22:46:52.873 - debug: mysensors.0 Send raw data: 0;0;3;0;13;force restart

I am trying to add a node to an existing mySensors configuration in ioBroker, but instead of adding dedicated Light Lux Sensor node, it renames existing node 10 and adds line 10.1_Light_Level. Tried multiple times, same result. My all nodes are based on 2.3.2 software. IoBroker uses latest mySensors adapter 2.0.0.

It would be fine, if the serial port could also selected by id from /dev/serial/by-id

Background:
I have 2 Sensebender Gateways connected to the Raspberry Pi (and 1 Conbee II), so /dev/ttyACM0 can be any of this devices depending how it is assigned at boot of the Raspi!

I suspect that one of my nodes is too far away from gateway, so I added a repeater in between, which is recognized by ioBroker as

I set mySensor adapter into a debug mode. Should I see any confirmation that repeater node is operational and periodically transmit data from a faraway node? Thank you.

request type: I_TIME
I need a local date/time.

You code:

main.js
mySensorsInterface.write(result[i].id + ';' + result[i].childId + ';3;1;1;' + Math.round(new Date().getTime() / 1000), ip);

do this way:
const utcTime = Math.round(((new Date()).getTime()) / 1000);
const localTime = utcTime - (new Date()).getTimezoneOffset() * 60;
mySensorsInterface.write(result[i].id + ';' + result[i].childId + ';3;1;1;' + localTime, ip);

Thank you.

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!

Boolean is not the correct data type for V_SCENE_ON and V_SCENE_OFF. These typpes are used to transport the number/ID of a scene which sould be switched on or off. At the moment the data type has to be manually changed to make the official mysensors examples work.

I'm using a mysensors serial gateway connected to iobroker, I would like to know how to send the V_IR_RECORD command using iobroker. On the NODE serial port I see the IR command coming but I don't know how to activate the record mode to record the message and send it to the controller.
And I can't find information on the documentation
When the node register to the controller, I can see only V_IR_RECEIVE and V_IR_SEND, but not V_IR_RECORD.
Can someone help me?

Hey,

i am sorry for opening an issue but i dont know where i can just ask or write a personal message to a contributor (thanks github). So i need to do it on this way - again sorry!

Is the very cool feature "smart sleep" in the adapter supported?
In a nutshell: the controller (in this case ioBroker) knows the device is sleeping and stores messages for this sleeping node until its wake, then ioBroker sends them.
https://www.mysensors.org/download/sensor_api_20#sleeping

Notification from ioBroker Check and Service Bot

Dear adapter developer,

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

Please see the result of the check below.

ioBroker.mysensors

-

ERRORS:

• ❗ [E029] Node.js 16 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '12.17.0' } }" at package.json.
• ❗ [E033] @iobroker/adapter-core 2.6.7 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
• ❗ [E035] No devDependency declared for @iobroker/testing. Please add "@iobroker/testing":"4.1.3" to devDependencies at package.json
• ❗ [E204] Versions "2.0.2, 1.2.1" listed at common.news at io-package.json do not exist at NPM. Please remove from news section.
• ❗ [E604] No ## License found in README.md

WARNINGS:

• 👀 [W044] dependency should not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "sensors:2.0.0"
• 👀 [W046] devDependency should not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "nan:2.17.0"
• 👀 [W105] Missing mandatory translation into de of "common.titleLang" in io-package.json.
• 👀 [W105] Missing suggested translation into ru,pt,nl,fr,it,es,pl,uk,zh-cn of "common.titleLang" in io-package.json.
• 👀 [W109] Missing suggested translation into uk,zh-cn of "common.desc" in io-package.json.
• 👀 [W145] Missing suggested translation into uk,zh-cn of some "common.news" in io-package.json.
• 👀 [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
• 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
• 👀 [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
• 👀 [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package
• 👀 [W519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
• 👀 [W522] Please consider migrating to admin 5 UI (jsonConfig).
• 👀 [W523] "package-lock.json" not found in repo! Please remove from .gitignore!

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

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

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

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

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

your
ioBroker Check and Service Bot

@mcm1957 for evidence

A node sends a request for variable value like :
1;2;2;0;2;
and interprets as :
Got: {"id":"1","childId":"2","type":"req","ack":false,"payload":"","subType":"V_LIGHT"}
V_Light does not exists anymore in 2.x protocol
Instead 2 should be translated to V_STATUS
Controller does not respond to request

Hello,

currently I have a 433mhz receiver on my mysensors gateway.

There are two types of messages that should be received by iobroker

1. actual value of received packet
2. rssi

The rssi values are calculated on the gateway and are send along with thie code of the received package (a few seconds later)

gateway sketch (only the most important parts):

MyMessage msg[12];
MyMessage msg_rssi[12];

present(7, S_DOOR);

msg[7].setSensor(7);  msg[7].setType(V_TRIPPED);
msg_rssi[7].setSensor(7);  msg_rssi[7].setType(V_VAR1);

send(msg_rssi[i].set(rssi));

      else if (code == XXX)
      {
        // Reed (2)
        send(msg[7].set(1));
        send(msg[7].set(0));
        rssi_current_count[7]++;
        last_tripped = millis();
        tripped = true;
      }

On iobroker I can only see the V_TRIPPED values but not the V_VAR1 values (representing my rssi value)

Is there a way to enable debugging for this adapter to see where the values got missing?

I also get stuff like this when the gateways starts:

mysensors.0 | 2018-03-16 17:15:32.925 | warn | ID not found. Inclusion mode OFF: {"id":"0","childId":"7","type":"presentation","ack":false,"payload":"","subType":"S_DOOR"}
-- | -- | -- | --

Edit: I tried to change but nothing changed

var presentation = {
    'S_DOOR':               {index: 0,  role: 'door',              vars: ['V_TRIPPED','V_VAR1']},
    'S_MOTION':             {index: 1,  role: 'motion',            vars: ['V_TRIPPED','V_VAR1']},

Describe the bug
The selection of serial port is not available

To Reproduce
Steps to reproduce the behavior:

1. Go to instance
2. Click on serial port
3. Scroll down to 'serial port....'
4. See nothing appears

Expected behavior
It schould appear a selection of serial ports

Screenshots & Logfiles

TypeError: serialport.list is not a function at Adapter. (/opt/iobroker/node_modules/iobroker.mysensors/main.js:44:40) at Adapter.emit (events.js:314:20) at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5301:34) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:322:37) at processImmediate (internal/timers.js:461:21)

Versions:

• Adapter version: 3.0.0
• JS-Controller version: 4.0.23
• Node version: v12.22.12
• Operating system: Debian

Additional context
Add any other context about the problem here.

IoBroker shows the Temp and Pressure value but Hum is missing.

mysensors.0 2019-09-05 18:55:48.532 info Add new object: 1.0_TEMP.V_ID - 1.0_TEMP.V_ID mysensors.0 2019-09-05 18:55:48.531 info Add new object: 1.0_TEMP.V_TEMP - 1.0_TEMP.V_TEMP mysensors.0 2019-09-05 18:55:48.530 info Add new object: 1.0_TEMP - 1.0_TEMP mysensors.0 2019-09-05 18:55:48.475 info Add new object: 1.2_BARO.V_FORECAST - 1.2_BARO.V_FORECAST mysensors.0 2019-09-05 18:55:48.475 info Add new object: 1.2_BARO.V_PRESSURE - 1.2_BARO.V_PRESSURE mysensors.0 2019-09-05 18:55:48.474 info Add new object: 1.2_BARO - 1.2_BARO mysensors.0 2019-09-05 18:55:48.416 info Version :1.1 mysensors.0 2019-09-05 18:55:48.356 warn setObject mysensors.0.1 (type=device) property native missing! mysensors.0 2019-09-05 18:55:48.353 info Name :BME280 Sensor