Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. qobouky
    3. Topics
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by qobouky

    • qobouky

      Cannot add Nodes trough RS 485
      MyController.org • • qobouky  

      9
      0
      Votes
      9
      Posts
      102
      Views

      jkandasa

      @qobouky You are correct, the Binary type sensors should be visible here. I just revisited your sketch and I found a conflict on the allocated sensors id #define CHILD_ID_HUM 0 #define CHILD_ID_TEMP 1 #define CHILD_ID_CO2 2 #define NUMBER_OF_RELAYS 3 // Total number of attached relays void presentation() { present(CHILD_ID_HUM, S_HUM); present(CHILD_ID_TEMP, S_TEMP); present(CHILD_ID_CO2, S_AIR_QUALITY); for (int sensor=1, pin=RELAY_PIN; sensor<=NUMBER_OF_RELAYS; sensor++, pin++) { // Register all sensors to gw (they will be created as child devices) present(sensor, S_BINARY); } } your relay sensor id should start from 3 or above. I do not see the use of pin=RELAY_PIN. You can present the status of your relay's, that can create V_STATUS on MyController example: #define RELAY_SENSOR 3 // Relay sensor starts at 3 void presentation() { .... MyMessage relayMsg(RELAY_SENSOR, V_STATUS); for (int sensor=RELAY_SENSOR; sensor < (RELAY_SENSOR + NUMBER_OF_RELAYS); sensor++) { // Register all sensors to gw (they will be created as child devices) present(sensor, S_BINARY); relayMsg.sensor = sensor; send(relayMsg.set(loadState(sensor))); // current status of the relay } } NOTE: You have to update your relay code on setup and in receive too
    • qobouky

      MQ135 with RS485
      Troubleshooting • • qobouky  

      5
      0
      Votes
      5
      Posts
      611
      Views

      qobouky

      I found an root cause. In pin definition was #define AIQ_SENSOR_ANALOG_PIN 1 but should be #define AIQ_SENSOR_ANALOG_PIN A1 I do not know why with first definition it worked with nano but did not work with mini.
    • qobouky

      WeMos D1 mini and NRF24
      Development • • qobouky  

      7
      0
      Votes
      7
      Posts
      2519
      Views

      kimot

      @qobouky Use something like ESPeasy for connection your ESP2866 into controller.
    • qobouky

      Home automation - TFT touch display
      Feature Requests • • qobouky  

      4
      0
      Votes
      4
      Posts
      1402
      Views

      heinzv

      I'm on the way to implement something similar with e-paper (without touch at the moment) to save battery. However I will use an additional SPI port and require a lot more flash/RAM as ATmegas provide. Also with the STM32 I'm comming to a limit. Thus I'm switching to an ESP32 barebone module for 3,63€ (4,20$) and habe 4 SPI ports, many I2C ports etc. https://www.aliexpress.com/item/ESP32-ESP32S-WIFI-Bluetooth-Module-240MHz-Dual-Core-CPU-MCU-Wireless-Network-Board-ESP-WROOM-32/32817688406.html?spm=a2g0s.8937460.0.0.xvTLd7 The nice thing with the ESP32 is, that it has 10 touch panel ports on-chip and is very engergy efficient (if used with battery). We had this discussion already and if the bare module is used is has on one hand suffient MCU power as wel as very low engery in sleep/deep sleep. IT has WiFi, BlueTooth, no limits with Flash/RAM etc. Think about it. The best thing: There is a brach or event a planned PR which supports ESP32. See here: https://forum.mysensors.org/topic/9167/esp32-support-to-enable-the-powerful-esp32-rfm95-lora-lipo-battery-boards