Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Smart main' not synced #152

Open
Ryton opened this issue Oct 26, 2016 · 6 comments
Open

'Smart main' not synced #152

Ryton opened this issue Oct 26, 2016 · 6 comments

Comments

@Ryton
Copy link
Contributor

Ryton commented Oct 26, 2016

Some OG-res (open grid respondents :P) also gave (or only gave) their smart main sensors and token.

For example: FL03001579
However, the smart-main series are not synced trough tmpo.

Can this be resolved, either by replacing the smart main data with the non-smart sensor data, or updating all 'smart main' ID-s and tokens from the houseprint?

@saroele
Copy link
Member

saroele commented Oct 26, 2016

You have hit a nail :-) We have to solve these default smart sensors.
They often don't contain any data.

I think it's a good idea to try to sync data for any sensor that has been
configured by an OG-res, but when no data is available, there should be no
processing and no link on the website.

On Wed, Oct 26, 2016 at 11:23 AM, J. Ver. [email protected] wrote:

Some OG-res (open grid respondents :P) also gave (or only gave) their
smart main sensors and token.

For example: FL03001579
However, the smart-main series are not synced trough tmpo.

Can this be resolved, either by replacing the smart main data with the
non-smart sensor data, or updating all 'smart main' ID-s and tokens from
the houseprint?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opengridcc/opengrid/issues/152, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiVBpVmFc9cD0XkzSnDvcrktv58fYB7ks5q3xwogaJpZM4Kg8Vu
.

@JrtPec
Copy link
Member

JrtPec commented Oct 26, 2016

I have added a property for the fluksosensor to check if it has data or not, we could use that to filter views

@saroele
Copy link
Member

saroele commented Nov 27, 2016

I think we have this this issue in #166.
Before applying a quick change, we should write a unittest.

@JrtPec
Copy link
Member

JrtPec commented Nov 28, 2016

We would have to mock a sensor in tmpo...

Something like:

hp.tmpos.add('mock', 'mock')
...
# do not sync tmpos because it will fail with false sensor info
test_sensor = FluksoSensor('mock', ...)
assertFalse(test_sensor.has_data)
hp.tmpos.delete('mock', 'mock')

@saroele
Copy link
Member

saroele commented Nov 28, 2016 via email

@JrtPec
Copy link
Member

JrtPec commented Nov 28, 2016

Sure, we could do this in the mock houseprint object that we use in the tests somewhere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants