Topics created by jocke4u

@Sasquatch Thanks, it was a connection issue with HomeAssistant to MySensors GW. Now it is time to clean up the sketch and put it to operation again. Also thanks you other guys that have been helpful @mfalkvidd @Yveaux @niclas

@jocke4u yes that is correct, both gateways will also need to be using different channels as well.

@jocke4u I run 2 RF gateways and it's not a problem. When you 'migrate' a node to a new gateway make sure to run the mysensors clear eeprom sketch first to get rid of the old routing table or you might have issues.

Thanks @electrik for the update I got it running. However I think I should make some work on the sensors. As it seems the Ethernet GW are running 2.1.1 but I think the sensors are running 1.5.x (seen in MysController) But I get plenty of : 2020-05-28 19:29:47 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:30:22 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:30:57 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:31:32 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:32:07 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:33:17 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:33:51 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:34:26 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:35:01 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:35:36 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:36:11 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:36:46 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:37:21 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:38:31 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:39:06 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:39:41 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] 2020-05-28 19:40:50 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload'] Trying to get my dev environment correct to be able to recompile. EDIT: Since it have been so stable for a long time I am not up to date with the Arduino environment. My experience from the past is not without issues

What about something like this: https://www.cooking-hacks.com/projects/arduino-realtime-gps-gprs-vehicle-tracking

@jocke4u The moisture example could be used to detect leaks This project on openhardware: https://www.openhardware.io/view/534/Extremely-Simple-Arduino-Pro-Mini-LoRa-Water-Leak-Detector The following forum threads might be of interest: https://forum.mysensors.org/topic/1761/water-leak-detection https://forum.mysensors.org/topic/9070/water-leak-sensor https://forum.mysensors.org/topic/7736/water-leakage-sensor-using-thin-ribbon-cable-testing-reliability/ https://forum.mysensors.org/topic/4651/my-basement-flooding-alarm

I read other messages about OH not responding to variable state requests, it looks like a "feature"

Without any evidence - yes. I have not made that much tests yet since I waited for my logger. I have made some posts about this on the forum. I dont want to make any conclusions yet. @gohan

Thanks - works just fine

Mo ha ha... I will take over ALL your sensors.

I hope it's resolved I had some extra hardware so bought a genuine Arduino Uno R3 which I assembled temporarily. It seems to work just fine. Different main board and different network card (still w5100). The old gateway:

@axillent thanks and what is the smd coil that you use?

@hek said: It won't work if you previously had AUTO enabled and have received an id. This id will be written to eeprom. But If you always had a static id for a node this means no id has been written to eeprom and you can still go back to AUTO to fetch a new id. For a node that HAS received an id and you want to receive a new id for some reason, you have to use the clear eeprom example which writes 0xFF to the id-position of eeprom again. This allows node to fetch a new fresh id from controller in AUTO mode. I always use nothing but static node-ids and I'm unable to re-include working nodes to my Vera without first erasing the eeprom. The sensors "new parent"-debug message isn't showed until after this either. Is this correct?

I'm just curious. What is the benefits and difference between a Lux and Photosensitive sensor?

Good to see there are also MQTT client libraries for Arduino (Part 2) Parts 3 and 4 are about a controller / graphing solution. For sure nice, but I personally like to keep my data on my devices.

@hek Yes I know about setVariableIfChanged preventing to set unchanged Vera variables but I log all setVariable calls (unless childId or serviceId is null) and have not seen this with serial GW so I thought Ethernet GW was sending duplicate messages.

@gregl said: i think on mine the solder pads are bridged... but i will check. I am pretty sure it's the same (5V as default) for me but will double check.

@jocke4u said: I have used this code: gw.begin(incomingMessage, AUTO, false, AUTO, RF24_PA_LOW); Since the PA parameter is the fourth one, you need to set the ones before (but go with defaults for the ones after) Yes, the MySensors configuration design is to set the unified configuration parameters in MyConfig.h to ensure common sensor configs (.e.g. channel) across sensors but then override on a per-sensor basis as needed.

Great, thanks for info

@ServiceXp you said in this post: That was it!!!!! I tried 22uF, was still doggie, so I thought why not move up to 47uF wink and what do you know, that seems to be the winning value. I have some more testing, but looking pretty good so far. This sounds to me that the issue is solved... I can imagine that 1.4 requires a bigger cap while 1.3 doesn't. 1.4 uses auto acknowledge which can send burst packets. This could put a bigger load on your power supply.