New Venus OS 3.50 UI issue adding BT Sensor - RuviTag

DIY
,
1

Not sure if this is the correct method for reporting issues with the new UI, but I ran into two issues today integrating an additional RuviTag into my Ekrano GX system today.

  1. After adding a RuviTag BT 4-1 temp sensor into my system by enabling scanning and turning the sensor on in the I/O>Bluetooth Sensors menu, the sensor did not appear in the Device List menu even when connected. This was the 2nd RuviTag sensor added to the system, but the first sensor configured in 3.50. The previous BT sensor was added months ago. Even so, I was finally able to get the sensor to appear in the Device list so I could configure after a system reboot of the Ekrano GX.
  2. When the RuviTag did appear in the Device list after a system reboot, I was not able to select the device type “Freezer.” When selected, the system just ignored the selection. No issues with making the sensor a “Fridge” type and renaming the device “Freezer.” Not sure if this was by design.
2

For me if I select Battery, Fridge or Generic they work (stay selected) but if I select any of the others it will just stay on whatever I have previously selected (one of the three above)

All of mine were added months ago.

3

Thank you for confirming. I experienced the same. Something to add to the list for future updates.

4

I too am experiencing the same issue since updating my Cerbo-S GX to Venus OS 3.50. I have 3 RuuviTags that I use to measure fridge, inside and outside temperatures all of which were added under Venus OS 3.42. I have tried changing the type for the inside and outside tags to Room and Outside respectively but the setting reverts to Generic.

It seems from what @joeAV451 says there’s no point in me spending time today removing the delinquent tags, rebooting the system and re-installing them in the hope they can be set to one of the new types.

Fingers crossed that someone will be along later with some new magic to get the OS to remember a type other than Generic for my inside & outside tags and help you other guys too. :crossed_fingers: :crossed_fingers:

5

Yes let’s wait i am sure @guystewart are aware of this and will fix soon.

1 Like
6

Hi all, noted. Will he looked into.

Meanwhile, as a work around, you can revert back to the Classic UI, set everything up, can then change to the New UI again.

1 Like
7

No, it does not work either. Only the first 3 choices are shown.

8

A post was split to a new topic: 3:50 Feature request - can we have some color back?

9

Sadly changing to Classic UI doesn’t help. Classic UI, and for that matter Node-Red, only allows the type to be set as Generic, Fridge or Freezer.

So, meanwhile I’ll continue to appreciate the new UI and look forward to being able set one of additional types on my Ruuvi once this issue is fixed.

10

Temperature senders

  • Fix issue where, depending on sensor type versus UI combination, it wasn’t possible to select temperature types other than Battery, Fridge or Generic. Fixed for all combinations and situations.

Hi @mpvader i can confirm (for me) in v3.52~4 this indeed is now fixed, thanks to all the team :+1:

11

Same here. v3.52~4 supports selection of freezer sensor type and resolves issue #2. Thank you!.

I did not confirm v3.52~4 addresses issue #1 that a newly added BT sensor does not show in the device list until Ekrano GX is rebooted.

12

Can confirm that v3.52~4 contains the missing magic to fix my issue with the selection of the full range of types for my Ruuvi temperature sensors.

Thanks.

13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.