Hi,
I have my Serial Gateway on a RasPi with Pimatic operational for >2 years now.
Since a few days I notice all drie leds (rx, tx, error) are flashing simultaneously every second.
I can recall it didn't behave like that when I setup the system.
All is working correct, I see all sensors sending/receiving data in a correct way.
What can be wrong here?
I think it is logical to have sensors try indefinitely since this is the concept of sensors in a network.
Otherwise you would not know (when not debugging) all is ok in your network.
A network sensor not being one in an usual way, just for convenience (like my BBQ-temp sensor), has to be defined otherwise.
@GertSanders The define was sufficient in my case:
#define MY_TRANSPORT_WAIT_READY_MS 2000
The sketch continues on startup when not able to connect (my BBQ-temp node is working stand alone) but will keep on trying to connect. When the gateway is found it will connect and the data is available on iPhone.
Thanks!
@gertsanders Can you show your script on this with the define MY_TRANSPORT_WAIT_READY_MS to get a "timeout" and using the TransportReady() ?
I would like to do the same with my BBQ-temp node since it has it's own display (node is for convenience to check temps on iPhone but not always needed).
@gohan A capacitor is used in al my sensors, I did not shield it. Also my gateway has no shielding and is working fine.
Wat should ne shielded? All the electronics of the radio, so everything except the antenna?
@etxmsol I think you might be right about to strong signal.
I just tried changing the MY_RF24_PA_LEVEL from RF24_PA_MAX down to RF24_PA_LOW and RF24_PA_MIN. With RF24_PA_MIN it worked. 
I will try again with increasing distance and increasing the level when needed for my purpose.
@gohan That's what I did as mentioned in my post (radio power module) using a separate 5V power supply as well.
@sundberg84 I powered it directly from the Arduino Nano, also tried with separate power supply. No change, same results.
My gateway works fine with the same type of radio directly from the Nano.
What else to consider.
Hi,
I'm trying to replace a NRF24L01+ radio with a NRF24L01 + PA + LNA radio (with the antenna) to achieve a better range.
The node is working with the NRF24L01+ without any problem.
I now have tried 3 different NRF24L01+ PA +LNA and still end up with the same issue:
0 MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.1.1
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSF:SID:OK,ID=10
14 TSM:FPAR
51 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2058 !TSM:FPAR:NO REPLY
2060 TSM:FPAR
2096 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4104 !TSM:FPAR:NO REPLY
4106 TSM:FPAR
4142 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6150 !TSM:FPAR:NO REPLY
6152 TSM:FPAR
6188 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8196 !TSM:FPAR:FAIL
8197 TSM:FAIL:CNT=1
8199 TSM:FAIL:PDT
18202 TSM:FAIL:RE-INIT
18204 TSM:INIT
18211 TSM:INIT:TSP OK
18213 TSF:SID:OK,ID=10
18215 TSM:FPAR
18252 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20259 !TSM:FPAR:NO REPLY
20261 TSM:FPAR
20298 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22305 !TSM:FPAR:NO REPLY
22307 TSM:FPAR
22344 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24351 !TSM:FPAR:NO REPLY
24353 TSM:FPAR
24390 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
26397 !TSM:FPAR:FAIL
26398 TSM:FAIL:CNT=2
26400 TSM:FAIL:PDT
It doesn't want to connect.
I also tried to use the radio power module but with no luck.
My serial gateway is also using the same NRF24L01+ PA +LNA and works for over a year ok.
What can I do to get it working?
@gohan I know it is suggested only when experiencing bad reception issues:
Connecting a Decoupling-Capacitor
If you experience bad reception or if transmitted data never reaches destination, try adding a decoupling capacitor of 4.7µ - >47µF (the exact size usually doesn't matter) across the radio's 3.3V and GND.
But I didn't have issues, only when using the Arduino IDE Serial Monitor and only with this specific node.
Until now I only had one in the Gateway radio. All other nodes work without except for the Weather Station node because this is running on a solar cel with rechargeable battery on a larger distance. In this one I also extended the NRF24L01 radio antenna.
Problem seems solved. Thanks for helping out.
@gohan I understand. But when running ok it is also connected to the PC (using power of the same USB port but not running IDE Serial Monitor) so I guess the PC itself is not the issue.
Since it seems a communication issue I just added a decoupling capacitor of 4.7µF on the radio power supply.
Now the node connected after 5 attempts.
I guess using the serial monitor generates some noise on the USB influencing the 3.3V output of the Nano making the radio instable.
@gohan said in Node not connecting in IDE Serial Monitor but does stand alone:
ok, but don't you have another computer to try?
No.
What makes you think it is computer related?
@gohan No I didn't want to downgrade my EDI ending up in having library issues.
@FotoFieber I have the node attached via USB to my PC. All works fine.
I open the Arduino IDE having the sketch, as already running on the node, open to edit. All works fine.
I now start the Serial Monitor. The node restarts and I see this:
0 MCO:BGN:INIT REPEATER,CP=RNNRA--,VER=2.1.1
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSM:INIT:STATID=100
15 TSF:SID:OK,ID=100
17 TSM:FPAR
53 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2061 !TSM:FPAR:NO REPLY
2063 TSM:FPAR
2099 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4107 !TSM:FPAR:NO REPLY
4109 TSM:FPAR
4145 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6153 !TSM:FPAR:NO REPLY
6155 TSM:FPAR
6191 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8199 !TSM:FPAR:FAIL
8200 TSM:FAIL:CNT=1
8202 TSM:FAIL:PDT
18205 TSM:FAIL:RE-INIT
18207 TSM:INIT
18214 TSM:INIT:TSP OK
18216 TSM:INIT:STATID=100
18219 TSF:SID:OK,ID=100
18221 TSM:FPAR
18257 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20267 !TSM:FPAR:NO REPLY
20269 TSM:FPAR
20305 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22313 !TSM:FPAR:NO REPLY
22316 TSM:FPAR
22352 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24360 !TSM:FPAR:NO REPLY
24363 TSM:FPAR
24399 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
26407 !TSM:FPAR:FAIL
26408 TSM:FAIL:CNT=2
26411 TSM:FAIL:PDT
Continuing to RE-INIT.
Closing the IDE does not solve anything. I first need to unplug the USB and plug it in again and the node is working again.
No suggestions?
In addition: in both situations the node (Nano) is powered by the PC (usb). The node is connecting to the gateway but as soon Arduino IDE Serial Monitor is started (node restarts) the node won't connect to the gateway anymore responding with FAIL (keeping trying).
Debugging is an issue now.
Since the latest Arduino IDE update I did last week I notice my Display Node project can't be monitored by the IDE Serial Monitor. The node fails to connect to the Gateway.
However when the node is powered without using the IDE Serial Monitor it is working properly.
What can be the reason for this?
@gohan thanks for the info.
I'll look into it and see if the transition is worth while.
@gohan Sorry I didn't answer that this weekend.
I tried many times before to build a ESP8266 Gateway and ended up in frustrating continuous reboot issues.
So I gave up on that.
I have now a Serial Gateway working fine.
How would a MQTT gateway benefit more in the issue I have not being able to directly retrieve data from the controller?
@Boots33 That's how I plan to do it now. But for every new sensor value to get to the Display node (or when building a new Display node) I also have to update someting in Pimatic. That's what I would like to get rid off.
@Boots33 Display nodes are convenient in monitoring status of other nodes. I would like to have a Display node in the lead for this (on request).
In this way new Display nodes can be set up more easily without having to update the controller for each change on Display nodes.
If Pimatic would be able to handle the 'request()' for the node doing the request it would be great I think (like your solution).
@AWI said
- Let the display node request()/"pull" the value from the controller.
This is where Pimatic fails. I can't request info of any node from the controller even not from the node itself.
@Boots33 Thanks for the explanation!
However, as mentioned in an earlier post, I can't directly request data from the weather station node since it is battery operated and uses a sleep to save power. In this case the node will not react to a request.
I'm now using the receive command exactly in the way you mentioned by determining the sensor in the message to get the correct data for the right value to display in my Display node.
In Pimatic I set up a rule to send the data of the latest received value of the weatherstation node, triggered by a change of that value (when weather station node is sending a new value). The point is now that this is a push functionality by Pimatic where I'm looking for a pull mechanisme to be done by the Display node to Pimatic.
@gohan I would like to leave the weather station reprogramming as the last option since it was built in the v1.5 period and calibrated. Never try to repair a working device
In general I would like to develop a solution where display nodes can be added to the network not having to change other nodes for that. The independency of using display nodes without having to change sensor nodes would be great to achieve.
@mfalkvidd I'll try to find out how to request data from the gateway/controller of a specific node. As long as the Pimatic controller is showing the data there must be a way to get it from there. Search the Pimatic forum for now.
@mfalkvidd I'm getting there in time
Thanks for all the patience you have in explaining.
Using the message.setDestination() function would then be an option to implement/add in the weather station node for each of the 5 sensors?
The drawback would be to reprogram the weatherstation which is fully operational now.
Using the resquest function in the display node would want to activate the weather station (being a battery node in my garden) which uses the sleep mode and that would not work as documented.
As said before I would also want to use the display node as a repeater.
This would make it a kind of gateway in passing through data.
Is there a possibility there to evaluate the weather station node data?
You also mentioned a way to get the data from the controller (Pimatic in my case).
How can I request data from the controller/gateway?
Or is there a way to let the controller/gateway send the data to the display node?
Maybe I'm looking at this issue in the wrong way.
All I would like to do is display data from a battery operated sensor node on another node.
@mfalkvidd actually it is one node having 5 sensors.
My setup is one gateway with multiple nodes (4 PIRs, 1 Temperature, 1 Humidity and the weather station with 5 sensors).
These nodes just use the standard 'send' function. This is a broadcast, isn't it, since no destination node is provided in this function?
The gateway picks up these messages of the nodes (as I can see them in my controller Pimatic) and I hope the display node will pick the message up as well.
Or does the receive function only pick up dedicated sent messages from other nodes?
If this is the case I will have the display node to query the controller. No clue how to do that.
I'll build the display node tomorrow to test the sketch I have now and see if it receives the data of node 38 (weather station and its 5 sensors).
@mfalkvidd thanks for the info.
I came up with this and verification of the sketch is ok in Arduino IDE:
void receive(const MyMessage &message)
{
// Explore message
if (message.sender == 38) // weatherstation node
{
switch (message.sensor)
{
case 0: // Humidity sensor
{
lcd.setCursor ( 0, 1 );
lcd.print("Hum: ");
lcd.print(message.getFloat());
lcd.print("%");
}
case 1: // Temperature sensor
{
lcd.setCursor ( 0, 0 );
lcd.print("Temp: ");
lcd.print(message.getFloat());
lcd.write(223); // Degree-sign
lcd.print("C");
}
case 2: // Light sensor
{
lcd.setCursor ( 8, 1 );
lcd.print("L: ");
lcd.print(message.getUInt());
lcd.print("Lux");
}
case 3: // Barometer sensor
{
lcd.setCursor ( 8, 0 );
lcd.print("P: ");
lcd.print(message.getFloat());
lcd.print("mBar");
}
case 4: // Barometer Temperature sensor
{
}
case 5: // Rain sensor
{
}
}
}
}
Is this the way to approach ?
I still have some questions about the concept:
When I use the 'receive' function in this display node, will the message still be received by the gateway?
In general: can messages sent by one node be receive and evaluated by multiple other nodes in parallel?
@mfalkvidd to start right:
The function 'void receive(const MyMessage &message)'
This will catch all data being send from nodes?
I will have to identify what type the data is and from which node and sensor the data came and if the node is correct use that data to update the display with?
The function 'void request(uint8_t childSensorId, uint8_t variableType, uint8_t destination);'
This function will request directly data from a particular node and sensor.
Probably not the way to go when the sensors are battery nodes since this function will activate the battery nodes often.
The receive function would fit better but I have to investigate how to determine the node and sensor the data received is coming from. Is there an example for this?
@mfalkvidd yes I did and believe it is showing the RTC data of that same node. It gets the time initially from the controller by a specific for the system time available function 'requestTime()'.
How would I for example get the temperature from a particular node in this display node?
So how to refer to that particular node and the temperature attribute in the sketch of the display node?
Is there a kind of function 'requestValue(NodeId, SensorId)'?
Hello,
I would like to create a display node (1602 or 2004) with the possibility to show measurements of other node(s).
How do I approach on this? What is the way to work with MySensors.
I would like the display node to be available in the living room with the ability to show for example the data from my weather station (multi sensor node). On top af that this display node can act as repeater node.
Will in such case this node receive data directly from the weather station node or do I have to retrieve the data for this node from the pimatic database?
How do I implement this?
Thanks for any suggestions :simple_smile:
I gave it a try again by using some suggestions on the net like changing the radio CS connection from GPIO15 to GPIO5.
No effect.
In the comments of the sketch I read:
* Not all ESP8266 modules have all pins available on their external interface.
* This code has been tested on an ESP-12 module.
* The ESP8266 requires a certain pin configuration to download code, and another one to run code:
* - Connect REST (reset) via 10K pullup resistor to VCC, and via switch to GND ('reset switch')
* - Connect GPIO15 via 10K pulldown resistor to GND
* - Connect CH_PD via 10K resistor to VCC
* - Connect GPIO2 via 10K resistor to VCC
* - Connect GPIO0 via 10K resistor to VCC, and via switch to GND ('bootload switch')
I guess these are not needed when using the NodeMCU as presented in the MySensors store?
Today arrived the new MCU (as presented in the shop) and I uploaded the sketch.
Still no success, but with again a new error code:
ets Jan 8 2013,rst cause:4, boot mode:(3,7)
wdt reset
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3de0c112
~ld
mode:(3,6) changed to mode:(3,7)
I powered by USB on PC (for serial Monitor), USB on 2.0A output and seperate 5V directly to pin on MCU (how to monitor when not using USB on MCU?).
It won't work. I think the concept is not stable enough (resets are common issues I see on the net).
I'll have to give up on this I guess.
@Harry-van-der-Wolf thank you for this interesting link.
When using a more stable (other than PC-usb, iPad charger, decicated USB 2A power outlet??) other then USB, how would I be able to feed the module and also Monitor its behaviour with the Arduino IDE?
@Harry-van-der-Wolf I tried your suggestion without luck.
I'll wait for my other MCU to arrive and try again.
@Harry-van-der-Wolf thank you for the info!
I'm not so familiar with these hardware items: what is the 'spiffs-flash-size' and how to adjust it?
When using MySensors 1.5, I had this output in the Serial Monitor:
ESP8266 MySensors Gateway
Connecting to Vierkenshof_G
..Connected!
IP: 192.168.1.76
ets Jan 8 2013,rst cause:4, boot mode:(3,4)
wdt reset
load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
~ld
Where now using MySensors 2.0, I end up with:
ets Jan 8 2013,rst cause:4, boot mode:(3,6)
wdt reset
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3de0c112
~ld
So I don't see the connect to my network anymore (?) and having different boot mode for the reset cause.
Tried a different radio, no change.
Powered with my iPhone power plug I also do not see the MCU connect to my router.
I guess my Amica NodeMCU isn't compatible/has hardware failure.
I now ordered the one as presented in the shop.
See if that will work.
@sundberg84 I powered my NodeMCU 1.0 (ESP-12E Module) via USB from my PC. That should not give a powerissue.
How does your linked sketch work: load it to the NodeMCU and then check the Serial Monitor?
@Harry-van-der-Wolf and @mfalkvidd . I'm now on Mysensors 2 trying to get my WFI Gateway to run.
Used new sketch (tried both 0.9 and 1.0 board setting but no luck.
Serial Monitor now:
ets Jan 8 2013,rst cause:4, boot mode:(3,6)
wdt reset
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3de0c112
~ld
repeating
@bisschopsr That must be the same one I use for the gateway with the external antenna.
I also saw once a wire connected to the standard radio but can't recall where I saw that.
@Salmoides I built this weather station (exactly as decribed above in the initial message) and have some problems with the radio when going about 15 meters from the gateway.
I have several other nodes on similar distance working just fine.
I guess the metal top of the case (where the solar panel is in) is causing the issue. Is there a way to change that? Maybe an additional antenna wire (how)?
@mfalkvidd I use Pimatic to control all. I'm not aware of having set an offset in there to start at node 33.
Can you explain how this mechanisme works?
I use the Arduino IDE Serial Monitor to scan the communication of a new node and determine the node ID it has. After that I use this node ID to configure the node in the Pimatic settings and definitions.
Hello,
I built a serial gateway (auto node), a few PIR-nodes, temperature node and a solar weather station node.
What I don't really understand is the automatic node management of the gateway.
First of all the first node I activated got ID 33 and sequential new nodes got node IDs by increment from 32.
Why didn't it start with node ID 1?
Is there a way to 'release' node IDs in the gateway that aren't used anymore?
When experimenting with nodes every time a new node is introduced a new node ID is created.
I guess the gateway is managing the IDs and there might come a point where node ID 254 is reached and no IDs are available anymore.
How do you deal with that?
@Yveaux thanks for your reply.
I will update MySensors to v2.0.0 when I believe my Control software Pimatic can handle all (there are some issues with sensors I have built with v2.0.0 and are running well on v1.5.4).
So I will give it some time to evolve for now.
@Nca78 I did not find a solution in taht thread.
Maybe it is just hardware failing: the MCU itself.
@Harry-van-der-Wolf I tried but I'm still getting the same reset message: Cause:4, boot mode:(3,4).
I'm stuck here. I also tried another NRF with the same result.
@Harry-van-der-Wolf thank you for this suggestion.
I will try that one.
It is only selecting the board 'NodeMCU 0.9 (ESP-12 Module)' instead of 'NodeMCU 1.0 (ESP-12E Module)' as board to upload to, isn't it?
@bigjimjeedom did you already solve the issue?
I'm running into the same now.
Gateway ESP8266 Wifi resets after connecting to router
Can you please respond in the thread mentioned?
@mfalkvidd I have found someone with the same issue, using a different board version 0.9 vs 1.0.
WIFI Gateway NodeMCU 0.9 always reset
@bigjimjeedom was using firmware 2.0.0 ending up with the same error. Not solved in this thread.
@mfalkvidd Thanks.
I now loaded a sketch using a different frequency and a simple Dallas Temperature node.
The gateway powered by a direct USB power source (to avoid the power issue). The node is trying to find the parent and gets stuck there.
The gateway is not available and I guess rebooting (blue leds lights up in I assume reboot sequence).
So the watchdog timer issue to investigate.
Maybe try to get firmware v2.0 for the ESP.
@mfalkvidd said:
the watchdog timer kicks in if your code is busy for too long. If you have any delaysor long-running loops, remove them and see if it helps.
I have the basic sketch for the gateway from MySensors so I think there are no delay nor long-running loops in there.
Another question: can I run two gateways (the wifi one I'm only testing while my serial one is operational) when nodes are already operational? Will they not get confused about what gateway to work with?
Change the nrf radio channel in MyConfig.h when uploading the sketches for your new network. Wih different channels the two networks will not interfere with eachother.
Ok. Good suggestion. In that case I need to build a standard node on that channel as well.
What happens when running on the same channel. Will existing nodes at all communicate with the new gateway when also the serial gateway is operational?
@mfalkvidd Thanks for all the info.
I followed the link you sent and the 'cause:4' indicates watchdog timer related. How to get by that one :).
You power suggestions I will have a look at. I don't think I have a powered USB hub.
I guess I will need to have Controller software and a new node to test this (current nodes are operational with a MySensors serial gateway with Pimatic). Another question: can I run two gateways (the wifi one I'm only testing while my serial one is operational) when nodes are already operational? Will they not get confused about what gateway to work with?
@mfalkvidd I would like to try with eliminating the possible power supply issue. In case this is the issue the firmware downgrade will also not work I guess.
When not connected to the computer, how can I monitor if it's working? I can't use the Serial Monitor in that case, can I.
@mfalkvidd I saw those threads earlier today but judged them as other errors: the first has 'cause:4, boot mode:(3,6), second had already a node connected where after a while resets began.
Did the Wifi Gateway not work on the MySensors versions before V2.0.0?
I thought the basic version as explained on the MySensors website with v1.5.4 was a working one.
Since I'm using Pimatic with the serial gateway on v1.5.4 and read some issues on using MySensors V2.0.0 I do not want to upgrade at the moment. As I read, I then need to upgrade my serial gateway and operational nodes as well to retain compatibility. This would be to risky now since I do not want to end up having nothing working at all.
I guess I have to wait until v2.0.0 is more common and adopted by the community to switch.
Hello,
I just build my ESP8266 Wifi gateway with a NodeMCU Lua board and an NRF24L01+ and loaded the standard sketch as distributed in MySensors 1.5.4 library with ESP8266 v2.1.0 according to the board manager in Arduino 1.6.8, using board 'NodeMCU 1.0 (ESP-12E Module)'.
The same MySensors library I used to build a Serial Gateway and a few nodes with success.
However when uploading the sketch to the NodeMCU and starting the Serial Monitor I see rebooting after successful wifi connection:
ESP8266 MySensors Gateway
Connecting to Vierkenshof_G
..Connected!
IP: 192.168.1.76
ets Jan 8 2013,rst cause:4, boot mode:(3,4)
wdt reset
load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
~ld
ESP8266 MySensors Gateway
Connecting to Vierkenshof_G
..Connected!
IP: 192.168.1.76
I do not understand the 'cause: 4, boot mode:(3,4)'.
What could be wrong?
@gigi I know but in your breadboard picture the now mentioned V output is connected directly to ground. 
@gigi said:
New fritzing
I have two questions?
- voltage divider for more 5 v (battery voltage 12-13 volts)
- I use a auto phone charger for step down (12v --> 5 V) - warmers if I close in a box?
Thank
Is your fritzing correct?
On the green wire (light sensor?) you measure on ground where I guess you should measure between the resistor and the sensor.
I agree.
It is very hard/difficult to keep a consistent set of libraries operational in a broader scope of elements to be managed.
Got it working now 
I installed Arduino software and mysensors api again.
Reloaded my gateway from this install.
On the node ran the EEPROM sketch from mysensors library and reloaded the DST sketch from also the mysensors library.
I think something went wrong in library updated Arduino suggested.
@hek Is it essential to work from the mysensors library (as distributed in the api) and keep that as a stable set and ignoring library updated suggested by the Arduino software?
And when updating libraries they will updated in a My Documents folder causing Arduino software to generate issues on compiling of having libraries twice. What is the way to work on this?
@hek said:
You should have a look in the gateway log.
Is this the gateway log?
debug [pimatic-mysensors]: <- MySensorDST { sender: 0, sensor: 0, type: 0, value: '72.2' }
15:47:17
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0:72.2
15:45:02
debug [pimatic-mysensors]: <- MySensorDST { sender: 0, sensor: 0, type: 0, value: '72.1' }
15:45:02
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0:72.1
15:45:01
debug [pimatic-mysensors]: <- Presented Node [ '0', '0', '0', '0', '6', '' ]
15:45:01
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0:
15:45:01
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0:1.1
15:45:01
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0:Temperature Senso
15:44:59
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0:0
15:44:59
debug [pimatic-mysensors]: <- Presented Node [ '0', '255', '0', '0', '17', '1.5.3' ]
15:44:59
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0:1.5.3
15:44:59
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=255,c=3,t=15,pt=2,l=2,sg=0:0
15:44:53
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0:0
15:44:53
debug [pimatic-mysensors]: <- Presented Node [ '0', '255', '0', '0', '17', '1.5.3' ]
15:44:53
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0:1.5.3
15:44:53
debug [pimatic-mysensors]: <- I_LOG_MESSAGE 0;0;3;0;9;read: 0-0-0 s=255,c=3,t=15,pt=2,l=2,sg=0:0'
I do not see a INTERNAL/I_CONFIG message.
Line 8 is giving the temperature and will keep doing this.
It is also accepted by my controller (Pimatic on a RasPi) and therefore I did not think of a communication problem.
Where can I find this gateway log?
I'm pretty new to this so still learning
I tried again to get it to work with the original sketch.
1. send: 0-0-0-0 s=255,c=3,t=15,pt=2,l=2,sg=0,st=ok:0
2. send: 0-0-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,st=ok:1.5.3
3. send: 0-0-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
4. sensor started, id=0, parent=0, distance=0
5. send: 0-0-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0,st=ok:Temperature Sensor
6. send: 0-0-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:1.1
7. send: 0-0-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0,st=ok:
8. send: 0-0-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=ok:66.6
Should the M appear in line 7?
What is deciding in going for Imperial or Metric?
Can anyone help me out?
Strange. I can not see what goes wrong.
I updated the sketch to just use Celsius.
Replace this (for the Temperature sketch) from:
float temperature = static_cast<float(static_cast<int((gw.getConfig().isMetric?sensors.getTempCByIndex(i):sensors.getTempFByIndex(i)) * 10.)) / 10.;
With this
float temperature = static_cast<float>(static_cast<int>((sensors.getTempCByIndex(i)) * 10.)) / 10.;
Related to this topic and the fact I used CodeBender I guess somewhere there is the problem.
The IsMetric function doesn't seem to work.
Hi,
I'm a bit confused on the temperatures my DST is sending.
send: 0-0-0-0 s=255,c=3,t=15,pt=2,l=2,sg=0,st=ok:0
send: 0-0-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,st=ok:1.5.3
send: 0-0-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
sensor started, id=0, parent=0, distance=0
send: 0-0-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0,st=ok:Temperature Sensor
send: 0-0-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:1.1
send: 0-0-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0,st=ok:
send: 0-0-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=ok:75.8
send: 0-0-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=ok:73.7
send: 0-0-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=ok:72.8
send: 0-0-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=ok:72.1
send: 0-0-0-0 s=0,c=1,t=0,pt=7,l=5,sg=0,st=ok:71.7
I used the standard sketch where I see this 'boolean metric' setting (I guess for arranging this):
float lastTemperature[MAX_ATTACHED_DS18B20];
int numSensors=0;
boolean receivedConfig = false;
boolean metric = true;
// Initialize temperature message
MyMessage msg(0,V_TEMP);
My Pimatic shows the temp as 70 C.
I think it is a Fahrenheit vs Celsius mix-up since 70 F is about 21 C which would be correct.
Thank!
I'll give it a try.
I'm new in the Arduino world and hoping to learn from more experienced users.
For my garagedoor I would like to build a relay actuator with a slightly different functionality.
My Hörmann garagedoor motor works with pulse contact to activate up or down.
Two relays are needed, one for up and one for down.
When making a short contact (say using relay 1) the door starts to go up. Again making a short contact would stop the door (for intervention). When making contact again it will continue to go up, as a cycle until the door is completely open or the second contact is activated to close it. The second contact is used to close the door having the same procedure.
So the relay should make contact for 1-2 seconds and then release again.
How can I arrange this?
Hi All,
I'm new to mysensors and picked it up to use it with Pimatic on a RasPi.
I've built a serial gateway and loaded the default sketch.
Now I would like to check if the gateway is ok (I do not have sensors yet).
Is there a simple way to check the gateway without sensors?
I looked at the Arduino serial monitor and see this:
0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;14;Gateway startup complete.
Gateway seems to start alright.