Adding JeeLink - stops Tx4 feeds

emonHub
1

I have a emon Tx4 v4 and emonbase 433MHz. I’ve added a JeeLink device with the recommended configuraton change to emonhub.conf suggested in the documentation: after the SPI entry and before the MQTT entry

[[jeelink]]
        Type = EmonHubOEMInterfacer
         [[[init_settings]]]
             com_port = /dev/ttyUSB0
             com_baud = 38400
         [[[runtimesettings]]]
             pubchannels = ToEmonCMS,
             subchannels = ToRFM12,
             nodename = RF

As soon as I restarted emonhub, Tx4 feeds which are configured for 5s, were updating intermittently - about every 10 minutes. When I powered up the JeeLink, the Tx4 feeds stopped completely. JeeLink worked beautifully. Commenting out the JeeLink block from emonhub.conf and restarting emonhub restored the Tx4 feeds to normal.

This must be an emonhub.conf formatting error - or perhaps just the location of the JeeLink entry in the file. I may well be overlooking something very obvious.

2

Hi @rkstobart - you can’t interleave a JeeLib device with an LPL device through the same receiver. The packet format is different and it will discard the “other” one. What device do you have with the old JeeLib? If it’s an OEM product, there’s likely to be an updated version of the firmware using LPL.

1 Like
3

Hi Angus

Many thanks for your reply which forced me to go back and review the supporting documents for range extension. I apologise. I misread the documentation for the range extender - and there is no need for the emonhub configuration change. All is well with distant temperatures being read according to schedule.

1 Like
4

No problem Richard, glad you’re running again :slight_smile:

5

What documentation I can find is extremely thin on the ground. Looking at the Shop page and the Github code, the comment on the Shop page “The JeeLink is a fully assembled and ready-to-use USB-type “stick” which plugs directly into a PC, Mac or USB hub.” seems to imply it’s got two distinct uses:

As a receiver.
It can be plugged into a serial USB port of a PC or RPi and used instead of an RFM69Pi or RFM69SPI. Then you need that entry in emonhub.conf.

As a repeater.
When you’re using it to relay the radio packet, it pretends to be a Base node (ID=5) when receiving but transmits taking on the identity of the original node (no real surprise there).
If you’re only using the USB port to power it, you’re not interested in the data coming out of that serial port, so you should not make the entry in emonhub.conf.

I can’t blame you for that - it appears to rely on you knowing all about it in the first place. I’ve added this for future readers.

1 Like