Best posts made by Clone Tv
-
RE: Correct way RSSI display in current version
@jkandasa
Senks, unfortunately I have not seen this post, but together we found a way out of this task
Latest posts made by Clone Tv
-
RE: The question is about groups scenarios
it's a shame, it's a pity that there is no such possibility ..
-
RE: The question is about groups scenarios
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?
-
RE: The question is about groups scenarios
Thanks for your reply, this method will do. Is there no way to bind groups to mgtt topics?
-
RE: The question is about groups scenarios
@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 scenarios
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?
-
RE: Correct way RSSI display in current version
@jkandasa
Senks, unfortunately I have not seen this post, but together we found a way out of this task -
RE: Correct way RSSI display in current version
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.
-
Correct way RSSI display in current version
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..
-
RE: how to change the built-in MQTT broker to use SSL?
@jkandasa
Thank you very much, I will look forward to it -
RE: how to change the built-in MQTT broker to use SSL?
@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"