Search found 10 matches
- 10 Aug 2017, 23:18
- Forum: RFlink: General Discussions
- Topic: Openhab and RFlink
- Replies: 1
- Views: 4827
Re: Openhab and RFlink
You can use the serial binding as I described here.
- 06 Mar 2017, 20:11
- Forum: ESP Easy: General Discussion
- Topic: Feature Request collection/list
- Replies: 197
- Views: 194791
Re: Feature Request collection/list
Hope this is the right place to ask.
Will be great to have version number available via MQTT, the same way as RSSI and Uptime.
Many thanks to psy0rz for v2!
Will be great to have version number available via MQTT, the same way as RSSI and Uptime.
Many thanks to psy0rz for v2!
- 04 Feb 2017, 10:50
- Forum: ESP Easy: General Discussion
- Topic: extra slash at the end
- Replies: 2
- Views: 2707
Re: extra slash at the end
Thanks, already fixed - I misunderstood some configuration fields meaning.
- 17 Jan 2017, 16:40
- Forum: RFlink: General Discussions
- Topic: nothing in the debug log
- Replies: 10
- Views: 9703
Re: nothing in the debug log
Changed receiver to RXB6 and everything works as it should.
In order to get real temperature I probably need to convert hex to decimal then divide by 10 - right?
0e (hex) == 14 (dec), La Crosse display shows 1.4 outside.
Thanks!!
Code: Select all
20;24;LaCrosse;ID=0400;TEMP=000e;
0e (hex) == 14 (dec), La Crosse display shows 1.4 outside.
Thanks!!
- 17 Jan 2017, 11:05
- Forum: ESP Easy: General Discussion
- Topic: extra slash at the end
- Replies: 2
- Views: 2707
extra slash at the end
Hello
I'm running Build: 147. This is my configuration:
This is what I'm getting from MQTT broker (using mosquitto_sub):
Why the slash is added at the end?
"rssi" seems to be a %valname%, but what is the %tskname% ?
I'm running Build: 147. This is my configuration:
Code: Select all
Publish Template: %sysname%/%tskname%/%valname%
Code: Select all
esp1/rssi/ -69
"rssi" seems to be a %valname%, but what is the %tskname% ?
- 05 Jan 2017, 12:11
- Forum: RFlink: General Discussions
- Topic: nothing in the debug log
- Replies: 10
- Views: 9703
Re: nothing in the debug log
Sounds logical, but situation is still weird because TX6U Monitor keeps providing some sustaining output: Message recognized from LaCrosse TX6U device! ID: 32 Temperature: 6.91 °C Message recognized from LaCrosse TX6U device! ID: 32 Temperature: 6.58 °C Message recognized from LaCrosse TX6U device...
- 05 Jan 2017, 10:50
- Forum: RFlink: General Discussions
- Topic: nothing in the debug log
- Replies: 10
- Views: 9703
Re: nothing in the debug log
It is 433MHz.
It has 4+2 pins, CE pin has no external connection, but on PCB it is connected to Vcc over 10k resistor.
Thank you for looking into my issue.
It has 4+2 pins, CE pin has no external connection, but on PCB it is connected to Vcc over 10k resistor.
Thank you for looking into my issue.
- 04 Jan 2017, 12:31
- Forum: RFlink: General Discussions
- Topic: nothing in the debug log
- Replies: 10
- Views: 9703
Re: nothing in the debug log
This is the sketch I used for testing: https://github.com/andreacioni/TX6U-Monitor I've tested both pins here - 2,0 (default) and 19,4 (to be in sync with RFLink): TX6U t(2,0); //Arduino UNO pin 2 -> interrupt 0 I'm using Mega 2560, receiver data pin connected to pin 19, all according to the instruc...
- 04 Jan 2017, 09:58
- Forum: RFlink: General Discussions
- Topic: nothing in the debug log
- Replies: 10
- Views: 9703
Re: nothing in the debug log
taking power from 5V pin does not help
- 03 Jan 2017, 22:17
- Forum: RFlink: General Discussions
- Topic: nothing in the debug log
- Replies: 10
- Views: 9703
nothing in the debug log
Hello everyone My plan was to catch weather information from my old outdoor La Crosse TX-2U sensor, but for some reasons I see nothing in the debug log. I expected to see either something decoded or at least some raw debug data, but I see nothing [from the sensor]. 20;00;Nodo RadioFrequencyLink - RF...