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
@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:
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.
@andmaster I have mycontroller starting via crontab and this always works for me, you could try that and see how it works for you. Here on pi3 it is working no problem and every reboot mycontroller comes right back up.
If you can I would recommend replacing the SD card with a SSD HDD. They are quite cheap now (less than £20 in UK) and seem much faster and more stable. I have mine connected to pi via usb adaptor and it is working well.
Another thing to keep in mind is that a good quality power supply and good thick cable from power supply to raspberry pi are strongly advised. Pi seems to be affected by power quality easily. I have been around the block a few times with this!
@jgrieco You may try log raw data from the gateway.
This changes available in SNAPSHOT version
jkandasa created this issue in mycontroller-org/mycontroller
Add raw logs from gateway in a file