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

Negative longitude numbers are turned into "true" #130

Open
claudiuo opened this issue Mar 12, 2014 · 3 comments
Open

Negative longitude numbers are turned into "true" #130

claudiuo opened this issue Mar 12, 2014 · 3 comments

Comments

@claudiuo
Copy link
Contributor

Trying to set the longitude value to a negative number (which is the case in the western hemisphere) I discovered that the value is set to true instead of the real value. So this:
publish.js -t "/sys/294028-solar/longitude" -p "-111.890810" -r
doesn't work. I tried all kinds of combinations until I found this issue: https://github.com/substack/node-optimist/issues/79

Indeed, setting the payload like:
publish.js -t "/sys/294028-solar/longitude" --payload=-111.890810 -r
seems to work.

It is a bug in optimist so not much you can do, I thought maybe you could mention in the docs for solar and weather this issue.

Thanks for all your work, it is really great!

@binarybucks
Copy link
Owner

Ah yes, this was reported somewhere else before and as you mentioned a bug
in optimist. Alternatively you can also use mosquitto_pub if you've the
Mosquitto Python tools installed. Could you submit a pull request with
updated docs?

On Wed, Mar 12, 2014 at 7:23 PM, claudiuo [email protected] wrote:

Trying to set the longitude value to a negative number (which is the case
in the western hemisphere) I discovered that the value is set to true
instead of the real value. So this:
publish.js -t "/sys/294028-solar/longitude" -p "-111.890810" -r
doesn't work. I tried all kinds of combinations until I found this issue:
substack/node-optimist#79https://github.com/substack/node-optimist/issues/79

Indeed, setting the payload like:
publish.js -t "/sys/294028-solar/longitude" --payload=-111.890810 -r
seems to work.

It is a bug in optimist so not much you can do, I thought maybe you could
mention in the docs for solar and weather this issue.

Thanks for all your work, it is really great!


Reply to this email directly or view it on GitHubhttps://github.com//issues/130
.

Mit freundlichen Grüßen / With kind regards
Alexander Rust

@claudiuo
Copy link
Contributor Author

That's what I did, I used mosquitto_pub, and was happy to do it since it
was the first time ever using it and loved to learn how to do it.

I will do the docs, thanks a lot for suggesting it. I will have to figure
it out though, since I never did a pull request. But it is time to learn
this as well, so thank you for pushing me to do this.

On Wed, Mar 12, 2014 at 2:04 PM, Alexander Rust [email protected]:

Ah yes, this was reported somewhere else before and as you mentioned a bug
in optimist. Alternatively you can also use mosquitto_pub if you've the
Mosquitto Python tools installed. Could you submit a pull request with
updated docs?

On Wed, Mar 12, 2014 at 7:23 PM, claudiuo [email protected]
wrote:

Trying to set the longitude value to a negative number (which is the
case
in the western hemisphere) I discovered that the value is set to true
instead of the real value. So this:
publish.js -t "/sys/294028-solar/longitude" -p "-111.890810" -r
doesn't work. I tried all kinds of combinations until I found this
issue:
substack/node-optimist#79<
https://github.com/substack/node-optimist/issues/79>

Indeed, setting the payload like:
publish.js -t "/sys/294028-solar/longitude" --payload=-111.890810 -r
seems to work.

It is a bug in optimist so not much you can do, I thought maybe you
could
mention in the docs for solar and weather this issue.

Thanks for all your work, it is really great!

Reply to this email directly or view it on GitHub<
https://github.com/binarybucks/homA/issues/130>
.

Mit freundlichen Grüßen / With kind regards
Alexander Rust

Reply to this email directly or view it on GitHubhttps://github.com//issues/130#issuecomment-37457228
.

binarybucks pushed a commit that referenced this issue Mar 13, 2014
@simonvanderveldt
Copy link
Contributor

Is this still something that needs fixing? As it's also already been added to the docs.

I found this commit from Turfjs/turf-point that was done to address the same issue, maybe it can be of help?

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