Hi @berkseo. Thanks for the suggestion, but could you describe in more detail? As for my TODO list, there is already a task to add 485 interface to the gateway. My latest device "xRoom" have this interface.
ps/ Where have you gone?
I have been working on "xRoom" shield. A small announce:
Do you remember the discussion about multinode? So, it will be available soon))
@scalz
in the second test i used that getting started code to test the radio modules with a library other than mysensors. and they worked. (That code is not mine, i suppose it use the maniacbug library).
So i did investigate to find the differences between mysensors and that library. Only after replacing, in mysensors, the enablefeatures with that code, i got the communication gw-node.
@NeverDie Yes, you are correct - it is based on ATMega1284P. So not relevant
My point is that I'd rather stick to the datasheet rather than overclock, but that's just me. And yes I realise that Moteino is overclocking, but the size, voltage and flash are really appealing to me.
Still, there seems to be 'someting rotten in the state of Network' where my LAN is concerned. Although the Arduino serial monitor says:
13:03:55.821 -> connected with XXX, channel 6
13:03:55.868 -> ip:192.168.178.4,mask:255.255.255.0,gw:192.168.178.1
13:03:55.915 -> ip:192.168.178.4,mask:255.255.255.0,gw:192.168.178.1
13:04:04.826 -> pm open,type:2 0
when I ping the IP-address I get:
Pinging 192.168.178.4 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.178.4:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
When I use the tool 'Wireless Network Watcher' I do see that a device is connected at 192.168.178.4 with the correct MAC address.
However, when I look at the management page of my FritzBox 7490 modem/router no device is mentioned at 192.168.178.4.
I remain at a loss here.
Hi all,
Should anyone face the same problem, I found the root cause: brownout threshold. I burned a new bootloader (Optiboot 8.0) without such trigger and the node has been working with used batteries (~2.7V) since May.
Hope this helps.
I see a lot of "!TSF" and "NACK" which seems to be radio communication problems.
That's MySensors related and can be related to many things, from soldering problem to power / capacitor issues.
In MY_DEBUG mode you should see your temp/hum printed on serial every ~15s so there is something wrong there, either wiring or a code issue.
Ty with the example included with the library "i2c_SI7021.h", without any MySensors related stuff, to see if your sensor is detected. You should see temp/hum on the serial.
