@skywatch @sindrome73 This is what I do, too. Note that it is wait(), which is a MySensors function and not delay(), an Arduino function. wait() checks for MySensors messages, delay() halts all process, thus a message might be missed.

@mfalkvidd A while ago I tinkered with Media Wiki running on a docker. If I remember correctly you can set access for authors moderators etc. But I forgot, I need to spin that docker up any time soon anyway. Because it contains my network documentation and I need to update it. I'll let you know.

@OldSurferDude So if I get my circuit to work, that would by 22 times less (on average). Well I'm doing too many things at the same time. :)

You don't check for which sensor the message is send - message.getSensor() - and in both cases you set the relays both on Like Skywatch said. So you could do something like: if ( message.type == V_STATUS ) { // check if GW send a status change if ( message.getSensor() == sensor 1 ) { // handles sensor 1 } else if ( message.getSensor() == sensor 2 ) { // handles sensor 1 } ... etc }

I did a grep on the source code and found this snipper #if defined(MY_GATEWAY_ESP8266) || defined(MY_GATEWAY_ESP32) // Turn off access point WiFi.mode(WIFI_STA); #if defined(MY_GATEWAY_ESP8266) WiFi.hostname(MY_HOSTNAME); #elif defined(MY_GATEWAY_ESP32) WiFi.setHostname(MY_HOSTNAME); #endif #if defined(MY_IP_ADDRESS) WiFi.config(_MQTT_clientIp, _gatewayIp, _subnetIp); #endif /* End of MY_IP_ADDRESS */ (void)WiFi.begin(MY_WIFI_SSID, MY_WIFI_PASSWORD, 0, MY_WIFI_BSSID); #endif MySensors uses the standard ESP libraries for this. So I expect it to work. But you need to provide at least a bit of source code. Right now it's hard to answer your question. Regarding to MySensors: A HTTP hostname can only be set for Gateways that either use Wifi or Ethernet For nodes you can provide a sketchname and that will be seen in your controller. Regarding to static non static IP addresses. I prefer to use DHCP and set that device in my router as a static IP. There I also give it another hostname. So that in case I have to replace my Gateway I can do it all in the router. Hope this helps. But please provide more info on what you're trying to achieve

we’ve been using Triton detectors at my school for a while now, they catch both nicotine and THC vapor fast and it sends an alert right when someone vapes, even picks up small amounts. it’s probably the closest thing you’ll find for what you need.

@goblin feel free to share concrete error messages or questions. We might be able to help on well-described problems. Otherwise - hope ChatGPT can help you ;-)

MySensors is an EXCELLENT project. It allows for complete control over the various sensors. It's extremely simple. Its drawback is that it's open source, so it's unfunded and development is slow, but I don't think there are any better projects than this at the moment.

@tnick I know this is an old post, but if it helps you - I've created support for STM32 based on latest STM32duino here. It's currently made to be backward compatible for the existing STM32F1 support, which is what you are struggling. But with a small change you can use the new STM32 HAL support. Let me know if you are interested to give it a try. The longer term plan is to remove the existing (old) STM32F1 support in favor of the new and more general STM32 support. (If @mfalkvidd agrees ;-))

Did it work before or is it a new build?

@Vuinne-Ryvmar You seem to be confused about what this forum is. Maybe you just ended up here on a random Google search? But in our case on an Arduino, D3 is literally the name for one of the metal legs coming off of the little controller, and we call it a pin sometimes. @tbowmo was looking for how to send the command to turn the power on or off to that part of the board, not a code to enable connecting up a controller to their phone. I see that a D3 game controller is a thing, but I doubt you will have any luck getting help with that here. It's not what this site is about. This is what we work with: [image: ArduinoUnoFront.jpg]

Hello I still didn't figure it out exactly, what is the issue with LGT8F328P and arduino, but for start, it can work, if you define 4x faster baud rate. So I define MY_BAUD_RATE 76800 and connect terminal with 19200, and it works. LGT is started in 8 MHz by default, and it looks like this is not corrected with mysensors. But this only helped for serial port, because later I had issues with DHT library timings. If I later change speed to 16 MHz and start serial port again, it works as expected: noInterrupts(); CLKPR = 0x80; CLKPR = 0x01; interrupts(); Serial.begin(19200);

as I experienced, MQ sensors are not really gaz sensitive, they are more particle size sensitive when hot enough and when not totally scrap. I would not rely my life on them, if you have an alcool spray use it around and any MQ will to go the sky...

I like the joke : ) I'll try to keep it simple. Most of my sensors are just reporting temperature and humidity. Since I can assign them to a room in home assistant. They don't need anything fancy.

@sebastieng Thanks for letting us and future readers know. -OSD

Thank you so much for your support

@jaydenlord Probably you do. If you leave the EN floating, electrical noise could cause it to enable or disable randomly. Some enable pin require a HIGH, some LOW. Connect it to VCC to see if it works more consistently. If it doesn't detect, connect it to GND. If one of these works, then the part wasn't designed to be in a default state of enable. Let us know your results (I found this video OSD

Hi everyone, bumping this thread because I could read some of you were interested in packet loss (@NeverDie and someone else) and my findings could help fix it partially or completely via software. It's certainly a hardware problem, though I can't figure out if it's due to the components physical positioning, the power supply, or both (and/or more issues like wiring, proper PCB traces, etc). Also, even the same modules from the same manufacturer, say EByte E01 PA+LNA modules in my case, have shown different performances, so it might be something bound to the variability of the SMD components used as well. Let's get straight to the point. I am the developer of rf24tunlink, a radio network bridge which uses primarily nRF24 modules. During R&D, I found that around 30% of packets from my modules were dropped due to a couple corrupted bytes, which was constant even in close range. That does indicate a hardware problem already, but the distribution of the bit flips is an even stronger indicator. [image: eb505750-d741-45b2-aba1-57d26913c786] All flips are in the first bytes! You might be getting at least one flip in most packets, resulting in ALL of them being dropped automatically because this invalidates the CRC. In this scenario ShockBurst can fail, or you might get duplicates, might not get ACK payloads or simply get a slow link because the same packet can be sent up to 15 times with a wait between each retry. Not coming here unarmed: how to fix it? Easy in principle, you: Disable CRC -> ShockBurst off, no ACK payloads, essentially your module will be RX only. Implement RS ECC: sacrifice just enough bytes to fix all the corrupted bytes. (in my case, 2/32 was enough!) That's how I turned a 30% packet loss into a 100% flawless reception, see this result: [image: 43bcccb9-9b9d-4ae8-ac4b-c9ed1f8fc320] There is more to it, as the link gets worse, of course this situation also gets worse. Finding out how many errors are in a packet can help you estimate signal quality and potentially take preventive measures. Now, if you only care about sending a specific packet, you either receive it or not at all and that's it. But if you want more like I did, then things get more complicated. In this case I wanted a full duplex link -> a second pair of nRF24 modules was mandatory I also wanted to send network data (iperf, ping, ssh, realtime video, audio, telemetry, control, anything really) -> frames needed to be split into radio packets, sent, corrected and stitched back into a frame. That is a HARQ algorithm. After all of this, I could get a usable network speed of 1.2Mbps (determined via iperf). Used a Pi 4, Pi zero 2 W and 4 nRF24 PA+LNA modules. You could use this same metric to evaluate your components, some modules could do better and some could do worse. Would be cool to fix this hardware for all and get closer to that 2Mbps max speed. Some people declared a speed of 1.7Mbps and I have seen a 1.5Mbps peak during development, so there is definitely room for improvement. [image: 1bd38d37-7a09-49e1-b92b-7d0838d1c436]

Are you still able to use the same analog phone plugged into the back of your modem? If so then it has to still use the same protocol, and I don't understand why the analog beacon wouldn't still work. It would just have to be on that same wire, not on the internet side of the modem. The modem is doing all of the translation in that case. Or am I missing something? Did you have to get a new phone to use the new service?