Logic Programming

[PerH]

It's getting ready now, and I uploaded a "release" to github in a fork from the original. Do I have to upload to the original repository to make it available in AppStore?

@akbooer: This plugin has a script that is run in domoticz to get async updates. How is that done in zway/vera bridge? (in short, and laymans terms please)

[PerH]

About Zerobrane: Sometimes the output shows "The syntax of the command is incorrect", how do i find where precisely that is?

[akbooer]

@perh said in Domoticz Bridge:

This plugin has a script that is run in domoticz to get async updates. How is that done in zway/vera bridge? (in short, and laymans terms please)

Sorry, not quite clear what you're asking here. Can you expand on this?

[PerH]

How does Vera tell Openluup that a value needs updating?

[PerH]

And how is this possible?

No reading here:

No info here:

While the data is obviously available?

[therealdb]

@perh it’s polling, not pushing. So it’s openluup getting values from the Vera.

[PerH]

I C, but then, "asyc poll" is just that it sends a report immediately on changes done in openluup, but changes on Vera will not be updated until next polling round?

[akbooer]

The lack of display must mean that the serviceId/variable name does not match the one defined in the device .JSON file. It’s an AltUI thing, not an openLUup one per se.

[therealdb]

@perh if you’re trying to mirror things using domoticz => openLuup => Vera, then yes

[PerH]

Sorry if i'm mixing things together here;
I have no Vera in my system, i'm simply trying to understand the mechanism used in Vera/Ezlo bridge to see if that would simplify the Domoticz Bridge.

Right now its a bit more complicated to install, as you have to set up a script at the Domoticz side as well. This script is triggered by any change on the devices on the Domo side, and immediately sends an update on the device to OpenLuup.
That seems to be even faster than the mechanism in VeraBridge, so i guess its worth keeping.

[PerH]

@rafale77 : Where can I find your Barometer sensor files?

I see that the ones I have mixes "micasaverde-com" and "upnp-org" in the service definitions, and its also missing an icon..

@perh said in Domoticz Bridge:

It's getting ready now, and I uploaded a "release" to github in a fork from the original. Do I have to upload to the original repository to make it available in AppStore?

Anyone who can help with this question?

[akbooer]

@perh said in Domoticz Bridge:

Do I have to upload to the original repository to make it available in AppStore?

You're talking about the Alt App Store?

It can only install from one GitHub repository at a time. You could either copy what you need into your, or add another compeltely separate entry pointing to the other required repository. You can shoose to download only selected files from any repository using the filename filter.

Sorry, realise that this might sound a bit cryptic. Can you explain a little further what you're actually trying to achieve?

[PerH]

Well, I've made a 0.2 version of the Domoticz Bridge, and want it to be available in AltAppStore. (Don't use Vera anymore, so i won't be adding it to that appstore myself)
DomoticzBridge is currently in there at 0.16, so how do I update that so the 0.2 is available? I'm not fully versed in Github yet either..

[akbooer]

The 1.6 version repository belongs to @logread. Should that be retained? I'm not going to do anything there without the original author's permission.

Your alternative is simply to create it as a new and separate plugin, if that's not too confusing for the users.

I can make the Alt App Store entry for you, I just need to know which GitHub repository to use (and which files.)

[PerH]

999LV has given me permission: https://github.com/999LV/DomoticzBridge/issues/1

Whatever works, just though mabye the .16 still works for those using Vera behind openluup or something like that? If so, the history should be retained?

[therealdb]

@perh said in Domoticz Bridge:

That seems to be even faster than the mechanism in VeraBridge, so i guess its worth keeping.

It will always be, because it’s pushing updates, vs waiting for the polling. I’ve recently released a ha-bridge plugin based on the same principles. It’s Vera/openLuup pushing to ha-bridge, instead of something polling Vera/openLuup and then update ha-bridge.

I’ll probably do the same for the upcoming new features for my mqtt bridge. You’ll basically install a plugin on your Vera and push everything to a bridge, that will publish them as mqtt messages.

[akbooer]

@perh

Let's just create another App Store entry for the moment – we can always merge later if required.

[PerH]

Ok, just uploaded to the master branch. Don't get the "release" function, I uploaded som files to that yesterday, but i've made updates after that which is reflected in the master branch..

[rafale77]

@perh

@perh said in Domoticz Bridge:

@rafale77 : Where can I find your Barometer sensor files?

I see that the ones I have mixes "micasaverde-com" and "upnp-org" in the service definitions, and its also missing an icon..

Hmm I created one myself along with defining a new subcategory number. I will be home in half a day and will post all the files in a zip here.

[akbooer]

@perh said in Domoticz Bridge:

Don't get the "release" function

Are you using Git from the command line, or an app?

I publish from an Apple Mac and the desktop app there is great.

Regarding releases, you may choose to tag a particular version as a release, which makes it easy to download/use. But you don't have to.

The Alt App Store is able to load both tagged release and specific (current) branches of your repository. In order not to have to update anything on the App Store, I generally just use the master or development branch to pull latest version.