Skip to content

MyController.org

77 Topics 663 Posts
  • Connecting NodeMCU 1.0 Gateway to WiFi

    1
    0 Votes
    1 Posts
    7 Views
    No one has replied
  • influxDB et Grafana

    1
    0 Votes
    1 Posts
    16 Views
    No one has replied
  • Fields Mysensors

    9
    0 Votes
    9 Posts
    93 Views
    J
    https://forum.mycontroller.org/ integration of motioneye in MyC Base OdroidC2/Armbian buster et Cam arducam (libcamera) :clown_face:
  • French Version

    1
    2 Votes
    1 Posts
    25 Views
    No one has replied
  • Widgets météo

    1
    0 Votes
    1 Posts
    23 Views
    No one has replied
  • Cannot add Nodes trough RS 485

    9
    0 Votes
    9 Posts
    114 Views
    J
    @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
  • serial, Ethernet to MQTT

    serial ethernet mqtt bridge converter mycontroller
    5
    1 Votes
    5 Posts
    56 Views
    J
    @Yveaux said in serial, Ethernet to MQTT: Of course, but MySensors MQTT gateway runs just as fine when connected over cabled ethernet, as when connected over wifi I do not know that :) Now on this tool, I do not see much benefit from ethernet to MQTT ;) Still, it is good from serial to MQTT.
  • 1 Votes
    4 Posts
    58 Views
    alexeliteA
    Gateway >> Node >> Device >> Metrics Nodes have devices attached and each device has metrics.
  • Java version for MyController?

    2
    0 Votes
    2 Posts
    35 Views
    J
    @Alexandr-Kazakov Try with this start.sh file https://github.com/mycontroller-org/mycontroller-v1-legacy/blob/0f473bafb729baf5551829daa5f838eec9df4384/dist/src/main/package/bin/start.sh
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    5 Views
    No one has replied
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • V 1.5.0 stability problem solved (my fault!)....

    1
    1 Votes
    1 Posts
    30 Views
    No one has replied
  • MyController Forum Registration

    4
    0 Votes
    4 Posts
    64 Views
    J
    @chrispy @mfalkvidd sorry for the inconvenience. I didn't notice it. I have enabled search option for guests.
  • Where to send messages about battery charge and signal strength?

    12
    0 Votes
    12 Posts
    174 Views
    C
    Yes, I found :) It may be useful for those who might come across this issue later: Git MYCONTROLLER repo Code for sending RSSI from loop function. It is not necessary to announce (present) the RSSI sensor. MY_CRITICAL_SECTION { char *buff = new char[18]{}; (void) snprintf(buff, 17, "rssi:%d", rssi); reportMsg(getId(), V_VAR5, buff); delete [] buff; }
  • Setup problem

    2
    1
    0 Votes
    2 Posts
    46 Views
    skywatchS
    @Skysurfer14 I am not totally sure what you have done, so this might help you get more help. The sensor is connected to what? Post the gateway code so we can see what is happening there. Your debug shows that the node cannot find the parent (gateway) and therefore fails. Again, how it is all connected (drawing, photo) would help.
  • Momentary output command to node

    2
    0 Votes
    2 Posts
    31 Views
    F
    Also, ideally, moreso very necessary, the momentary needs to be sorta snappy, as I am planning on connecting to a starter circuit on the generator, so which is why i was thinking more at the node built into the sketch as opposed to the controller, due to lag times in data to/from node
  • Hi everyone newbish question here

    6
    0 Votes
    6 Posts
    81 Views
    F
    @kimot Yeah, but mainly this is more proof of concept. If this platform works for what I am trying to accomplish, I may just go mesh and start migrating to mysensors/mycontroller
  • React on other MQTT messages possible?

    8
    0 Votes
    8 Posts
    584 Views
    rejoe2R
    @trs-80 Imo it's not as easy as comparing (or even just counting) some fancy pictures to really make a judge on the "most integrations" issue :grinning: . As a FHEM-user (without OpenHAB experience thouhg), I'd state there's at least three or four big systems missing (on the picture collection): HomeMatic / HomeMatic-IP, 1-Wire (it's more than DS18B20 :smirk: ) and EnOcean. All of them are supported by FHEM, and additionally a lot of "special" stuff (like RS485 protocolls and many others). To get an impression, the commandref is a good starting point). Additionally, there exist a lot more "innofficial" modules for whatever purpose... So in fact, I've seen quite a few people leaving FHEM in the past (it requires quite some familiarizon) and coming back to it, also from OpenHAB for it's flexibility. Also the level of comfort may vary from integration to integration. So I'd state, there's not THE nor perfect answer to the question which controller supports the highes number of integrations :stuck_out_tongue_winking_eye:
  • Using an 802.11g wifi transport

    9
    0 Votes
    9 Posts
    2k Views
    FotoFieberF
    @mfalkvidd said in Using an 802.11g wifi transport: @eveningstariot If you have wifi, the MySensors library adds almost nothing to your project. Connect your wifi devices directly to your controller, using mqtt or whatever protocols your controller supports. MySensors was the starting point for me to build my own parts for home automation. It is more than a library: active community inspiration for new projects an API which I more or less transferred to a generic API for other sensors (zWave, homematic...) I have reduced the usage of radio based sensors (only one active sensor left) and sometimes I get blue, that mysensors has no real solution for my WiFi-based sensors. The solution with one gateway per WiFi node is not appealing. (No auto discovery, many endpoints to one controller...) I switched to MQTT (without mysensors) and direct REST-API calls. But it feels a little bit clumsy. :(

19

Online

11.7k

Users

11.2k

Topics

113.1k

Posts