Andras/BoundlessFlowCampus2K
4
7
Fork 0
Code Issues 90 Pull requests 7 Projects Releases Packages Wiki Activity Actions

Additional microservices for monitoring for multiple sensors #7

New issue
Closed
opened 2026-03-27 14:49:02 +00:00 by Andras · 4 comments
Andras commented 2026-03-27 14:49:02 +00:00
Owner
Copy link

Right now, we only have a single sensor. Displaying multiple sensors (even on a mock-up level to show the interface) for 8 different sensors should be preferred.

Right now, we only have a single sensor. Displaying multiple sensors (even on a mock-up level to show the interface) for 8 different sensors should be preferred.
c24danli commented 2026-04-08 10:50:05 +00:00
Collaborator
Copy link

If i understand it correctly, this issue is about adding additional sensors that messures temp in diffrent places/rooms and then displaying them sepratly?

If i understand it correctly, this issue is about adding additional sensors that messures temp in diffrent places/rooms and then displaying them sepratly?
a22erigr commented 2026-04-09 09:23:16 +00:00
Collaborator
Copy link

Now pair programming with c24danli

Now pair programming with c24danli
a22erigr commented 2026-04-09 12:57:09 +00:00
Collaborator
Copy link

It's now possible to retrieve data from multiple sensors.

It's now possible to retrieve data from multiple sensors.
a22erigr commented 2026-04-09 13:04:36 +00:00
Collaborator
Copy link

Having problem with retrieving/sorting data from a specific sensor. Noticed that the postgresDB utilities a general table structure

  • id
  • timestamp (when data was inserted into table)
  • payload
    It is in the payload all the temperature data is stored
  • temperature
  • sensorId
  • timestamp (when data was retried)

When we tried to implement we assumed that the sqlite and postgresDB tables were identical. Because this was not the case a lot if interesting bugs appeared.

Worked with c24danli

Having problem with retrieving/sorting data from a specific sensor. Noticed that the postgresDB utilities a general table structure + id + timestamp (when data was inserted into table) + payload It is in the payload all the temperature data is stored + temperature + sensorId + timestamp (when data was retried) When we tried to implement we assumed that the sqlite and postgresDB tables were identical. Because this was not the case a lot if interesting bugs appeared. Worked with c24danli
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
#1236-edit-mode-txt
#1229-generic-themed-buttons
Add-an-option-to-set-no-image-to-image-view-1227
#1242-prog-bar-colors-fix
#1239-Remove-Vertical-Scroll
Image-view-error-1230
Make-the-card-title-and-header-of-card-uniform-1233
both_teams_week_8
team_2_week_7
team_1_week_7
temp_branch_week_7
team_2_week_6
team_1_week_6
team_2_week_5
team_1_week_5
temp_branch_week_5
team_2_week_4
team_1_week_4
week_4_temp_branch
temp-branch-week-3
team_2_week_3
team_1_week_3
team_2_week_2
team_1_week_2
temp-week-2-merge-branch
team_2_week_1
team_1_week_1
No results found.
Labels
Clear labels   
_CRITICAL_

Only use this label for critical tasks that are project-scope,and must be addressed ASAP.

  
API

   
app

   
backEnd

   
Blocked, waiting for further changes

   
bug

Something is not working

  
cleanup

Issues to cleanup the codebase (restructure folders, remove deprecated or smelly code)

  
close

Issue to close

  
design

   
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
feature request

   
frontEnd

   
help wanted

Need some help

  
invalid

Something is wrong

  
low priority

   
needs input

Issue needs input from product owner or customer

  
needs review

issue is in need of review

  
project documentation

   
question

More information is needed

  
research

   
reviewed

This Issue has been reviewed

  
script

   
security

use this for security-related issues

  
SQL

  
style

   
testing

   
topLevel

Reserved for top-level, project-wide issues.

  
wontfix

This won't be fixed

No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
c24danli
a22erigr
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#7
No description provided.