Best posts made by Mickey

Im starting to upgrade all my sensor nodes to use mysensors library after a ling time just using nrf24network with my own star topology implementation:

I design my own board to put the pro and radio and use the tuner transfer method.

Hi
I made this boards as small as I could and would like to operate them on 3v coin battery - CR2032.


I check them all and the range is excellent (more than 15 meter and behind 3 brick walls)
but they will run out of power quite soon with this battery so what is the simplest and fastest way to change the arduino fuses so it can run down to 1.8v.
If there is a need for external flash I have this one(is it good?):

Hi
I see in the git repo that there are 2 bootloaders:
Bootloader
MYSBootloader
Do I need to burn one of them to use MySensors ?

However if someone has a good proposal for how these kind of batteries are best used with the Sensebender Micro I would like to know also.

mcp1702 for example...

@Sweebee said in arduino pro 3.3 + nrf24l01 smd onboard + On board 4K-Bit Flash memory:

@Mickey Nice, can you show the inside of the box?

Thanks a lot...
I already create a MYSController and GW + 2 NODES but your explanation made things much clearer especially the OTA part.
Do you plan to publish MYSController source?

and again I really appreciate the detailed step by step guide.

Hi
I want to develop a node that need to save some data to local node eeprom. but I wouldn't want to erase the node id and other params that the mysensors library saving.
how much room is available for my node ( arduino pro mini 328 ) and from where can I write to eeprom without erasing anything?

Hi
I would like to alter GatewayESP8266MQTTClient.ino a bit to be able to transfer mqtt broker connection params from an HTML5 app I developed.
I altered the core code in the file MyGatewayTransportMQTTClient.cpp to enable SMARTCONFIG:
WiFi.beginSmartConfig();
To be able to transfer the SSID and PASS dynamically from the app.

All the other params(server IP, user/password for MQTT broker etc.) I would send from the app with JSON and the GATEWAY will save them to local storage (the ESP-12 have 4mb for storage).
I do not want to alter core files too much and would like to implement all of the above in the ino file as much as I can.(with the smart config option I didn't see a way other than altering the MyGatewayTransportMQTTClient file.)

The MyGatewayTransportMQTTClient file looks for defined variables to function but I need to change the code to enable dynamic params.

The parameters I need to change are:

#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway1-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway1-in"
#define MY_MQTT_CLIENT_ID "mysensors-1"
#define MY_MQTT_USER "username"
#define MY_MQTT_PASSWORD "password"
#define MY_ESP8266_SSID "MySSID"
#define MY_ESP8266_PASSWORD "MyVerySecretPassword"
#define MY_ESP8266_HOSTNAME "mqtt-sensor-gateway"
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68
#define MY_PORT 1883

I know how to code the ino file to listen to JSON and then process the data and put it in storage but I cant seem to grasp how to change the core file as minimally as I can...

@hek said:

Why pass it to the sketch? You could implement the id-handout directly in core (I pointed out the area where internal messages directed to the node is processed).

To mess with core as little as I could so it can be easy upgradable in future (I already altered the MyGatewayTransportMQTTClient.cpp to support using dynamic connection parameters instead hard coded , I don't want to alter a lot of core files but if it necessary I will...)