Posts made by Clone Tv

it's a shame, it's a pity that there is no such possibility ..

how to use scripts in groups? where to add the name of the script file? what value should I use to turn on and off?

Thanks for your reply, this method will do. Is there no way to bind groups to mgtt topics?

@jkandasa
Wouldn't it bother you to give a solution with an API? control through an arbitrary mgtt topic is desirable, although any other options are interesting. I looked at the page with the description of the API but did not see direct HTTP links to control .. or I looked wrong?

The question is about groups, in fact these are scenarios. The question is how to call (enable or disable) a group from external sources? For example, from a node, sensor or using voice control?

@jkandasa
Senks, unfortunately I have not seen this post, but together we found a way out of this task

https://forum.mysensors.org/topic/11373/where-to-send-messages-about-battery-charge-and-signal-strength/12

It's not about the radio module, it's about the way this topic and its identifiers are sent. I am using nrf24 and Esp. Consider simply sending a statistical value, such as the digit -12. The main thing is that it would appear in the appropriate column in myController.

How do I display the RSSI in the current version?
i try on sensor:

void receive(const MyMessage & msg) {
....
          if ((msg.type == V_VAR1) || (msg.type == V_VAR5) || (msg.type == I_SIGNAL_REPORT_REQUEST)) {
            radioQuality();
            PRINTF("-- rssi: %u\n", rssi);
            MY_CRITICAL_SECTION {
              char *buff = new char[18]{};
              (void) snprintf(buff, 17, "rssi: %d", rssi);

  // 1.a  _sendRoute(build(_msgTmp, GATEWAY_ADDRESS, MY_NODE_ID, C_SET, V_VAR1, false).set(buff));
  // 1.b _sendRoute(build(_msgTmp, GATEWAY_ADDRESS, MY_NODE_ID, C_SET, V_VAR5, false).set(buff));
  // 1.c _sendRoute(build(_msgTmp, GATEWAY_ADDRESS, MY_NODE_ID, C_SET, I_SIGNAL_REPORT_RESPONSE, false).set(buff));
     
  // 2.a _sendRoute(build(_msgTmp, GATEWAY_ADDRESS, MY_NODE_ID, C_SET, V_VAR1, false).set(rssi));
  // 2.b _sendRoute(build(_msgTmp, GATEWAY_ADDRESS, MY_NODE_ID, C_SET, V_VAR5, false).set(rssi));
  // 2.c _sendRoute(build(_msgTmp, GATEWAY_ADDRESS, MY_NODE_ID, C_SET, I_SIGNAL_REPORT_RESPONSE, false).set(rssi));

  // 3.a  _sendRoute(build(_msgTmp, GATEWAY_ADDRESS, SENSOR_ID, C_SET, V_VAR1, false).set(rssi));
  // 3.b _sendRoute(build(_msgTmp, GATEWAY_ADDRESS, SENSOR_ID, C_SET, V_VAR5, false).set(rssi));
  // 3.c _sendRoute(build(_msgTmp, GATEWAY_ADDRESS, SENSOR_ID, C_SET, I_SIGNAL_REPORT_RESPONSE, false).set(rssi));

              delete [] buff;
            }

not work..

@jkandasa
Thank you very much, I will look forward to it

@jkandasa
Thanks for the answer, there is hope to expect the implementation of these commands in MyController, at least at the level of the configuration file? It shouldn't be that hard to do, and declare the options "experimental"

@jkandasa
This: https://moquette-io.github.io/moquette/documentation.html#_ssl_configuration
https://github.com/moquette-io/moquette/issues/499
http://codewr.com/view/Moquette/install-mqtts-with-moquette-ssl

The various options for moquette described in the myController configuration do not change its initialization..

example:

mcc.mqtt.broker.sslEnabled=true
mcc.mqtt.broker.mqttPort=1883
mcc.mqtt.broker.mqttsPort=8883
mcc.mqtt.broker.websocketPort=7080
mcc.mqtt.broker.allowAnonymous=false
mcc.mqtt.broker.enabledOnBackend=true
mcc.mqtt.broker.sslKeystoreFile=../conf/homediy.jks

@jkandasa

Thanks for the quick reply, but I did not look at the log at the time of adding. Or rather, no recordings caught my attention when I watched it later! With sensor detection and information I tried it, unfortunately the topology hasn't changed. It seems to me that this is due to the fact that the auto gateway is registered in the repeater state. I will check this later.

I have one more question: how to change the built-in MQTT broker to use SSL?
The various options for moquette described in the myController configuration do not change its initialization..
(I guess I'll create a separate question on this topic )

Collected a test circuit from a gateway and one sensor. Hardware in both cases is the same, Vetos d1 r1 + nRF24L01.

I registered the gateway to MQTT myself, the rest was picked up automatically. But, I'm a little confused, because in my opinion everything was determined incorrectly ..
And when testing MQTT topics from an external dash program, the paths of topics look very strange. For example:

gw-out/21/1/1/0/16
gw-in/0/21/1

and the topology doesn't look natural

Sketch Gateway:

#define MY_WIFI_SSID "xxxx"
#define MY_WIFI_PASSWORD "xxxxxxx"

#define MY_DEBUG
#define MY_SPECIAL_DEBUG
#define MY_DEBUG_VERBOSE
#define MY_DEBUG_VERBOSE_RF24
#define MY_DEBUG_VERBOSE_SIGNING

#define MY_RADIO_RF24
#define MY_RF24_PA_LEVEL RF24_PA_HIGH
// #define MY_RF24_ENABLE_ENCRYPTION

#define MY_GATEWAY_ESP8266
#define MY_REPEATER_FEATURE

#define MY_NODE_ID 0
#define MY_BAUD_RATE 115200
#define MY_GATEWAY_MQTT_CLIENT
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "gw-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "gw-in"
#define MY_MQTT_CLIENT_ID "myqw-mqtt-client"
#define MY_HOSTNAME "ESP8266_MQTT_GW"
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 0, 105
#define MY_PORT 1883
#define MY_GATEWAY_MAX_CLIENTS 8
#define MY_SMART_SLEEP_WAIT_DURATION_MS (2000ul)
#define NODE_SENSOR_ID 1

....

void presentation() {
  sendSketchInfo("ESP MQTT Gateway", "1.1");
}

Sketch Fake Sensor:

#define MY_DEBUG
#define MY_DEBUG_VERBOSE_SIGNING

#define MY_RADIO_RF24
#define MY_RF24_CE_PIN D2
#define MY_RF24_CS_PIN D4
#define MY_RF24_PA_LEVEL RF24_PA_HIGH
//#define MY_RF24_ENABLE_ENCRYPTION

#define MY_BAUD_RATE 115200
#define MY_NODE_ID (AUTO)
#define MY_PARENT_NODE_ID 0
#define MY_PARENT_NODE_IS_STATIC

#define MY_HOSTNAME "FAKE_SENSOR_1"
#include <MySensors.h>

#define OPEN 1
#define CLOSE 0
#define CHILD_ID 1
#define NODE_SENSOR_ID 1

MyMessage msg(CHILD_ID, V_TRIPPED);

int cnt = 0;
uint8_t value = OPEN;

void setup() {}
void presentation()
{
  sendSketchInfo("Fake Sensor", "1.1");
  present(CHILD_ID, S_DOOR);
}

void loop()
{
  if (++cnt >= 60 ) {
    value = ((value == OPEN) ? CLOSE : OPEN);
    send(msg.set(value));
    Serial.printf("Set DOOR status = %d\n", (int) value);
    cnt = 0;
  }
  delay(100);
}

Gateway RF:

19125773 RF24:WBR:REG=7,VAL=64
19125776 TSF:MSG:READ,21-21-0,s=1,c=1,t=16,pt=1,l=1,sg=0:1
19125781 GWT:TPS:TOPIC=gw-out/21/1/1/0/16,MSG SENT
19131805 RF24:RXM:LEN=8
19131807 RF24:WBR:REG=7,VAL=64
19131810 TSF:MSG:READ,21-21-0,s=1,c=1,t=16,pt=1,l=1,sg=0:0
19131816 GWT:TPS:TOPIC=gw-out/21/1/1/0/16,MSG SENT
19137845 RF24:RXM:LEN=8
19137847 RF24:WBR:REG=7,VAL=64
19137850 TSF:MSG:READ,21-21-0,s=1,c=1,t=16,pt=1,l=1,sg=0:1
19137856 GWT:TPS:TOPIC=gw-out/21/1/1/0/16,MSG SENT
19143892 RF24:RXM:LEN=8
19143894 RF24:WBR:REG=7,VAL=64
19143897 TSF:MSG:READ,21-21-0,s=1,c=1,t=16,pt=1,l=1,sg=0:0
19143903 GWT:TPS:TOPIC=gw-out/21/1/1/0/16,MSG SENT
19149944 RF24:RXM:LEN=8
19149946 RF24:WBR:REG=7,VAL=64
19149949 TSF:MSG:READ,21-21-0,s=1,c=1,t=16,pt=1,l=1,sg=0:1
19149955 GWT:TPS:TOPIC=gw-out/21/1/1/0/16,MSG SENT
19155988 RF24:RXM:LEN=8
19155990 RF24:WBR:REG=7,VAL=64
19155993 TSF:MSG:READ,21-21-0,s=1,c=1,t=16,pt=1,l=1,sg=0:0
19155999 GWT:TPS:TOPIC=gw-out/21/1/1/0/16,MSG SENT

Sensor RF:

Set DOOR status = 0
19162221 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:1
Set DOOR status = 1
19168276 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:0
Set DOOR status = 0
19174328 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:1
Set DOOR status = 1
19180364 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:0
Set DOOR status = 0
19186403 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:1
Set DOOR status = 1
19192436 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:0
Set DOOR status = 0
19198493 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:1
Set DOOR status = 1
19204541 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:0
Set DOOR status = 0
19210586 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:1
Set DOOR status = 1
19216634 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:0
Set DOOR status = 0
19222695 TSF:MSG:SEND,21-21-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:1
Set DOOR status = 1

Gateway settings:

Nodes settings:

how to be in such a situation?

@jkandasa
This link helped, it turns out you had to choose the .p12 format. Add this to FAQ Senks.

Thanks, it helped, but it does not solve the real certificate issue. Everyone knows how to generate a new one without trust.

I used valid working real certificates and i get error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Client and server support different versions of SSL or cipher suite.

added certificates like this:

"%JAVA_HOME%"\bin\keytool.exe -import -keystore homediy.jks -storepass mypass -noprompt -alias homediy -file mycert.crt

and also made changes to the configuration:

mcc.web.ssl.keystore.file=../conf/homediy.jks
mcc.web.ssl.keystore.password=mypass
mcc.web.ssl.keystore.type=JKS

are there solutions?