Pending how you installed HA, you will need to install HACS first. Then you’ll be able to easily add those custom components, like Noonlight.
How did you install it on Linux Virtual Box? I.e Virtual Environment, Container, etc.
On Linux with Oracle Virtual Box.
followed the first bold bullet point of step 2 in the link below:
While the HACS web site seems to imply they have this repo, from HACS on home assistant searching for Noon provides no intergation. Is this component still supported via HACS?
I got the store installed. I just need to find how to get to the config file in the virtual machine now.
This would be great, Wyze if going to use Noonlight for their monitoring, so it would be cool if we could do the same thing in HA instead.
This is a perfect solution, I knew about Konnected but not this. Thank you!
Some time ago I spoke on the phone with a Product Manager from Noonlight and it was my understanding anyone could sign up for an API key. Sure it is a partner program but it doesn’t seem to be regulated in such a way that an individual can’t be their own client and that’s it.
@HA_fanatic appears to be correct: I am able to go to Noonlight’s website and sign up for API keys myself.
I literally signed up for the community just to comment in this thread. I think integration is incredible! I have been looking for a monitoring solution for a very long time and i think this is the winner. I’m interested in adding onto this integration adding support for fire/ems/police. Was looking to see how people thought this should be added in: 2 more switches, one switch for each service?
i’m limited on my HA development knowledge, but my next suggestion would to be pass in data like you pass in data for a light, but i’m not sure if this is possible.
1 Like
FYI - I updated the konnected-io noonlight-hass code base to the current V2 API supported by noonlight. V2 is considered to be their stable API. The changes were done in such a way so that you can continue to use the V1 API as it works today. To move to the V2 API you change the noonlight URL. With the change to V2 I change the code to send the house address instead of the gps coordinates. The address is provided as additional configuration values. The V2 API also requires the primary POC and phone number to be included in the message, which must also be included in the configuration. The code was also modified to utilize two text_input objects, which you can set in your alarm handling automation. One lets you select the service you want associated with the alarm: police, fire, medical. The other allows you to provide the cause of the alarm. I’ve done a pull request so hopefully the updates will be accepted and merged shortly. If you have comments on the pull request it’s available here:
1 Like
Not sure if this has been posted before, but I’m getting the following in my log.
No ‘version’ key in the manifest file for custom integration ‘noonlight’. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of ‘noonlight’
Has there been an official release to v2? I haven’t seen anything in HACS or listed as released on Git.
I’m not seeing this on 2021.4.6. Are you running the latest Ver. 1.0.1?
Nope. I’m running 2021.4.6 as well.
@bkprath @curt7000 thanks everyone for bringing up these issues. I’ll hopefully have some time this week to assess the minor changes to the manifest.json requirements and certainly review the PR for using the V2 API for Noonlight.
1 Like
Curious to see if there has been any progress on this.
Look like PR got approved but not merged yet.
Same here 2021.6 broke noonlight
Have not tried it yet, but appears you can modify the manifest.json in the meantime.