@OldSurferDude yes, you are correct. this sensor is capable of 50A continuous, which safely I would make it working at 40A max., but for such an important load as in your case I would go for a beefier one, like the ACS75x, 77x, but at this point I would also change the node's form factor for space and insulation reasons. On my application on the RV I have a max. curr. of 13A running on a AWG14-16 cable (European rules for RVs), so I did not ask myself too many questions beside, of course, safety. About the signal, it will be a sinusoidal signal swinging around Vcc/2. Vcc can be easily measured internally on the ATmega328. On all my DC sensors I measure Vcc at every loop, just before measuring the ADCs. Honestly, when the space is not an issue like in my RV, I would rather use a ring core current transformer, and I would get rid of noise, response time, power dissipation, but over all no need to cut any cable. Long story short, it has been a nice experiment and I used it for 6 months, and then I switched back to my RF-NANO based RS485-Modbus - Mysensors bridge connected to an off-the shelf power analyzer. Just for fun I attach a pic of my 12Vdc sensors installed on my RV. Forgive me for the spaghetti wiring on the right side, but this is an area that needs improvement. [image: 1723442333591-img_20231008_120026-resized.jpg]

@OldSurferDude thank you !

@HJ_SK said in 2x BME 280 on 2x arduino nano hangs in HomeAssistant: BME280 I had a similar situation. First you have to delete all the MySensors devices in HA. This is aggravated by HA wanting the devices to be on line before you delete them. You may have to delete the MySensors data in the HA config directory. You may even have to uninstall MySensors from HA. Then shutdown HA. Next, turn off your gateway. Are you using MQTT for messaging? You'll have delete the MySensors data from there, too. (MQTT Explorer is good for doing this) Then start HA. Did your MySensors devices come back as zombies? That's the problem. Try deleting them again. Are they data still in MQTT? OK, now start again. I had documented how to do all this deleting in HA Forum, HA/Discord and here, but I can't find that documentation now. grrrr OSD

Hey @OldSurferDude I think we have a missunderstanding here. I have my gateways running on ESP32. When I add the integration I can enter the IP in this dialog: [image: 1721934496526-2024-07-25-21_05_25-einstellungen-home-assistant-mozilla-firefox.png] If you want to change the IP number of the gateway (or the MQTT topic or the serial port), there is no way to do this: [image: 1721935167535-2024-07-25-21_18_03-einstellungen-home-assistant-mozilla-firefox.png]

Thank you @JeeLet ! I've been struggling with missing msgs for years with my Arduino Mega I changed pin and no issues! :D In the pjon code I've reached to list of tested pins that communication works properly https://github.com/gioblu/PJON/blob/38e36bb1228c1690143cfbf693a0bcb809514d6c/src/strategies/OverSampling/README.md?plain=1#L12

Nice work so far @wint0178, great that you try expanding on the examples. Sorry for the late reply. If you look at https://github.com/mysensors/MySensorsArduinoExamples/blob/bba998bce09bc5139eb4ca7a05b0279f4083ff88/examples/PressureSensor/PressureSensor.ino#L90 you see where the existing child ids are defines. You just add another one for the gas sensor, with a unique number (incrementing by 1 is an easy way). Try that and report back on your result. If something is unclear, just post a followup.

No, it does not recover. The Problem is not easy to debug. I now want to build a serial gateway. With that, I am more flexible to test. Maybe to run MySensors on a second raspberry pi with a standard Home Assistant HASS-Os image. Or I check the MySensors network with MyController. At this moment i run the whole system on 64 Bit raspbian, with HA in docker, which is a little bit experimental and i had to fix some lines in the ethernet gateway to compile it for 64 bit. So this is experimental, too.

@bgunnarb I like @eiten 's solution for you. Personally, I am not a fan of using cloud/public brokers. Thus I am curious about your system and there is something about it from which I can learn. I would like to understand why you cannot deploy your own mosquitto broker. I see your set up as 3 sensor groups defined by the channel used #define MY_RF24_CHANNEL ChannelOfSensorGroup Each sensor group has some number of sensors and one MQTT GW on ESP8266. On the MQTT side, do you distinguish between gateways by using a different host name? Something like: #define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway-nOf3-out" #define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway-nOf3-in" #define MY_MQTT_CLIENT_ID "mysensors-nOf3" #define MY_HOSTNAME "ESP8266_MQTT_GW_nOf3" //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68 #define MY_CONTROLLER_URL_ADDRESS "test.mosquitto.org" #define MY_PORT 1883 I must assume your controller (aka Home Assistant) discriminates between through which gateway the data is to flow by way of the different topic names. If my "something like" is correct, then changing brokers is changing the IPaddress/URL in your gateways and in your controller (though if the controller is Home Assistant, it may be a bother because the device-id's may change which will make a mess of all the work you've done in HA. This is why I like @eiten 's solution.) I hope it's all working for you again. OSD

@eiten Ran into the same error but of course the community is always at hand, ready to help! Great! I'm using MySensors 2.3.2 release version. Downgrading the ESP8266 board library to 2.7.4 as suggested by @OldSurferDude did the trick. I'm still clinging to MySensors. So simple and inexpensive to use! All sensors and other stuff connects over three MQTT GW in three locations back to my Home Assistant. PS: Get well soon! Regards, Gunnar

Hi2All! Surprising is here. After about 24hours I refresh HA and suddenly my motion sensor was integrated. There is also second entity > battery : 0 , have to look deeper into that for understanding. Need to change little in the sketch, because don't want every short time 'no movement' so only when there is motion and maybe once a hour indication sensor is alive. Meantime I found 3 other good threats: https://forum.mysensors.org/topic/11200/finally-progress-evidence-based-radio-testing-method-and-capacitors https://forum.mysensors.org/topic/1664/which-are-the-best-nrf24l01-modules/27 https://forum.mysensors.org/topic/9550/build-a-reliable-power-supply-chain Very usefull for me also finally progress because of lacking time in the past. Great jobs are done here! Thanks for this all of you guys or girls!

@OldSurferDude Thanks a very valued to know. I was wondering today why my (big) powerbanks fall down after short time. I have small 1 & 2-pieces powerbanks, they work very well. I use also BSM hw-168 or hw-107 for charging single 18650. Will try to use them outside also with small solarpanels.

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 @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