[SOLVED] reactor_inet_check script... and containers

[Matteburk]

Him ... Got The reactor up and running but I can't see my Vera Plus and Hubitat.

I have restarted the reactor after doing necessary input in the reactor.yaml file.reactor:

What could I be doing wrong? Runs on a RPI

Is it correct ?

baseurl - The base URL to access the Reactor system.

baseurl: "http://192.168**.***:8111"

units - imperial or metric

units: metric
location:node app js
city: "Stockholm City"
# Non-US users please use "province"
state: "GA"
#province: "Akersberga"
postal: "18494"
# Must be ISO two-character country code (i.e. the ISO 3166-1 Alpha 2 code)
country: "SE"
# Must be properly set for sunset/sunrise calculation.
latitude: 59.26465
longitude: -18.14490
# Units of elevation are meters (multiply feet by 0.3408 to get meters)
elevation: 0

controllers:

• id: vera
  enabled: true
  implementation: VeraController
  name: Penthouse
  config:
  source: 'http://192.168..*_3480'

• id: hass
  enabled: false
  implementation: HassController
  name: A Home Assistant system
  config:
  source: 'http://192.168.0.7:8123'
  access_token: "place long-lived access token within"

• id: hubitat
  enabled: true
  implementation: HubitatController
  name: Penthouse
  config:
  source: 'http://192.168..'
  access_token: '*************************************'

[Matohl]

location:node app js is not correct, it should be:

location:
city: .....

[toggledbits]

If this is in config and not dist-config then you are off to a good start. A couple of notes:

1. Remove the # from before province, and place a # before state -- you modified the data, but didn't comment/uncomment the fields.
2. The way you posted it lost the indenting, which is critical for YAML. It needs to be indented using spaces only (no tabs) exactly as the original version was. If you are not sure, the original distribution versions of the config files are in dist-config and you can use them as a reference, or copy them to config and start over.

Like the Vera Community, if you want to post a code block, put three back-ticks ``` on a line by itself, then your code, and then a line with three back-ticks again, and it will format it properly and not wreck the quotation marks and indenting.

Also, please start new threads for new topics. If every discussion happens in this one thread, we're going to have a bad time.

[Matteburk]

@toggledbits Ok Thanx a lot. Got it working with Vera but got stuck with Hubitat for a couple of hours trying everything until I read that Hubitat has limitations when you have more Maker API connections.
I have an RPI connected with Homebridge running against Maker API so I guess its the problem so if you can boost a solution was you mentioned it wood be greeeeat...

So no I will start playing with the Vera until a solution is ready..:)

/Mattias

[toggledbits]

Do you know, does HomeBridge set the POST URL automatically, or did you have to set it (e.g. copy-paste from somewhere)?

[Matteburk]

@toggledbits I can't remember doing it... Here is a link for the Maker API homebridge instruction...

Apr 15, 2019

New Homebridge Plug-in via MakerAPI

This new plugin does not rely on the "Homebridge App" in Hubitat and utilizes the MakerAPI and it's event stream to communicate with Hubitat. A few caveats upfront: You will have to redo all of your room assignments in the Home App on your phone Installation: 1. Hubitat MakerAPI App...

[toggledbits]

Guess we'll just have to try it and see what happens. I think there's a high probability it sets it itself, which will be a problem. I was so gung-ho on Hubitat until I started really getting into it and finding things like this. Bummer.

[Matteburk]

@toggledbits I have deleted the homebridge Maker API app and installed homebridge v2 that does not use Maker API but the reactor still doesn't want to connect to Hubitat. you have got it to work with Hubitat?
I read on a Hubitat thread that the Post has to be sent to the Maker API as you mentioned ...
I have played a bit with my vera and MSR and it works good so far. So nice to be back to Reactor, have missed it a lot . It still sits in thespinal cord! :).

[toggledbits]

@matteburk said in Can't see VeraPlus and Hubitat (config question):

you have got it to work with Hubitat?

Yes. There are two parts to the connection, so even if the POST URL is a problem, you should be able to see your devices. Make sure you are following the installation instructions correctly, and have the correct IP address in the configuration. You might also look at 'logs/reactor.log' after startup and see if there are any helpful messages there.

[Matteburk]

Been trying around and did new installation of MSR but still not work with Hubitat. I cant se any devices.
The MSR logs says:
2021-02-23T05:47:10.927Z Controller:ERR HubitatController#hubitat failed to connect/query http://192.168.68.145: Error: Request failed: 404 Not Found
2021-02-23T05:47:15.934Z Controller:NOTICE HubitatController#hubitat not ready; performing initial connect/query

The HUBITAT logs says:
sys:12021-02-23 11:37:32.680 Received local request for App 8 that does not exist, path: /devices/* from unknown

They are not from same time.... The msr is bombing the Hubitat with tries. ( so often that the Hubitat has hard doing stuff)

Ive done the installation as in the instructions.... Can the old Maker API still keep the 1 and only connection even if I have deleted it?..

[toggledbits]

If I had to guess, you have the access token wrong. Please PM me your the Hubitat controller configuration from your reactor.yaml file, and make a screen shot of your Maker API app where it shows the local URLs with the access token on them (scroll down).

[Matteburk]

ok here itr is Skärmavbild 2021-02-23 kl. 19.10.20
Skärmavbild 2021-02-23 kl. 19.10.00

- id: hubitat
  enabled: true
  implementation: HubitatController
  name: A Hubitat Elevation system
  config:
    source: 'http://192.168.68.145'
    access_token: "4421ed2b-4d85-4686-a104-23b3632a7824"

[toggledbits]

OK. I see the issue. I assumed something about the structure of their URLs that apparently I can not, so I'll need to fix that. Today's daily build will have a fix.

[Matteburk]

ok great!

[Matteburk]

Here is the rest of the Maker API below Skärmavbild 2021-02-23 kl. 19.38.54

[toggledbits]

OK, so when you upgrade to 21054 later today or tomorrow (should be published tonight my time Eastern US), you will just copy-paste the "Get Device Info" URL given there, or you can right-click the "Get All Devices" link above it and then paste that into your configuration. The updated HubitatController will just take that URL apart to get the information it needs. You should not even need to specify access_token any more (if it's on the URL, it will grab it). Coming soon...

[Matteburk]

ok perfect. that's the way other Maker API apps works , uses the hole url string with token.. Good work Patric!

[toggledbits]

Yeah, what I got wrong was that number in the middle. I assumed, very incorrectly apparently, that is was a universal application ID or an API version number, something relatively static. Well, it's an application ID, but not universal, or static--it's apparently going to be different on every Hubitat. Teething pains. And cheesus ghost, their documentation is horrible.

Speaking of documentation, and forums, on their forums is much discussion about the Post URL magically vanishing, or not working. So that's the next thing to watch out for.

[Matteburk]

Not just the documentation.... their Rulemachine can be soooo annoying! Speaking of documentation Whats the easiest way to update the msr?

[toggledbits]

Easiest way? I think... read the documentation! Look at the "Installation" page. You can use the "Manual" link in the left navigation of MSR, or click the link below:

MSR docs: Installation