Yes! Well Maybe NO is the correct answer
One sensor can be paired to several devices so that friends or family can enjoy sensor data within the Bluetooth range. is the Q&A answer.
My Ruvvi Pro does NOT maintain a connection to 2 Victron Vrm Instances or
2 Systems Are UNABLE to maintain a connection with the device at the same time.
Is there a way to fix this ??
Hi @wolfbarn , thanks for your message. RuuviTag Victron integration is created and supported by Victron. Unfortunately we cannot help with their app specific questions.
I would suggest to have a look at their support pages for more information.
I went with the Ruuvi sensor specifically because it worked with the Victron system. Are you guys backing away from your support with the Victron system? If that’s the case then I’ll stop recommending your sensors on the DIYSolarForum.com site.
I will say that I’ve had a lot more issues with the Mopeka sensors than the Ruuvi sensors when it comes to working with Victron.
From my DIY perspective, when there are issues, I don’t know who to work with. Seeing a vendor jump in to help when it isn’t clear who is responsible would go a long way towards ensuring a good reputation.
Devices that support the Bluetooth Multipoint feature can do this. I don’t know if the Ruuvi has this feature. However, it doesn’t seem to have a problem communicating with my Victron Cerbo GX while I’m also using the app on my phone to look at the RuuviTag numbers.
Sorry to advise that it is Seen in Both Systems Its just can NOT maintain the Updates or connection
ITS NOT a VICTRON ISSUE as I see it
Once Sold to you They dont want to Know You & many ruuvi sensors I have are Extremely Heavy on Batteries & their advice is to reduce the reporting interval
No Mine either to ONE system
I can see there is RuuviTag related information in GlobalLink manual on Victron website, but it doesn’t mention specifics about limitations related to connections to VRM instances, unfortunately. Maybe @henri can provide some clues about VRM. Reading their forum I don’t immediately see mentions about any limitations connecting to multiple instances.
Ruuvi sensors actively broadcast Bluetooth advertisements to their surroundings and doesn’t require creating a paired connection to the device.
Information on our website relates only to Ruuvi software and not to Victron systems. The RuuviTag integration to Victron systems is built and supported by Victron, we have unfortunately no good insight into their software as there is no direct relationship between the two companies. Our support is therefore always limited to best effort and the best possible support for Victron software is available through Victron.
For battery related comment, when used with the included CR2477 battery, the sensors can run typically between 12-24 months under standard use and operating conditions. Temperature and humidity can affect the battery life a lot and also if the internal memory is being read frequently. If your battery is drained much faster than this, then I would suggest to check if there is a possibility that condensation would have been able to enter inside the RuuviTag case. We can help you check this also, just send us message to support@ruuvi.com with closeup photo of your sensor circuit board.
I hope this is helpful to you and sorry for not being able to give a better conclusive answer for this topic at this point.
RuuviTags are never paired, and there’s no limitation how many devices can receive broadcasts from the Ruuvi sensors. This is also the case with Victron products as RuuviTag sensors are only broadcasting the data, and there’s no any pairing with the sensors.
So, as a summary from a RuuviTag point of view, sensor doesn’t know if the data is received by 1 or 100 receivers.
Could you tell a bit more what kind of VRM systems you are using? Are you receiving data with RaspberryPi or some other devices? How you are viewing the data?
Info received on VICTRON VRM or 2 Cerbo Gx Systems via connected GX Displays or on VRM via iPhone
2 systems Both Display the ruuvi tag & temps humidity etc But as I go from system to system on the VRM the ruuvi Bluetooth connection is lost on1 System
reloading the Vrm Regardless of device returns the Bluetooth connection to active
These systems are Both within 5 meters of the sensor.
No Raspberry Pi Involved
Hi,
As the sensor is not connected or paired to Victron (it’s one way broadcasting mode connection), RuuviTag sensor doesn’t know if there are 1 or 100 Cerbo GX systems receiving the data. As the data goes to Victron own app / cloud, for me it sounds that I cannot handle data from a two different installation for the same ID sensor. That would be my initial guess what could be causing this kind of issue.
Are you using external dongles with Cerbo? It’s probably not linked to this case but without external dongles Cerbo Bluetooth is not very reliable.
Have you tested if you receive data all the time with Ruuvi Station app or do you use this app at all?
I use VRM a bit but I’m no expert. There is a real time mode feature in VRM. Is it possible that real time VRM is expecting a continuous signal but the RuuviTag is sending discrete signals only every 30 seconds (the frequency I use)?
EDIT: The RuuviTag is communicating with the Cerbo GX. Nothing else. VRM reads from the Cerbo GX’s values. VRM doesn’t communicate directly with the RuuviTag.
It’s not possible, RuuviTag is sending data 1,285s interval and it doesn’t know anything about the receiver. This is continuing until battery is completely empty. You also cannot change this frequency on the RuuviTag, it’s fixed (unless some other firmware is changed manually)
If there’s green led blinking on the sensor it’s sending data all the time (it’s very dim). You can also verify that RuuviTag is sending data using our own app - Ruuvi Station.
Cerbo is listening Bluetooth data what RuuviTags are sending, and according to my understanding it’s stored to Victron own cloud where VRM dashboard is getting the data.
I would wrote about this issue to Victron own forum as it most probably relates to two Cerbo and VRM installation. There’s no any communication from VRM/Cerbo to RuuviTag direction, so the probability that problem is on the RuuviTag is not very high.
If you don’t use external Bluetooth dongle on Cerbo, it can also cause issues. More about dongles here Connect ruuvi to CCGX or Venus GX - VictronEnergy
@henri, thanks for the clarification. I was confusing my Mopeka sensors with my RuuviTag sensors. The Mopeka sensor can be configured for longer periods of times between broadcasts.
I have ordered a couple of dongles will see if that fixes the issue or not when they arrive
My best guess is that VRM doesn’t handle or not tested if there are same ID sensor installed to two separate systems. I might be also linked to Cerbo Bluetooth issue without dongle. But best answer to these questions can be get from Victron support forum.
It’s almost impossible that it would be related to sensor, as sensor doesn’t know how many devices are listening data what the sensor is broadcasting.
Dont think so as Mopeka sensors have No Issue with 2 systems same ID
Not the issue as same with tested approved dongle
Humm???
That Mopeka is working doesn’t mean that the VRM would handle same way Ruuvi sensors. Software doesn’t work like that as they are completely different software parts and can have totally different bugs and way how they work.
RuuviTag sensor is not connected to VRM, it’s one one way broadcast without any knowledge what kind of devices are listening the sensor data. RuuviTag sensor doesn’t know if there are 1 or 1000 VRM listening/getting data from the RuuviTag sensor. It for example doesn’t receive any information if the sensor data is received or not as there’s no way to connect to the sensor and get that kind of information.
Most important question: When you don’t get data to VRM, do you get the data from the RuuviTag sensor to Ruuvi Station mobile app?