@jee67 Thank you. I installed MQTT successful. I am facing some errors about USB0 not connected so I need some time for troubleshooting. I will let you know if it’s working.
-
Announcement: ESPimaticRF coming soon
-
Well, everything seems to be working as far as it concern sending info from the homeduino to the nodes. In the pimatic log I can see messages being send over MQTT and in the arduino serial monitor I can see them arriving at the nodes. But still no switching devices on or off. I replaced my RF receivers and transmitters several times and checked all connections over and over, but I’m not able to discover what could be wrong. Is there any way to monitor whether the RF signals are succesfully broadcasted or not?
-
In addition: if I connect an ESP with sender and transmitter connected directly, I receive a timeout after trying to switch on/off a device.
-
@koffienl I checked my receiver and its working, but I still have not a working setup. So I started looking at the code and found this in ESPimaticRF_node.h:
// This will send the request to the server client.print(String("GET ") + url + " HTTP/1.1\r\n" + "Host: 192.168.2.118\r\n" + "Connection: close\r\n\r\n");
This looks like a hard code adress. Is this correct? My Pimatic has a different adress and of course the ESP homeduino too.
On this page: https://github.com/pimatic/homeduino-esp8266-node/blob/master/homeduino-esp8266-node.ino
I see a variable instead of a hardcoded adress -
Hmm that indeed looks like something that isn’t supposed to be there. Replace that line wit the one you found on the master.
Like my projects and help? Consider donating electroneum etnjwAKGPqF6omQWRmpp9u2BPyVDG9VuyRQjNJ1S8yfBdfR9qeUQ46kRy8KS2CNqbpNLRrsgmNW6F2TMzxmZgPrh6KctrkrYbm
-
I finally found time to try this out and first of all: excellent work, thank you!
Sometimes sending via the node fails. When it does, i get this in the log:
unknown message received: unknown message received: Soft WDT reset unknown message received: unknown message received: ctx: cont unknown message received: sp: 3fff1b50 end: 3fff1ec0 offset: 01b0 unknown message received: unknown message received: >>>stack>>> unknown message received: 3fff1d00: 00000019 00277775 00277775 4020deb1 unknown message received: 3fff1d10: 3ffef830 00000032 3fff1d80 3fff1d60 unknown message received: 3fff1d20: 3fff1f00 3ffef830 00000005 4020df64 unknown message received: 3fff1d30: 3fff1d60 00000014 3fff1d80 4010068c unknown message received: 3fff1d40: 3ffef830 3fff4838 3ffef830 3fff1d60 unknown message received: 3fff1d50: 3fff1f00 3fff4838 3ffef830 4020d225 unknown message received: 3fff1d60: 00000132 000003bd 00002650 00000000 unknown message received: 3fff1d70: 00000000 00000000 00000000 00000000 unknown message received: 3fff1d80: 00000000 00000000 00000000 00000009 unknown message received: 3fff1d90: 3ffe92a0 00ff0000 3fff4984 00000400 unknown message received: 3fff1da0: 00000000 00000000 00000000 00000001 unknown message received: 3fff1db0: 3ffef794 3fffdad0 3ffe8af0 00000030 unknown message received: 3fff1dc0: 3ffef794 3fffdad0 3ffe8af0 00000030 unknown message received: 3fff1dd0: 00000000 3fffdad0 3fff0e94 00000030 unknown message received: 3fff1de0: 00000000 3fffdad0 3fff4084 0000001f unknown message received: 3fff1df0: 00000016 3fffdad0 3fff0e94 00000030 unknown message received: 3fff1e00: 00000014 3fff4840 3fff1d60 00000030 unknown message received: 3fff1e10: 3ffe8ebd 00000007 3ffef92c 4020e89a unknown message received: 3fff1e20: 3ffef80b 000003ff 3fff1f00 3ffef90c unknown message received: 3fff1e30: 3ffef80b 00000005 3ffef80e 4020d703 unknown message received: 3fff1e40: 3fff1f00 00000000 3ffef7fc 4020d84c unknown message received: 3fff1e50: 00000008 3fff3044 000003e8 4020cd09 unknown message received: 3fff1e60: 00000000 00000000 00000000 3ffe8af0 unknown message received: 3fff1e70: 3fffdad0 3ffef794 3fff0e8c 4020cf1e unknown message received: 3fff1e80: 00000000 402073bc feefeffe feefeffe unknown message received: 3fff1e90: 00000000 00000000 00000001 3fff0e94 unknown message received: 3fff1ea0: 3fffdad0 00000000 3fff0e8c 40212d94 unknown message received: 3fff1eb0: feefeffe feefeffe 3fff0ea0 40100718 unknown message received: <<<stack<<< unknown message received: unknown message received: ets Jan 8 2013,rst cause:2, boot mode:(3,6) unknown message received: unknown message received: load 0x4010f000, len 1384, room 16 unknown message received: tail 8 unknown message received: chksum 0x2d unknown message received: csum 0x2d unknown message received: v09f0c112 unknown message received: ~ld
That doesn’t seem right?
Edit: This only seems to happen when i tell the ‘arduino one’ transmit action to ‘both’. When i set it to ‘transmit to all nodes’ it works fine.
-
@koffienl
Ok, I’ll try.One other thing, in ESPimaticRF_homeduino.h it looks like there’s a hardcode pinnumber at line 103:
//pinMode(pin, mode); pinMode(5, mode);
Is this correct?
-
Hi,
If I only want to receive rf signals do I then only need one (or more for example in each room) esp nodes? I don’t need a esp8266 connected to the Raspberry Pi?
And can this be combined with the homeduino transmitter/receiver connected by usb?Thanks in advance
-
you need a homeduino esp and a node esp
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
I finally got it working.
Somehow this did the trick: https://forum.pimatic.org/topic/42/tip-homeduino-usb -
Hi Koffie et al.,
I’m again trying to get ESPimaticRF on a NodeMCU. Yesterday, after some tweaking I managed to get ESPimatic working on an NodeMCU module. Today I’m trying to get ESPimaticRF on my NodeMCU. As, was the case last year, I keep running into compile errors where the Arduino 1.6.5 IDE says, ‘can not find SerialCommand.h’ or ‘can not find rfcontrol_command.h’ or the sorts. I am using Arduine 1.6.5 IDE with boardmanager 2.3.0 and with the correct board selected (all the same settings as which got my ESPimatic running). I’m really at a loss here. I can not see what I’m doing wrong.
I have set the sketchbook location to F:/ (to avoid windows issues with virtual paths and so on) and have tried with the files directly under this path (with arduino IDE saying the .ino file must be placed in a folder called ESPimaticRF) and with all files in a subfolder called ESPimaticRF.
The strange thing is it al worked fine with ESPimatic. But not with ESPimaticRF.
In your manual, you state; “Download all the files and place in correct folders”. Maybe this needs some more clarification for me…
I hope you can help me with this, as using your briljant software is something I have wanted to do for a very long time.
Regards,
Ruud
p.s. A respons in dutch works for me if that is easier for you.
-
@ruudvddries the error is there because the working directory (same dir where you open the .ino project) doesnt include the .h files. As @koffienl mentioned, extract it to a directory, open the .ino from there and in the top it should also load the correct .h files that the script refers to.
In this project,
#include "rfcontrol_command.h"
means that that file has to be in the same directory as the .ino project. Not in a subdirectory (if you extract, it is in the correct place)
For the other one’s:
#include <SerialCommand.h> #include <RFControl.h> #include <ESP8266WiFi.h> #include <WiFiClient.h> #include <ESP8266WebServer.h> #include <FS.h> #include <ArduinoJson.h> #include <WiFiUdp.h>
These should remain in the Libraries folder, however, i had an issue as my arduino did not load them from sketch so i ALSO placed them into “my documents/arduino/libraries”.
Maybe you could try that.
-
after some trial and error with what files should be placed where I have been able to upload the sketch to two NodeMCU’s.
Strange thing is that I extracted the zipped archive, downlaoded from Github straight into my Arduino Sketchfolder. Somehow this was not enough. But anyways, I got it working and now I will continue with the next staps. Thanks for your time and effort!
Best regards,
Ruud van den Dries
-
Hi guys, me again,
I have a working ESPimaticRF connected through USB to my Pi and use it as Master (both). It works for several minutes and than fails to send any RF-signals.
It is connected to /ttyUSB0/ and thus as such configured (default within homeduino plugin).What could I try to resolve this? I see no errors in the pimatic log for homeduino.
Regards,
Ruud
-
@ruudvddries both as master? One on usb is master, the rest should be slave’s (node’s).
Master sends to ALL nodes while master can also send (if enabled).
I did notice that sometimes it stops working, probably due to wifi dropping.
-
Well, currently I just have one Master ESPimaticRF node as replacement of my Arduino nano RF hardware which I used before with homeduino. I haven’t installed a slave node just yet.
Anyways, the odd thing is that my Google Home Mini aka Google assistant can switch my lights where at the same moment (well almost the some give or take a few seconds) I cannot via the GUI. It times out. After restarting pimatic it works again. I think that is strange (and thus not a WiFi dropping issue) but it could explain the ‘empty’ log.
So still open for ideas. Tomorrow I will install a esp slave node. Maybe that resolves the issue in some magical way.
Regards,
Ruud
-
@ruudvddries did you increase “UDP repeat”?
-
@Gleno0h Don’t think so. It’s set at 1.
-
@ruudvddries got almost the same issues here, this is what I’ve done so far:
Done the following to test and debug:
flashed v0.0.6 to both nodeMCU’s, connected the master to pimatic and set it in homeduino mode, connected to MQTT, both receiver and transmitter are connected and working. master receive action send to pimatic, master transmit action set to both.
The second nodeMCU is hanging somewhere else in the house, set as node, MQTT mode and also connected to both rx and tx hardware. on this one receive action is set to send to pimatic, transmit action set to send to local RF.
as a test I’ve disabled the master send and receive settings to see if data from and to the second nodeMCU is being sent and received. this succeeded so communication between the master, the node and pimatic (and the rx/tx modules) is working.
But still communication to pimatic crashes occasionally resulting in a time-out when trying to flip a switch. It looks like this is mostly happening when using a dimmer device (HomeduinoRF Dimmer 1). after one command is executed the second command almost always results in a time-out. only way to restore the connection is to reboot pimatic.
I’ve read somewhere this was due to UDP being kinda buggy but it also happens on MQTT.
Is this a software issue or is it just a limitation from the system/ESPimaticRF/Pimatic? -
@djmvt i am indeed getting the same. Didnt even notice it.
Could it be that when the device loses its wifi, it unmounts from the usb port? Could one of you check that the next time?