What I didn't quite figure out was how it operates independently as a regular light switch. What I find most interesting is that this is 8 years old. There have been some incredible advances in the IoT world in that time. I was about to do a similar thing which morphed into an ESP-12F then added a touch screen. I call it the Universal Light Switch Imagine this: All the switches are identical. Any switch can easily be configured to control up to five devices ... and then changed, on-the-fly, to control a different set of devices. My design is part of a system that would require a controller (eg. Home Assistant), an MQTT broker, and receiving modules in the devices being switched. It's WiFI which assumes an access point. The DIY ULS is under $20 and the off-the-shelf receiving modules are under $10. (About the cost of a non-networked dimmer switch) If one doesn't have the controller and MQTT broker, they can run on an old (5 years?) computer (which is cheaper than an old RasberryPi). This project is a good one! OSD

@OldSurferDude My old 2.0 setup is with nRF24L01 radios. This is a link to the thread on some light switches that I designed and built. https://forum.mysensors.org/topic/7376/us-decora-wall-switch-continued/2 I am aware that you cannot have two MQTT gatways. When I designed my old setup I was not that familiar with MQTT so I never ended up implementing it. On the home assistant server that I have set up though, I have installed the MQTT broker on there so I should be able to comunicate with any MySensors stuff over MQTT in the future devices I make/set up. As I mentioned, I do have a Home Assistant box that I have started about 4 months ago and eventually want to migrate my Vera equipment to the HA box. As for the YAML and Python, I'll muddle my way through. used to program in PHP and have done enough on Arduino that I'm sure it won't hurt my brain too much.

@Michael-Link I have been out of touch with MySensors for some time now and looking to slowly get back into it. I created this and a few other boards back in 2018 All of the GERBER files for this are in the "Design Files" tab. Those you should be able to send to JLC PCB or one of the other fab houses and have some made. This was designed to be used with 2 other boards that I designed. There was the processor board and the power supply board. The processor board was designed in a way that I could use a couple different switch boards. This one and a universal multi-switch board that had multiple configurations. If you look here you will see my other boards.

Hi everyone Which MySensors lib did you use? The 2.3.2 or the delevopment version? I tried to fix the errors, but they don't appear in the development branch. Only another error which i fixed. Regards, Edi

Hi @adds666 I did in between the switch from 2.5.12 to 3.4.4 a change from pure textual configuration in 2.5.12 to a UI configuration in 3.4.4. This requires some homework. Can't remember beside the exchanged mysensors binding files anything else to upgrade to 4.0.4 from 3.4.4 and finally to current 4.1.1. Keep in mind, I use a OpenHAB manual installation on a non-Debian Linux system, not openHABian. This may have an influence, but I don't expect any hiccups. kerberos

@OldSurferDude well, the ESP8266 is limited to 4 TCP clients in arduino IDE. This can't be really increased. I did som experiments and you can set it up to 15, but after the 5th client on my web server, I got a freeze. Maybe you got something wrong. #define MY_GATEWAY_MAX_CLIENTS 2 defines how many controllers (eg Home Assistant) can connect to the gateway, not how many sensors/MySensors devices. And yes, you can have multiple TCP gateways in HomeAssistant. I got an NRF24, an RFM95 long range and a RFM95 short range gateway (all based on ESP32) on the same Home Assistant. Regards, Edi

Just wanted to say thanks for this, it is still relevant and useful six years later !

hey @dirkc, maybe you can trigger your interrupt to rising and falling edge and use millis() to see how long the press was?

@wrendral said in "Remote Irrigation with LoRaWAN: LM27313 Challenges and PCB Design": I will go with a Li-Po Battery type: 304048 3.7V 1200mAh Might work, but maybe the internal protection will trigger with the high current peaks. I'd suggest you plan a 0 Ohm, (2512/THT) resistor as R2 and then replace it with a 100Ohm/1Watt if the protection triggers.

@eiten said in Saving last known good state, but not in EEPROM: utility meter in home assistant This is exactly what I am seeking! Thank you! PS I truly enjoy reverse translating! It teaches me how to better understand my first language and it gives me alternate words to use in searches. So a second thank you! "Regelmässiges Zurücksetzen" would be best translated to English in this context as "Periodic Reset". In the English version of Home Assistant it is called "Meter reset cycle" (I remember seeing "keep dry" translated as "do not take in shower with you"

Hi OSD, thanks for your input. Those are the 4 relays on IO-MCU. I buzzed out the circuit and found that I had an open circuit on the 12v line to the relays. Furthermore 2 of the relays indicator LEDs were illuminating, 2 were not. I suspect, when I first juiced up the circuit on this MCU, the 2 relays fired, but I'd made the trace too thin for the required current. I wired up some jumper wire on the reverse of the PCB and the 2 relays started working. The 2 that remain inoperable? https://forum.arduino.cc/t/using-pins-a6-a7-on-pro-mini-compatible/118050 A6 and A7 can only be analogue inputs, cannot be digitally written to..... - so this part of my PCB is now redundant. However, all in all, some good fault finding, found the two issues, and I'm now going away to re-think my PCB trace widths and reading the datasheets more accurately Thanks

@mimaret It was a pleasure. Thank you for your feedback!

It has been a long time but I’ve learned a few things that I wanted to share. This library of information (Thank you NeverDie and others) has been so helpful in my hobby developments. Software Defined Radios for signal analysis. With the help of Andreas Spiess explanation of IQ transformations, I learned about Software Defined Radios and I bought one (RTL-SDR). Using this I can clearly discriminate between effective 433 MHz transmitters and bad ones. Not only is the signal density displayed on the software (SDR#) but so is the frequency. Power Profiler Kit II has been indispensable in watching power usage and seeing into the details of the radio transmission. In effect this thing has saved me from buying an oscilloscope for my simple little bench. Tonight, I saw this video: https://www.youtube.com/watch?v=Z9nycymUd-I It describes common PCB errors. It is too advanced for me, but I did pick-up a few ideas about ground planes (tip #6 from the video). I hope this is of some value for folks.

What I did not try but might work: copy your persistence file, delete the old GW and create a new one with the persistence file you copied. Maybe the devices are preserved like this. Maybe you should create a full backup before... <edit: typo>

I have success! (oops, that's suppose to be Timer1) I only sample for 1/60 of a second. What I did was to back up all the timer registered I used and then resorted them after I was done sampling. (As opposed to initializing the registers in setup and then starting the timer when needed.) Now I have a Nano sampling the data and sending it to a MySensors Gateway on an RPi3B+ which then sends it to an MQTT broker runing on an old laptop. Also running on the laptop is Home Assistant running inside of VirtualBox. If MySensors does use Timer1, it appears that restoring the registers allows it to be shared. //------------------------------------------------------ISR ISR(TIMER1_OVF_vect){ // interrupt service routine for overflow TCNT1 = TimerPreloadValue; // must be first line! starts the timer counting again digitalWrite(TRIGGER_START_SAMPLE_PIN,HIGH); samplesVolts[--sample]=analogRead(VOLTS_IN_PIN); // decrement before capturing samplesCurrent[sample]=analogRead(CURRENT_IN_PIN); digitalWrite(TRIGGER_START_SAMPLE_PIN,LOW); if (!sample){ // count down to zero digitalWrite(TRIGGER_START_SAMPLE_PERIOD_PIN,LOW); // indicate that sampling is complete samplingEnd = micros(); TCCR1B &= 248; // turns off timer } } //------------------------------------------------------sampleOneCycle void sampleOneCycle(){ // back up timer registers uint8_t TCNT1_b = TCNT1; uint8_t TCCR1B_b = TCCR1B; uint8_t TCCR1A_b = TCCR1A; uint8_t TIMSK1_b = TIMSK1; // configure timer which starts the sampling noInterrupts(); // disable all interrupts TCCR1A = 0; TCCR1B = 0; TCNT1 = TimerPreloadValue; // preload timer //TCCR1B |= (1 << CS10)|(1 << CS12); // 1024 prescaler TCCR1B &= 248; // turns off timer? TIMSK1 |= (1 << TOIE1); // enable timer overflow interrupt ISR // demark sampling sample = NUMBER_OF_SAMPLES; // count down to zero digitalWrite(TRIGGER_START_SAMPLE_PERIOD_PIN,HIGH); samplingStart = micros(); TCNT1 = 65535; // first trigger right away! TCCR1B |= 1; // turns on timer interrupts(); // enable all interrupts // wait for sampling to be complete while(digitalRead(TRIGGER_START_SAMPLE_PERIOD_PIN)){}; samplingEnd = micros(); // restore timer registers TCNT1 = TCNT1_b; TCCR1B = TCCR1B_b; TCCR1A = TCCR1A_b; TIMSK1 = TIMSK1_b; }

After re-installing the previous 32bit raspbian version, the gateway seems to work ok. It seems to me there is a problem with the 64bit version.

Just for completeness: the right way to do this is to add the json under ~/.platformio/boards and the other files as described in https://community.platformio.org/t/how-use-a-same-chip-but-with-different-environment/18082/4

true, but I see in practice pjon is handling collisions more efficient

@ctodor You are very welcome

Hm, maybe the problem is that your rPI has a short interruption in the WIFI connection, the MQTT TCP connection is interrupted and does not autostart again. Maybe there is something in the logs. Maybe you can find something about reconnects in one of these: journalctl --unit=systemd-networkd journalctl --unit=wpa_supplicant You could try to run wpa_cli in daemon mode to react to disconnects and connects. Create a script like this: #!/bin/bash case "$2" in CONNECTED) <your command to start the gateway>; ;; DISCONNECTED) <your command to stop the gateway>; ;; esac then, start wpa_cli in deamon mode: wpa_cli -a /path/to/your/script #use sudo if your gateway commands need sudo If that helps, you could create a service from this command. Regards, Edi

IT WORKS I got a first working version, using an ATmega1284P running on MightyCore 2.2.2 (as soon as I began developement, they switched from Optiboot to Urboot in version 3.0.0, whicht does not include the copy_flash_pages function anymore, but I'm working on a work around there). Only thing I could not solve is to do a CRC check of the image after download... You can try it out here: https://github.com/eiten/MySensors/tree/FOTAInternalFlashTest It's not beautiful yet with much Serial.prints in it, but maybe it helps you if you find errors.

We are of like minds, Don't like the cloud based controls (that's another discussion). In my case I have a Bryant/Connex system, heat pump, variable speed fan and 4 zones. There's a lot going on: the 4 zones creates 16 profiles. The fan speed for a profile will depend on the indoor and outdoor temperature. The thermal fluid pump also has to be controlled. A profile will have an optimal air pressure, so there's a sensor there. The controller works just fine not being connected to the cloud. But I want to set the parameters remotely, Bryant/Connex can do this. I also wnat the status of the various actuators and sensors to show up in Home Assistant. The signals sent over the RS422 are proprietary. My plan was to reverse-engineer the signals. After doing this I'll have to experiment to get the right mix of air pressue, fan speed and thermal fluid flow for each profile. I'd like to do the same for my AO Smith heat pump water heater. I'd like to follow your progress. OSD

I bought the Every because it implied it was backward compatible with the nano. No, it's not, as we found out. Be that as it may, any word on a getting the Every working with mySensors?

Don't ask me why, but now it works. I changed nothing! Went to my girl over the weekend, coming back, the node was registred. Maybe a jammer went away?

Hi @CyborgAndy many thanks for providing the binding update for MySensors 4.0.4! I upgrade my OpenHAB 3.4.4 a few minutes ago to 4.0.4 successfully with your binding update. I use a USB connected serial-gateway. The OpenHAB manual installation upgrade works perfect. I need to do afterwards the following steps in the Karaf console, to get the gateway online again, after the update: feature:install openhab-transport-serial feature:install openhab-core-io-transport-mqtt feature:install openhab-core-io-transport-serial-javacomm Many thanks again! kerberos

@Mizar03 sorry for the late response. getStream() only works for firmware transfers. I'd suggest getString(), this should also work for all types of payloads, as they are normaly ASCII and not binary data.

@eiten I haven't yet made any progress on finding a good VOC sensor, but along the way I did find out something interesting regarding CO2: namely, if you sleep with your bedroom door closed at night, then the odds are good that the CO2 levels rise to surprisingly high and unhealthy levels. The better CO2 sensors are factory calibrated and never again need recalibration for the life of the sensor (usually around 10 years or so), because they are used in HVAC systems to control fresh air intake to guarantee indoor air quality. As a for instance, here is one such CO2 sensor: https://www.digikey.com/en/products/detail/senseair/006-0-0008/15790694 At around $50 for just the sensor element itself, it's not exactly cheap, but then again, I'd say it's worth it, because who wants to be burdened by remembering to calibrate their CO2 sensors? Ideally, I'd like to find a sensitive VOC sensor that also will never require calibration. Nearly all, and maybe all, of the off-the-shelf IAQ montoring stuff that you might buy for, say, $300 or less seems to require periodic calibration. For that reason, this might be one of those occasions where build is rather than buy.

I don't know if any of you guys are still around and using this stuff - I moved and am reviving a few of these 51/52 boards that I had built. Prior to moving I had decent luck with all these fixes though I don't quite remember where I was with any of this stuff seeing as it was 3 years ago. I had a few motion sensors and some temp/humd based on these fixes and they were working great, no dips. Not sure any of you will ever see this but hey it all worked.

I found procedure gatewayTransportInit(), it works great. However, I cannot find a procedure that will enable detection of a network connection at level mysensors. I noticed that disconnecting the network plug or resetting the W5500 (37 pin to ground) changes the device's IP address to 0.0.0.0 - then I call gatewayTransportInit() - but mysensor's library must have such procedures - please tell me how to diagnose ethernet connection.

hello, I just deleted the eeprom but I still have the problem.

Solved. Issue with power supply. Added a capacidade to power source.

You should only include the relevant header file in the file Gestion_Porte.hpp, not Mysensors.h For example #include <core/MyTransport.h>

@nekitoss I used 3.3V pro mini with regulator removed and powered by Vin pin. Also removed leds from the pro mini. I used minicore bootloader. I used the small pir sensors and again removed the regulator to power directly from the pro mini outputs. After that sleep the node and trigger on interrupt. Send battery level once a day. Use inbuilt battery level monitor and not external components that constantly drain power to get battery level. 1.8V is 0% on the graph (not visible yet!) but I have had nodes working below 1.7V It's a matter of luck with that it seems. Hope this helps you on the right track. I'll try and help if you want. This is the latest image and still going strong after 18 months. Voltage is at 2.903V Here is photo of the test example - I need to make a case and produce more of them over winter..... Here is the same build/code of a window sensor. Similar time frame but hardly triggered.....

Hi all, Should anyone face the same problem, I found the root cause: brownout threshold. I burned a new bootloader (Optiboot 8.0) without such trigger and the node has been working with used batteries (~2.7V) since May. Hope this helps.

I'm afraid, the MYSbootloader is only available for the AVRs.

I deployed 5 sensebender nodes just after release in 2015, all with 2 AA batteries from ikea.1 died within a couple of years, because it was placed outdoors. But the rest kept going, and all have been going until this year. So 8 years of battery time on one set of batteries.. I think that is excellent battery life..

Search should be working again now. Sorry for the inconvenience.

Thanks for the quick response. Yep! When I updated the IDE I forgot to modify the settings (915 MHz) in the new myconfig.h file. Doh! All good now.

Of possible interest: Here's a guy who is building an inexpensive open source ethernet controller for stepper motors: What happend to Ethersweep? Project Update! – 12:36— Neumi If you listen to the end, it's revealed that there is now generous funding available which allows people to do this kind of open-source development as a full time job, which is what he is now doing. For that reason, I think there's a good chance he will complete his project within the allowed 6 months., and so by the deadline it will likely be nicely polished.

@skywatch said in Awesome tip: run LinuxFX instead of Windows!: @NeverDie Thanks - Interestingly they show a free version on their site still. Did they revert due to bad publicity? https://www.linuxfx.org/ I stopped following it, but I seem to recollect that the free version was noticeably missing things--otherwise, who'd buy the paid-for version? Anyway, its standing on Distro-watch has fallen considerably. It may seem unfair to niche distros, but I think it's generally better to stick with the more popular distros, unless you have good reason to choose otherwise.

Some humidity sensors are known to lose accuracy with age. For instance, the Si7021 is known to have this problem. If that matters to you, then the best choice is to pick sensors that have datasheets and which have specs as to their expected longevity or accuracy over time. Then buy from mouser/digikey to be certain you're getting the real thing rather than factory rejects or counterfeits. For extra insurance, I avoid electrolytic capacitors entirely whenever possible. I buy only 7XR rated ceramic capacitors that are overspec'd. The difference in price is small compared to a failure down the road.

@Matt Yes, the landscape there is incredible. Unfortunately, I mostly have to work when I'm there Where are you from?

No. For RFM69 you need Sensbender bootloader and external flash. Then it works.

Its seems to be working with this last sketch https://github.com/paolo-rendano/MySensors/blob/c01e14d0942de68126d67325a0687b1a6ce4fa16/examples/WaterMeterPulseSensor/WaterMeterPulseSensor.ino need some time to test it thanks

@monte thanks, did it!

@Dan-Mincu Hello I am looking for help because I have the same problem. Can you show me the code you use to set power down radio?

Same issue here. HA receives data from Ethernet Gateway for only a few minutes and then: DEBUG (MainThread) [mysensors.gateway_tcp] Connection lost with <_SelectorSocketTransport closing fd=42 read=idle write=<idle, bufsize=0>> I also have MYSController connected to the GW and it remains connected. There is an open issue as others are also having the same problem. Am wondering if anyone here is having success with Ethernet Gateway connected to HA.

The output of the display could also be sent over serial, but the whole idea is you can walk around with the doctor and improve your results as you go.

@Matt Yes, I was going to suggest this

Thank you @eiten for you suggestion. I will try it. I wanted to be independent from HA, just as a fail safe in case of problems. I am not relying on the time keeping of the arduino, but on a real time clock module.

Hi, I create a rflink pcb with this schema . I have an emission issue, the module RF 433Mhz Out not have 12v in VOUT+. What could I need to do. This is the pcb design, maybe it needs some improvement. Thanks

Hello everyone, Firstly, I apologize for reviving such an old thread, but I find myself in a unique situation and was hoping some of you might be able to help. I hope everyone's doing well. I have a specific inquiry that I couldn't find a recent solution for. Does anyone here know of a tool to generate "fake" Dooya remote (DC90) RF codes for curtains? I've acquired a few motors without controllers and am trying to integrate them with Home Assistant and Bradlink RF remote. Specifically, I'm searching for a way to generate codes for the Up, Down, Stop, and the "Set" button functions to configure curtain limits. Any insights or guidance would be immensely appreciated. Thank you so much in advance!

@Tmaster Never assume the original PCB was just a circuit of components, the PCB can incorporate RF shields and antenna radio ground planes...

@zboblamont OK, so experiments concluded that the return data from the latest version of Domoticz is a String whether it be V_VARx or V_TEXT. I tried the dual declaration using the same CHILD_ID as intended and as VAR_X (using an RF24 - not sure of the relevance) and the actual value sent but failed to make any sense of abstracting the Ulong conversion or the string. Only by presenting a fresh CHILD_ID and duplicating the send of data (water meter) as a V_VAR1 could I recover the last sent reading as a V_VAR1 from that fresh CHILD_ID, thence eventually arriving at 'strtoul' as a solution to restoring the last known value. For clarity my Gateway and Controller run on a UPS, and I hope shortly to add the spare router to that UPS so I'm not left in the dark on what is happening in the dark on a battery powered laptop... Hope this helps others trying to keep track of meters between relentless power cuts and reboots...

@Tmaster What I meant by my previous comment was to tap on the Node name to see what sensors were connected - Had you clicked on TANQUE you would have seen a box pop up below giving you all the children to that particular Node with what value was last updated and when, so you could easily have found out all about your mysterious 13 children. At least you have it sorted now, but it pays to do a bit of housekeeping in the sketch setup and Domoticz - eg which of the 6 "Unknown" Nodes is the one you want to next have a look at ? All my Node IDs are set at the Node, and the sketch name labels the Node ID also, the Nodes are named in Domoticz for easy identification. In the sketch my sensors are numbered sequentially and commented on what they are, so naming them in Domoticz becomes very much easier.

Only if you send a correct message from the controller to the node the receive function is called. I don't see a receive in your log. I think in your case the receive-function is not called (or called with a wrong message type or node id). Put a serial.print("receive() is called with type "); serial.println(message.getType()); on top of the receive function to see if the receive function is called and which type is handed over..

I am sharing my sketch. Based on the sketch below, I am using this led light to show air quality status (good for green, normal for yellow and bad for red). This sketch is just a switch so you should make some automation in HA. https://www.amazon.com/Traffic-Display-Module-Arduino-Mini-Traffic/dp/B07SZMRSDN #define MY_DEBUG #define MY_RADIO_RF24 #define MY_NODE_ID 16 #define MY_RF24_PA_LEVEL RF24_PA_LOW #include <MySensors.h> #define CHILD_ID_GREEN 1 #define CHILD_ID_YELLOW 2 #define CHILD_ID_RED 3 #define GREEN_PIN 3 #define YELLOW_PIN 4 #define RED_PIN 5 bool greenState = false; bool yellowState = false; bool redState = false; MyMessage msgGreen(CHILD_ID_GREEN, V_LIGHT); MyMessage msgYellow(CHILD_ID_YELLOW, V_LIGHT); MyMessage msgRed(CHILD_ID_RED, V_LIGHT); void setup() { Serial.begin(115200); pinMode(GREEN_PIN, OUTPUT); pinMode(YELLOW_PIN, OUTPUT); pinMode(RED_PIN, OUTPUT); wait(200); } void presentation() { // Initialize the MySensors communication sendSketchInfo("Traffic Light Node", "1.0"); present(CHILD_ID_GREEN, S_LIGHT); present(CHILD_ID_YELLOW, S_LIGHT); present(CHILD_ID_RED, S_LIGHT); } void loop() { // Send initial values of the LEDs to the controller send(msgGreen.set(greenState ? 1 : 0)); send(msgYellow.set(yellowState ? 1 : 0)); send(msgRed.set(redState ? 1 : 0)); // Other tasks in the loop if needed // ... // Add a delay to control how often the initial values are sent delay(5000); // Send initial values every 5 seconds (adjust as needed) } void receive(const MyMessage &message) { // Check which LED to control based on the message received if (message.sensor == CHILD_ID_GREEN && message.type == V_LIGHT) { greenState = !greenState; // Toggle the state digitalWrite(GREEN_PIN, greenState ? HIGH : LOW); // Set the pin accordingly send(msgGreen.set(greenState ? 1 : 0)); // Report back the new state } else if (message.sensor == CHILD_ID_YELLOW && message.type == V_LIGHT) { yellowState = !yellowState; digitalWrite(YELLOW_PIN, yellowState ? HIGH : LOW); send(msgYellow.set(yellowState ? 1 : 0)); } else if (message.sensor == CHILD_ID_RED && message.type == V_LIGHT) { redState = !redState; digitalWrite(RED_PIN, redState ? HIGH : LOW); send(msgRed.set(redState ? 1 : 0)); } }

i use the simplest boxes that you find,that suface mount with 4 screws and ruber on door. But be carefull with wall mount screws. if you drill the back of the box ,water come in beind this box. so this ones,the scrfew holes are outside the encosure an box is sealed... another tip is drill on bottom for pass cables but put some neutral silicone. hot glue let water come in with time because expansion coeficient is diferent that the plastic box and open gaps

Thx for the hint. Unfortunately this didn't help me to find a solution for the compilation error. I simply don't understand the lines 105 and 106 in (MyHwLinuxGeneric.h). Can anyone explain me the C magic going on there? #define ATOMIC_BLOCK for ( ATOMIC_BLOCK_CLEANUP, __hwLock(); \ __atomic_loop ; __atomic_loop = 0 ) I think the problem is the "new"/different compiler version being used on the OrangePi 5. On my Raspberry Pi the code compiled without any problem.

@mfalkvidd Thanks for the reply.

Hello@jemish Yes, it is possible to create a smart water level detector for your home water tank using an ultrasonic sensor or a float switch connected to a microcontroller with wireless connectivity.

Hi all, Should any one need, the fix mentioned in this page actually works. Thanks,

Could you share the capacitor values?

thanks again Edi. I will first make a full backup and put it on a new ssd. after that i will test your solutions as far as i can. sorry, i must have overlooked the code snippets function. best regards

Just for reference, as this solution was no yet mentioned: You could also use a second UART on your controller or a software serial for debuging with the following defines: #define MY_SERIALDEVICE Serial // Interface for controller connection #define MY_DEBUGDEVICE Serial1 // Interface for debug output Regards, Edi

Hi Monte! May you please post your sketch? Thank you very much, edi

If the message is retained, it will show up already when you connect MQTT explorer to the broker, without HA sending a message yet

@Multimax do you send initial states for all children for this multi relay node? HA won't show anything that hasn't sent initial data to show. https://www.home-assistant.io/integrations/mysensors/#presentation

Depending what's connected to a relay, I wouldn't make it go on or off depending on the controller state. It can lead to dangerous behaviour and it's prohibited by law in my country. In all honesty I have my Sensors running for a long long time. It's stable and more reliable than anything else I have running in my home. But like @eiten says yo could write a sketch that queries for a variable. But I think I'd go for a controller side solution. That would "ping" my node and send a nottfication to my phone whenever the node can't be reached.

@TheoL that's not the dimmer's fault a far as I am concerned. It behaves the same way at full brightness. It's just a cheap chinese driver in it.

Error establishing a database connection

Hi dzairo, Just wondering if you still monitor this thread. If so would love to know how to install the ComPort component so I can modify and use your terminal code. For some reason I don't have any luck with adding it to the IDE. thanks, Andy.

@Kokosnoot good solution. I remember the discussion in the early days of MySensors. I've powered the radio's for most of my sensors from the 3.3v regulator on the arduino board and for me that works perfect. But for my latest designs I decided to add a separate ams regulator for my radio's like the guys suggested in the beginning. Because you basically want the on board regulator to power the mcu only.

@adds666 I'm not sure but I believe Domoticz prresents it's dimmer values in steps from 5 to 100 I believe. It'd about 10 steps. That's why I'm not sure if you can add more patterns. Unless you indeed change it to a percentage. Hope it helps

@pbw a gateway's function is to act as a gateway between the nodes and a controller. I don't think you will have all of the needed memory available to add logic to the gateway and you will make your solution very static. You can implemented your own lightway controller, just have a look at the Serial API. But controllers like Domoticz are lightweight and the already over a browser based interface. And most of them are easy to setup creating a much more versatile and dynamic solution.

@DeepCore That is a need looking design. Did you consider using an alternative power supply other than usb? My Pi can't handle a lot of usb devices power wise, so I'm using a powered usb hub. But the wife doesn't like it, it's messy xd

@bach It does look really great! As far of resistor divers I'm not much fan of that. There are several other options, like a logic level converter circuit with FETs. If I have all 3.3V devices connected to an mcu I prefer to use a 3.3v mcu. Like an esp2866, but I'm still waiting until the irq support on the esp2866 gets available. For me the nrf24's are still working great and I have a stacked up a lot lol. I'm however experimenting with the rfm's. As I need a bit more range to reach the end of my backyard.

Thanks for the response. Can you be more specific about how to request the status from the node? My understanding is the request format is: request (Child_ID, VariableType); But if the Home Assistant entity that I want to request the status of is not a MySensors entity it will not have a Child_ID. So how do I format the request statement?

So @Greg-Bowers .... you found the flaw? hello @jkandasa ..... a little parenthesis! ( what's new in MyC ) https://github.com/mycontroller-org/server/releases/tag/development

I searched on the forum how to use ID255 but found nothing practical https://forum.mysensors.org/topic/8941/mysensors-get-temperature-value-from-another-node-through-the-gateway?_=1684325843882&lang=fr https://github.com/mysensors/MySensors/blob/development/examples/PingPongSensor/PingPongSensor.ino

Very useful topic for me, thanks. Even though it's been a long time, the information was useful to me. And especially the information on the link you sent.

Supposedly PIR doesn't work through glass (e.g. if looking for motion through a window), whereas I presume a microwave sensor might still work.

^^^This. Good point. Maybe do some testing with RadioLib to see whether or not you experience the same problem.

Thanks for sharing!

I am new in this forum and I have a question regarding mysensors and iobroker. I did not work with mysensors up to now. Since some weeks I use iobroker installed on a raspberrypi. Now I want to integrate my 433 Mhz doorbell in iobroker. I know, that there is an adapter for mysensors in iobroker. My question is: Is it possible to get a notification in iobroker if someone is pressing the button on my doorbell? As I understood, I have to connect the receiver to an arduino nano and connect the arduino to my rasberrypi on which iobroker is running.

@gerritv Thank you for pointing the problem. I was updating my code, while library was updated and found that i had funtion, that does not exists in library - i've added it in local copy in library, then it updated and my local patch was gone. I've investigated previosly mentioned PR - and must admit that later they removed that re-initialisation when reading. I will try a PR to slightly improve that behaviour, but looks like library is becoming abandoned. Now look it should work next way: after previous measurement done you must run lightSensor.configure(ONE_TIME_) so it starts measuring - this is shown in their example BH1750onetime.ino. Then we have to wait, but measurementReady() relies on _delay_ms, which (as i remember) won't tick during sleep so you can't sleep. We can sleep but we can't get exact measurement time for current settings. Soto save battery we sleep max time - which, according to library is 180ms. Then we get reading. On next cycle - repeat. As i understand maximum battery saving code will look like: void setup() { Wire.begin(); // Initialize the I2C bus (BH1750 library doesn't do this automatically) lux_init_status = lightMeter.begin(BH1750::ONE_TIME_LOW_RES_MODE); //init ONE_TIME - at same time it will start measuring, but we will ignore this and double-call start measuring if (lux_init_status == false) { send(deb_msg.set("ErrorInitLux")); //notify us about failure } } void loop() { if (lux_init_status) { //making it fail-safe - if BH1750 brokes then other sensors will still work lightMeter.configure(BH1750::ONE_TIME_LOW_RES_MODE); //this will start measuring, after it sensor will go into power-down mode //note, that configure has 10ms sleep built-in sleep(180); //this is guarantee time in this library with any config. We can't get that externally as for v1.3.0 long lux = lightMeter.readLightLevel(); //actually get results } sleep(SLEEP_TIME);//sleep between measurements } note that .configure() that is also called by .begin has built-in 10ms delay

That's the point, i don't see important part which change with or without my_core_only. I think i miss something

First let me say that the test "network" consists of a single node and a Serial GW with a Domoticz controller only. No repeater nodes are present and it operates at 250Kbd on a frequency outside of the WiFi spectrum verified to have no traffic. The test subjects are within 10 feet of each other and the protocol sniffer receiver is placed roughly midway between the two communicating nodes. The test node has a plugable connector for the RF modules so that I can switch them out separately. The GW has the LNA/PA module and the node is using the standard mudules. Both GW and node are set to "High" power. Looking at the problem with the promiscuous protocol sniffer and wireshark I can clearly see that packets collide mid air when both the node and the GW transmitting at the same time. This happens when the controller/GW talks to the node while having the protocol ACK request enabled and the node does not have the extra wait/delay programmed. Going through 12 RF modules node side, I can see that about 1/3 shows the problem consistently to the extent that all 16 retransmissions are used up , 1/3 to various degrees and the rest shows no problems at all. Before you say "ohh fake chips etc." these modules all came from the same batch, so more than likely not fake and non fake, but rather some parameter that the lib assumes to tight of a margin for. When turning off the protocol level ACK via the controller/GW, the package goes out without an request for the node to send back the package, only the HW ack remains in the picture. Setup like this I can see that the third of the modules that cause the persistent collisions evoke a re-send of the package by the GW after ~2 to 2.5ms , while the group that shows no problem shows one single transmission from the GW only. Since the sniffer is not fast enough to capture the quick turn around ( spec says 130us) for the short HW ack to go out I can not get say whether the node is simply not sending it or just not sending it in quick enough. All I can say is that the GW code did not see a HW ack and therefore sends out the package a second time. Meanwhile on the node side all is well, it just might get the same package twice and since no status changed there is no harm done. However when you now turn on the protocol level ACK request in the controller ( as you should) the node has to turn around and send out the echo package which then collides with the resend of the original package from the GW. The node also doesn't get an HW-ACK becasue of this and tries to resend the echo package over again until it runs out of tries. When I then introduce the wait/delay in the code above to wait out the 2.5Ms for the GW to resend the initial package this ACK/resend storm goes away because the air is clear when the node sends it's echo package. If I wait/delay for 2 ms the problem is greatly reduced and if I wait 3 ms I see no more evidence of collisions. Either wait or delay works however, I choose delay() to be positively sure that no other communication is started during that time by the node. I conclude that as a work around this solves the issue we are having with the RF24 transport, but without further investing into faster RF sniffing equipment I can't say for sure if this could be solved better on the TX side by waiting longer for the HW ack to arrive from the receiving node, however I think there would be a good chance for that. There is also a chance that the PA/LNA module used on the GW could be part of the problem by not being able to switch quickly enough back to RX mode and therefore loose the HW-ACK for nodes that respond quicker than others. Edited: Checked with a non PA/LNA module on the GW and no change could be observed, so this theory can be discounted. BTW: All of this is very reminiscent of an email communication in 2015 I had with Ekblad !! GS

thanks for the feedback

@mfalkvidd No, the issue with sleep(0) still exists in V2.3.2. That is the version that the ArDuino Library installer installs currently . -- Work around is to call hwPowerDown(WDTO_SLEEP_FOEREVER) as in above code if you want the battery to last more than a day. GS

Solved by adding a short delay between the RX/TX turnaround when replying with an ACK message. In file MyTransport.cpp at line 706 in the "if (msg.getRequestEcho) block, right after the debug message "TSF:MSG:"ECHO REQ" added a 2ms delay to allow the caller to switch from TX to RX mode. GS

Great! I'm glad it works and thank you very much for reporting back!

@GaryStofer Okay, then sounds like you're doing what I would. Are you able to turn on debug and connect serial to it to troubleshoot that way? Without getting more info on it, I'm out of ideas at the moment.

I had the same problem with "Emakefun LGT-RF-Nano für Arduino Nano V 3,0 RF-NANO LGT8F328P Integrieren NRF24l01 + Micro USB Nano Bord mit Antenne Interface" Using the default Compiler the Serial Messages were not working properly. I used this https://github.com/nulllaborg/arduino_nulllab Board Package and it worked(at least the serial issue). The rest I still need to test. I hope this helps some hours of trouble.

@monte said in Replace 2.4GHz remote controllers: "Mysensors fonctionne selon son propre protocole et ne prend en charge aucun produit commercial" yes the beginning of a track can be useful for you ? https://github.com/Yveaux/NRF24_Sniffer https://arduino.stackexchange.com/questions/39348/decoding-2-4g-rf-remote-controller

And just to add a clarification, do not modify MyConfig.h. Put the define statement into the sketch for your node (somewhere before line: #include <MySensors.h>), and don't forget to modify your gateway code as well. 0

Working great! Thanks very much!

I will answer myself after some testing done today: How can I change network id for gateway (mysgw)? It is possible to change MY_RFM69_NETWORKID for mysgw by exporting CPPFLAGS variable with the option set before running ./configure: example: export CPPFLAGS='-DMY_RFM69_NETWORKID="101"' ./configure --my-gateway=serial --my-transport=rfm69 --my-rfm69-frequency=868 --my-is-rfm69hw --my-serial-is-pty --my-serial-port=/dev/ttyUSB-MysGW --my-serial-groupname=dialout make Is it possible to create another RFM69 network on new hardware, just for the test, while my current RFM69 network keeps running on current gateway/controller? As soon as I started another RFM69 gateway (mysgw) on new hw, even with different network id (101), most of the sensors connected to my other (production) gateway running on old hw with default network id (100) stopped communicating... so it seems it is not possible to run multiple RFM69 gateways in the same range (on the same freq).

https://github.com/sandeepmistry/arduino-nRF5 Install this and find libraries for whatever sensors you have on that board. @basaksts said in nRF5 Multi Sensor Board (12-14€): Also I need an bootloader No, you really don't. You need ST-Link, or J-Link SWD programmer/debugger. Connect it to SWDIO, SWCLK, 3.3V and GND and program it using Arduino IDE.

Well, search seems to be broken again on the site. Hopefully a dev will see this come across their screen and know how to fix it. I searched the site for "multiple definition" and 'premain' but neither one got ANY hits, even this topic itself! So if you tried to search the site to see if anyone else had had this problem before, it wouldn't have much chance of success. Anyway, all that is to say that we've run into this before. I'll link below here the thread where I managed to get around it. I'm not sure if there were other threads, but this one should give you some info on how to fix it for yourself. I could find this by going into the history of posts I had made, since search was failing me.... https://forum.mysensors.org/topic/10193/stm32f103c8-problem-at-compilation

It's an awfully convoluted way of doing things but suspect your error lies in misunderstanding calculations mixing ints and floats and something screwy with your resistor bridge - It is always worth checking the bridge with a multimeter and raw voltage to verify the expectation. If you have 3v at the top of your voltage divider, you should be getting 0.9593v applied on the ADC pin which will be read as 892 against the 1.1v internal reference. The easiest way I found was to define a multiplier needed to derive the raw voltage, in this case (((R1+R2)x1.1)/R2) - For your resistor arrangement the max you can read is 3.4404v before exceeding the 1.1v internal reference. To reverse the ADC reading of 892 to raw voltage is (892x3.4404)/1023 = 2.9984 v. Perhaps this is a simpler way to do it float MULTIPLIER= (((1000+470)*1.1)/470);//Resistor bridge values in k and Vref int sensorValue = analogRead(BATTERY_SENSE_PIN); float batteryV = (sensorValue * MULTIPLIER)/1023.0; //Note the trailing decimal point on the 1023 for calculations involving floats

i had my answer on ahtxx issue Hi, ...figured out that the _address is messed up (i guess by mysensors). It is impossible, because _address is private variable. The private data members cannot be accessed from outside the class (mysensors can not see it). Сan you try my original library but with class initialization line AHTxx aht10(0x38, AHT1x_SENSOR); //sensor address, sensor type

super, once again a few super links, thanks for that i will go for the easy way. this sketch by boots33 works perfectly. But before that i will try to understand and learn the steps. thanks again branther

I have encountered the same situation trying to use a switch to control some blinds. Has there been any update on this issue from either Home Assistant or MySensors, or any workaround developed?

Hey vivek101 how did you connect the NRF24L01 to your home assistant server? Normaly, you connect the nRF to an microcontroller and flash it with a gateway sketch. Then you connect the uC to your server... Regards, Edi

@Branther Thank you for your feedback!

Hello this is Gulshan Negi Well, to connect with an accelerometer, you typically need a device that can communicate with the sensor and send its data to your PC. The specific device you need to use will depend on the type of accelerometer you have and its communication protocol. Thanks

yes, absolutely. i always order all my components from aliexpress. i don't think it makes any difference which dealer i use there. you can be lucky and sometimes not sometimes you can tell right away, for example an NRF module didn't have an IRQ. sometimes you have to search specifically to get the nrf24l plus model for example, which is different from the normal nrf module. in germany the parts are 3-4 times more expensive. so i put up with it. if you have several components, you can swap them and limit the error. thanks again

Please read carefully documentation for HA. https://www.home-assistant.io/integrations/mysensors/ You need to send initial state of your sensors. There is example code for doing it. Basically you check in loop if the node just started and send some values to HA. After that your sensor will appear in HA.

what the ratings are of the two capacitors used in your circuit? A 1000 uF and a 100 uF?

hi electrick, thank you for the hint, i'm so glad that someone finally talks to me Yes i reached the same conclusion about power supply of the nrf24 board. 3.3V pin from nano can only deliver 50mA when e01-ml01sp4 needs 120mA. I redesigned my project including a ams1117 between nano's 5V pin and the radio board https://forum.mysensors.org/topic/12109/nano-e01-ml01sp4-gateway/4?_=1679247873047 next episode when i'll receive the new pcb !

Yes, this is a good idea. but not with an ethernet switch/hub, only an ethernet crossover cable. ?? https://copperhilltech.com/wt32-eth01-serial-to-ethernet-module-based-on-esp32-for-iot-applications/

OK problem found. Found out that when I selected "Blackpill F411CE" board before code compilation everything were ok. Usually I am choosing generic types so I used "F411CEUx" in case of blackpill 2 and I found out that generic types has different default "Serial" pins in ST core. Now I can confirm that Bluepill , Blackpill and F4VE board are working with MAX485. ST core v 2.4.0. ../.arduino15/packages/STMicroelectronics/hardware/stm32/2.4.0/variants/STM32F4xx/F411C(C-E)(U-Y)/variant_generic.h // UART Definitions #ifndef SERIAL_UART_INSTANCE #define SERIAL_UART_INSTANCE 2 #endif // Default pin used for generic 'Serial' instance // Mandatory for Firmata #ifndef PIN_SERIAL_RX #define PIN_SERIAL_RX PA3 #endif #ifndef PIN_SERIAL_TX #define PIN_SERIAL_TX PA2 #endif ../.arduino15/packages/STMicroelectronics/hardware/stm32/2.4.0/variants/STM32F4xx/F411C(C-E)(U-Y)/variant_BLACKPILL_F411CE.h // UART Definitions #ifndef SERIAL_UART_INSTANCE #define SERIAL_UART_INSTANCE 1 #endif // Default pin used for generic 'Serial' instance // Mandatory for Firmata #ifndef PIN_SERIAL_RX #define PIN_SERIAL_RX PA10 #endif #ifndef PIN_SERIAL_TX #define PIN_SERIAL_TX PA9 #endif So be carefull while using ST core and generic type of STM32.

Correct, me too. I've set in my profile, weekly digest, so it's only weekly, but always twice. I observe this behavior already for months. @mfalkvidd, do you have an idea why?

yes also here (France) there is still some person with the mask, a remnant of the trauma?

@dhanushmh Here is my project using mySensors and LoRa modules for sensors around a farm. https://farmer-eds-shed.com/?s=lora

I mean the ESP framework version, selected by the board version https://arduino.esp8266.com/Arduino/versions/2.0.0/doc/installing.html#:~:text=Open Boards Manager from Tools,from a drop-down box.

@karlheinz2000 Sorry I missed your original post. I've used the WhiskyDelta code successfully for gateways using the 401 and 411. Glad you found it.

@monte said in Boards esp8266 v3.1.0 or Newer Doesn't Work with MySensors: il existe tellement de solutions bon marché et faciles pour ce que font mysensors as rich in possibilities as this does not exist

@scalz I have just updated to MySensors 2.3.2 and the sketch with interrupts stopped working. Any changes in any lib?

Anyone tried this with RFM69HCW? I got it compiled on Arch Linux ARM with the aarch64 linux-rpi kernel after editing ./configure and hal/transport/RFM69/driver/new/RFM69_new.h as described above. [root@alarm git]# cat /proc/cpuinfo | grep Model && uname -a Model : Raspberry Pi 4 Model B Rev 1.4 Linux netberry 6.1.11-2-rpi-ARCH #1 SMP PREEMPT Tue Feb 14 06:34:59 MST 2023 aarch64 GNU/Linux It runs, but doesn't communicate with the radio properly: [root@alarm MySensors]# ./bin/mysgw Feb 16 13:20:45 INFO Starting gateway... Feb 16 13:20:45 INFO Protocol version - 2.4.0-alpha Feb 16 13:20:45 DEBUG MCO:BGN:INIT GW,CP=RPNGL---,FQ=NA,REL=1,VER=2.4.0-alpha Feb 16 13:20:45 DEBUG TSF:LRT:OK Feb 16 13:20:45 DEBUG TSM:INIT Feb 16 13:20:45 DEBUG TSF:WUR:MS=0 Feb 16 13:20:45 DEBUG RFM69:INIT Feb 16 13:20:45 DEBUG RFM69:INIT:PIN,CS=24,IQP=22,IQN=25 Feb 16 13:20:45 DEBUG RFM69:PTX:LEVEL=5 dBm Feb 16 13:20:45 DEBUG RFM69:DUMP:Registers Address | HEX value Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x01 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x02 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x03 Value=0x1a Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x04 Value=0x0b Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x05 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x06 Value=0x52 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x07 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x08 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x09 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0a Value=0x01 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0b Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0c Value=0x02 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0d Value=0x92 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0e Value=0xf5 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0f Value=0x20 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x10 Value=0x24 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x11 Value=0x9f Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x12 Value=0x09 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x13 Value=0x1a Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x14 Value=0x40 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x15 Value=0xb0 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x16 Value=0x7b Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x17 Value=0x9b Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x18 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x19 Value=0x86 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1a Value=0x8a Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1b Value=0x40 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1c Value=0x80 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1d Value=0x06 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1e Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1f Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x20 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x21 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x22 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x23 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x24 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x25 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x26 Value=0x05 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x27 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x28 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x29 Value=0xff Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2a Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2b Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2c Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2d Value=0x03 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2e Value=0x98 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2f Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x30 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x31 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x32 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x33 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x34 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x35 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x36 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x37 Value=0x10 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x38 Value=0x40 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x39 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3a Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3b Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3c Value=0x0f Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3d Value=0x02 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3e Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3f Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x40 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x41 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x42 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x43 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x44 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x45 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x46 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x47 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x48 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x49 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4a Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4b Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4c Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4d Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4e Value=0x01 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4f Value=0x00 Feb 16 13:20:45 DEBUG !RFM69:INIT:SANCHK FAIL Feb 16 13:20:45 DEBUG !TSM:INIT:TSP FAIL Feb 16 13:20:45 DEBUG TSM:FAIL:CNT=1 Feb 16 13:20:45 DEBUG TSM:FAIL:DIS Feb 16 13:20:45 DEBUG TSF:TDI:TSL Feb 16 13:20:45 DEBUG RFM69:RSL I have built commit aa520cea, the latest from the development branch, using this config: ./configure --my-gateway=ethernet --my-transport=rfm69 --my-is-rfm69hw --my-rfm69-frequency=868 --extra-cxxflags="-DMY_DEBUG_VERBOSE_RFM69 -DMY_DEBUG_VERBOSE_RFM69_REGISTERS" My hardware should be fine, i didn't change anything and it was working with the 32-bit kernel before.

Hi, friend! He also became interested in the Home Assistant system, but was upset by the lack of support OTA. I use a system Majordomo for MySensors devices and my Ethernet-RS485 gateways are based on ENC28J60. And I found such an idea for myself - to implement a proxy for the TCP protocol in order to implement a parallel connection to the gateway of two systems at the same time. I tested this solution and it turned out to work - I was able to flash via OTA , while simultaneously receiving data in Home Assistant. Perhaps this idea will be of interest to you.

I finally got this to work. Unlike what the description here says, this is how to update the value: In Home Assistant, go to Developer->Service->YAML mode: service: text.set_value data: value: "967067" target: entity_id: text.water_meter_100_2 (change 967067 with the value you want to add to the current counter) The service "notify.mysensors" seems to be deprecated by Home Assistant.

@isded from what is explained in this page it seems it is based on the Semtech SX1278 : https://www.makerfabs.com/sx1278-lora-module-433m-10km-ra-02.html

@mrhutchinsonmn I'm not an expert on this code and when I get into a situation like yours, I suspect a corrupted file. So I download the MySensors code again. Yeah it's a pain because you have it all configured. To minimize that pain, I create shell script to run the the configure program. I also keep my source files in a different directory from MySensors. When I go to compile the code, I copy the source(s) to the directory(ies) to where "make" expects it(them). Sometimes, for me, I've bolluxed things so badly that I reimage the RPi and really start over! I try to document exactly how to start over. I admit, it's not efficient nor elegant, but I eventually I get a configuration with which I can live. Documenting what I do is key!

a line of the examples given in the sketches for the use of RS485 can be a source of problem (it's my case, I use Pin2 or3 for a long time ) ... // Define this to enables DE-pin management on defined pin #define MY_RS485_DE_PIN 2 (2 or 3 is an interrupt pin for a Uno) ... avoided interrupt pins. the pin 10 is a good thing

... compiled: Jan 27 202312:42:11 01/27/2023 12:42:11 RTC lost confidence in the DateTime! RTC is the same as compile time! (not expected but all is fine) 01/27/2023 12:42:11 19.25C 01/27/2023 12:42:14 19.25C -------- power loss ----- RTC communications error = 4 01/01/2000 00:00:00 0.00C RTC communications error = 5 01/01/2000 00:00:00 0.00C.. ------------- return power supply +5v ---- RTC lost confidence in the DateTime! 01/01/2000 00:00:12 19.50C RTC lost confidence in the DateTime! 01/01/2000 00:00:15 19.50C ... https://forum.arduino.cc/t/librairie-makuna-freez/1081415/34

Yes, comment #define MY_DEBUG and in setup() add Serial.begin(115200);

The short answer is no. Regular battery chargers are designed to deliver higher constant voltage to the battery charging it much faster, however the trickle chargers deliver a slow charge to your battery and are designed to be left on your battery for extended periods of time.

I've purchased the family plans for both LastPass and Bitwarden. I'm torn between the two. I've been alternating back and forth between using them and I much prefer LastPass. Family sharing in Lastpass is vastly superior and easier to use. Bitwarden does family sharing in a clunky and disjointed fashion. Family sharing of some sites is especially important to us. My wife is not technical at all and has learned to effectively use Lastpass over the last 12 years. I've not even shown her how Bitwarden works yet, and I know what her response will be.

Reporting back: I have my BambuLab X1C printer setup and have printed with it for about a week. It's fantastic: it's fast, and the prints come out perfectly every time. Truly an appliance: it works with only minor setup straight out of the box. I'd say it's a quantum leap better than my Prusa MK3S, which I guess I should try to sell while it still has value.