Domoticz

@pjr That was one thing that made it hard for me on some nodes when I was using Domoticz. One of the big ones was my sprinkler node. The node passes zone names and run times using the V-VARx if you use the code on the build page. Because of the fact that at the time Domoticz didn't support those, I had to re-write code for the node to hackishly (if that's even a word) make the three values work.

Personally I'm using the last versions of both the arduino ide and the boards definitions. Also I would expect all of us would be seeing the same problem if that was the case, wouldn't we? Not a big deal for me anyways, the only reason to select the wemos d1 r2 in my case is because I'm using an enclosure designed for the arduino uno which it fits perfectly... But no problem on switching to the nodemcu.

@mfalkvidd First thing one does is to follow instructions exactly and hope things will work out. They don't. You try a different type of connection. Which one? Why one or the other? Which option among the same type? It doesn't work, either. Now, you are thinking, ok this guide is for several controllers, so how do I adapt it for my specific case. The point being, you can't adapt the instructions on your own. You have to ask someone who's done it before and knows what commands to use in order to make Gateway connect to the specific controller. For example: using --my-gateway=ethernet --my-controller-url-address=YOUR-CONTROLLER-ADDRESS will never connect your Gateway to Domoticz. How can one know that this is the line to be modified?

Hi I have coneccted the arduino mega to RPI 3 via usb I can not handle the script on more than one motion sensor #define MY_DEBUG // Enable serial gateway #define MY_GATEWAY_SERIAL // Define a lower baud rate for Arduino's running on 8 MHz (Arduino Pro Mini 3.3V & SenseBender) #if F_CPU == 8000000L #define MY_BAUD_RATE 38400 #endif // 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 #include <SPI.h> #include <MySensors.h> #include <Bounce2.h> unsigned long SLEEP_TIME = 120000; // Sleep time between reports (in milliseconds) #define DIGITAL_INPUT_SENSOR 6 // The digital input you attached your motion sensor. (Only 2 and 3 generates interrupt!) #define CHILD_ID 1 // Id of the sensor child #define DIGITAL_INPUT_SENSOR_2 7 // The digital input you attached your motion sensor. (Only 2 and 3 generates interrupt!) #define CHILD_ID_2 2 // Id of the sensor child // Initialize motion message MyMessage msg(CHILD_ID, V_TRIPPED); MyMessage msg2(CHILD_ID_2, V_TRIPPED); void setup() { pinMode(DIGITAL_INPUT_SENSOR, INPUT); // sets the motion sensor digital pin as input pinMode(DIGITAL_INPUT_SENSOR_2, INPUT); } void presentation() { // Send the sketch version information to the gateway and Controller sendSketchInfo("Motion Sensor", "1.0"); // Register all sensors to gw (they will be created as child devices) present(CHILD_ID, S_MOTION); present(CHILD_ID_2, S_MOTION); } void loop() { { // Read digital motion value bool tripped = digitalRead(DIGITAL_INPUT_SENSOR) == HIGH; Serial.println(tripped); send(msg.set(tripped?"1":"0")); // Send tripped value to gw // Sleep until interrupt comes in on motion sensor. Send update every two minute. } {// Read digital motion value bool tripped = digitalRead(DIGITAL_INPUT_SENSOR_2) == HIGH; Serial.println(tripped); send(msg2.set(tripped?"1":"0")); // Send tripped value to gw sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE,digitalPinToInterrupt(DIGITAL_INPUT_SENSOR_2), CHANGE, SLEEP_TIME); } } This script generates a lot of different sensors in the domoticz and should only two. I don't now why? :( When it erases: sleep(digitalPinToInterrupt(CzujnikRuchu1), CHANGE, digitalPinToInterrupt(CzujnikRuchu2), CHANGE, SLEEP_TIME); `````` It's the same Could you help me with this?

I am sorry, but the problem still exists. Error sending switch command, check device/hardware ! on PKG_SOURCE_URL:=https://github.com/domoticz/domoticz.git PKG_SOURCE_VERSION:=5d708b35d3f6f16d749574f7bf75b2242d47790c and even on last beta PKG_SOURCE_URL:=https://github.com/domoticz/domoticz.git PKG_SOURCE_VERSION:=b4b59b0762a1715d4ecf574ebae060f6a77b9fae

My Debug is for debug, it adds extra info into the serial output and those info are not handled by the controller and it starts acting weird

Ill make backup and try that. Thanks.

@sundberg84 said in Losing connection: mostly about Ethernet GW That's correct

@NeverDie The Domoticz team is not likely to look here, but I moved the thread to the Domoticz category to make it a bit more visible.

@NeverDie said in How to graph datapoints more often than once every 5 minutes?: @rmtucker Which different controller do you recommend? I Am using myHouse at the moment.

@Boots33 Thanks a lot works😊😊😊😊😊😁😁👍👍👍

@arduino_89_89 said in Problem with Domoticz: Hi everyone, I wanted to know how ever whenever the PC reboots, I also change the com port. And why when I break the gateway, are the sensors no longer connected? What environment? Could this help? https://www.domoticz.com/wiki/Assign_fixed_device_name_to_USB_port

Exactly the same as @stefaanv and many others, I started with Domoticz and used it for few years, but after a while it was a bit too much "this script for this", and "this hack for that", and this in python and seven virtual switches for that hack... So I was looking into a more robust solution, and I was sold on presentations that leading people of OpenHAB held online, showing the architecture, the reasons and plans, having clear roadmap and long term plan for the system. I feel I understand how and why openhab works the way it does, why it is organized in such a fashion. And that is very important with any software, to have a good documentation (technical, not just for the users). With domoticz, almost no idea about how it was internally organized, why and what the future plans are. It was always somehow "well this is what we have, it works, and here are the workarounds... with bunch of hidden difficult to find virtual switches and rest api" When I started making more "abstracted" rules about events and logic, then lua showed quite a few challenges, but it was mainly having 30-40-50 virtual switches, a pain in the ** keeping track them all, making rules for each of them (f.eks. switches for datetime: isSunrise, isMorning, isAfternoon, isEvening, isNighttime, isDaytime..... isSomeoneHome, isMeHome, isWifeHome,... ) And this was actually the biggest issue I had with domoticz, handling and organizing the automation part and virtual switches. At the end I had like 6-7 times more virtual switches then physical ones. Then I moved in another apartment and decided to try openhab2. It is just way more robust. It didn't took me a long time to get up and running, and having items defined in a text file is a blessing as you can just do a backup, organize them in multiple files, use git (or backup) for versioning. Writing comments also helps A LOT when you come back to the item after few months/years. Only thing I was struggling a bit is the RFlink, whose binding is not quite ready yet. But I managed to install and use rflink->mqtt "gateway" and all works as expected. I am also using node-red for logic as @Fabien which I am still learning, but so far it looks much much better and easier to debug. Not all challenges from above are domoticz related, some are also "me a rookie" related, so not to downspeak on domoticz, it works great! As long as you are comfortable with all above and dont plan to overgrow it. My goal is to make "smarter home", more then just basic rules and remote home. (about remote home, my.domoticz.com for remote access never actually worked for me, noone could/tried to solve it, so I felt it didn't work) And that is where the community comes in place, it feels that the people on the openhab are more technical, and generally have great technical discussions about best solutions and approaches. F.eks. only for persisting values, you can have multiple completely different database systems, using the advantage of each of them. And each is very easy to install, as they all comply to some "technical rules and documentation". Now that is a downside, as you need to know that you need persistence strategy at all, I wish some would come predefined, but... I am not developing anything, but I feel there are "big boys" who think hard about issues and then develop a long term and best solution for the problem. And I want a stable and long term solution for my home automation, and waf :) On the other side, openhab is a bit more technical, but I think that someone who can change mysensors sketches and make that work, can make openhab work as well. They are very focused on "non-technical" user these days, and it shows with every update. I guess home-assistant is pushing its way forward. (a novel about my life and divorce with domoticz will be published someday, snippet above is just the preview, I have too much caffeine cannot sleep help)

@gohan Yes, they are/were. Alas, case solved... I have lost a line of code somehow. Which in this case meant that presentation was done correctly but these "missing values" were never actually sent, thereby keepin Domoticz from accepting them (seems every parameter to be recognized must actually have been sent once). Anyway, sorry for bothering You and thanks again, Christoph

I will like to know more too.

Sorry guys. Not at home lately. I will report if and what solved my problem when i am back.

Great. I'm adding a link to the other post in case someone stumbles over this thread: https://forum.mysensors.org/topic/7101/domoticz-relay-node-doesn-t-show-up-in-devices/

Not sure how this is handled in Domoticz. On my controller (FHEM) you can also use the "by-id"-path of the serial gateway (or alternatively the "by-path"-path) to make sure you get the rigth data from the right point in system. For getting the necessary info, you type "ls -l /dev/serial/by-id" (linux-console) and most likely you have to enter the entire path for defining your gateway correctly in Domoticz, eg. "/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A901RQ9F-if00-port0" (add the baud rate, if necessary).