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

How to inject a message daily when sun azimuth equals 250 #148

Closed
mattmattmatt opened this issue May 21, 2020 · 5 comments
Closed

How to inject a message daily when sun azimuth equals 250 #148

mattmattmatt opened this issue May 21, 2020 · 5 comments
Assignees
Labels
🕙 awaiting feedback waiting for feedback from ticket owner 💡 enhancement New feature or request

Comments

@mattmattmatt
Copy link

What's the recommended way to inject a message once per day when the sun's azimuth equals e.g. 250?

It seems like the inject at time node should be able to do this, but it only seems to support hardcoded sun events like sunset and nautical dawn. I tried to hack it with the alternate time functionality of that node, but to no success.

I worked around this issue currently by blindly injecting a message into the system every minute and then checking with the sun position node if the azimuth equals a certain value. While this works, it seems overly complex and not ideal.

image
Workaround

@Hypnos3
Copy link
Collaborator

Hypnos3 commented May 21, 2020

This is an interesting use case. The time Inject node currently only support fixed azimuth angles which are the sun times. There is a possibility to adding a time offset to these timestamps.

The way you modeled it is currently the only way. I will think 🤔 about it, if I could implement this in any way.

@mattmattmatt
Copy link
Author

Thanks for the quick response. 🙏

It sounds like since sunset is based on a fixed azimuth, a similar check could be done with an arbitrary azimuth as well. In any case, thanks for looking into it 👍

Hypnos3 added a commit that referenced this issue May 24, 2020
- blind-control + clock-time
  - fixed missing topic from rules #150
  - fixed last until rule will not be evaluated
  - maybe fix of #152

- general
  - for any simple time input added possibility to add time as format `HH:MM UTC` or `HH:MM:SS UTC` to force UTC Format
  - added time calculation by azimuth and elevation (is not fully tested) #148
@Hypnos3
Copy link
Collaborator

Hypnos3 commented May 24, 2020

I have implemented something in version 1.1.1, but it is not really tested.

@Hypnos3 Hypnos3 self-assigned this May 24, 2020
@Hypnos3 Hypnos3 added 💡 enhancement New feature or request 🕙 awaiting feedback waiting for feedback from ticket owner labels May 24, 2020
@no-response
Copy link

no-response bot commented Jun 23, 2020

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Jun 23, 2020
@Hypnos3 Hypnos3 reopened this Jun 24, 2020
@no-response
Copy link

no-response bot commented Jun 24, 2020

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕙 awaiting feedback waiting for feedback from ticket owner 💡 enhancement New feature or request
Development

No branches or pull requests

2 participants