Domoticz

kraades wrote:

sanderl wrote:Ok read the entire post and I am impressed!
Iam experimenting with domoticz running on my synology nas fine. Today I was looking in the hardware list and I saw this Nefit Easy HTTP server over LAN interface. I filled in the ip address and tried some port numbers... despite. And then after reading this entire post with all kid of versions, scripts, http server, versions (pi etc)... what do I do, where do i start? Can i fet some directions please?

If you use the build-in Easy support you need the easy http server.
If you want to run it on your Synology you need to install node v4.x or higher. You can try to download the binaries from nodejs.org. The arch arm, x86 etc. depends on the Synology that you have.
You cannot use the nodejs package from synocommunity (version is too old).
If you have node and npm installed (=download en unpack in for example /usr/local/bin) you can install the easy http server using npm.

Edit:
Deleted

jumbotroll wrote:

kraades wrote:

sanderl wrote:Ok read the entire post and I am impressed!
Iam experimenting with domoticz running on my synology nas fine. Today I was looking in the hardware list and I saw this Nefit Easy HTTP server over LAN interface. I filled in the ip address and tried some port numbers... despite. And then after reading this entire post with all kid of versions, scripts, http server, versions (pi etc)... what do I do, where do i start? Can i fet some directions please?

If you use the build-in Easy support you need the easy http server.
If you want to run it on your Synology you need to install node v4.x or higher. You can try to download the binaries from nodejs.org. The arch arm, x86 etc. depends on the Synology that you have.
You cannot use the nodejs package from synocommunity (version is too old).
If you have node and npm installed (=download en unpack in for example /usr/local/bin) you can install the easy http server using npm.

I have compiled some Node v.5.3.0 test versions for arch-armadaxp and arch-x86.
This is compiled with DSM 6.0 Beta toolchains (gcc-4.9), but it's running nice here on DSM 5.2 DS712+ arch-x86.
node_armadaxp-6.0_5.3.0-5.spk
node_x86-6.0_5.3.0-5.spk
http://www.jadahl.com/domoticz_beta/ind ... llist=true

Thanks!
Ehhh, can you please help how to install 'easy http server' on Synology?
appreciated!

Sorry I 'm not familiar with easy http server.
Not using this myself.
Do you need easy http server on synology?

It's some bug with the Node 5.30 packages.
Need some more testing, so I will delete tha packages for now.

Doler wrote:

pepijn wrote: I modified the flow to use JSON HTTP instead of MQTT. Now i only use MQTT for setpoint changes. Please note you have to edit the Build HTTP Request function to your Domoticz settings.

Pepijn, thanks. I've got it running and will see if this is more stable. I'll keep you updated.
Thanks, Mark

The promised update.
Running fora week now with hardly any problems. I've had one occasion (in the night) where the connection was lost, so Domoticz wasn't updated. Opening the Nefit app on my tablet apparently restored the connection and all was well again. In the log I see infrequent timeouts, but last night between approx. 2 and 5 continuously timeouts (Nefit/Bosch being updating?) but after that no problems. So you have a happy user .
Any plans on adding more functions (or instructions how to do it myself?).
Thanks, Mark

Just noticed that in beta 2.4409 there is native Easy support build into Domoticz. Just tried it (also needs the http-server) and seems to work.

SweetPants wrote:Just noticed that in beta 2.4409 there is native Easy support build into Domoticz. Just tried it (also needs the http-server) and seems to work.

Yes there is, but as you can see in the release notes it's experimental. It was created because we have seen a problem when using MQTT.

pepijn wrote:Yes there is, but as you can see in the release notes it's experimental. It was created because we have seen a problem when using MQTT.

I use domoticz MQTT (domoticz/in) all the time, and never have seen an issue with it, but I run on a NUC using Ubuntu, not on RPi.

Can someone give some guidance on the settings? really like to test this one!

SweetPants wrote:

pepijn wrote:Yes there is, but as you can see in the release notes it's experimental. It was created because we have seen a problem when using MQTT.

I use domoticz MQTT (domoticz/in) all the time, and never have seen an issue with it, but I run on a NUC using Ubuntu, not on RPi.

Yep I'm running a Ubuntu VM and not able to reproduce it. Maybe the Node Red send a wrong formatted message.

But I changed the flow to json so there is another workaround. Just to explain the background.

Marcel wrote:Can someone give some guidance on the settings? really like to test this one!

Enable the new Easy hardware, point to the running easy web-server (ip, port) and enable new hardware. It will create a bunch of devices for you.

Update... password was incorrect!!!! it is running now


Think I am pretty far now, after some challenges I now have an issue where google is not helping me finding an answer...

I am running Node v5.3.0 and npm 3.3.12. have set the serial etc through export. when running easy-server command this happens:

Just updated the node-red flow to the json version. Let's see if this is more stable. Every other day Domoticz stopped logging everything.

The Native Easy is working very stable for me with regard of data updates have it running now for 3 days. Have only one issue. On my iphone I have added the "Temperature setter" as favorite on my dashboard. When loading the mobile version of the webpage the button to set the temp appears, if the page remains open for a couple of seconds the button (after a data refresh?) disappears and becomes a static label. Anyone else have the same?

jeroenkl wrote: Ehhh, can you please help how to install 'easy http server' on Synology?
appreciated!

As an alternative to a Synology package or installating it manually -and if you have a Synology that can run Docker- you can also use the following Docker image:
https://hub.docker.com/r/trafex/nefiteasy-http-server/

kraades wrote: As an alternative to a Synology package or installating it manually -and if you have a Synology that can run Docker- you can also use the following Docker image:
https://hub.docker.com/r/trafex/nefiteasy-http-server/

That is working like a charm! Thank you so much for this solution.

I'm trying to install the webserver on my Raspberry Pi2, but no luck:

after entering the next log is generated:
Internet connection is available and the page mentioned after GET does actually exist. Any advice?

Regards,
Niels

Niels wrote:I'm trying to install the webserver on my Raspberry Pi2, but no luck:

after entering

Code: Select all

npm i nefit-easy-http-server -g

the next log is generated:

Code: Select all

info it worked if it ends with ok
verbose cli [ '/usr/bin/nodejs',
verbose cli   '/usr/bin/npm',
verbose cli   'i',
verbose cli   'nefit-easy-http-server',
verbose cli   '-g' ]
info using [email protected]
info using [email protected]
verbose config file /home/pi/.npmrc
verbose config file /usr/etc/npmrc
verbose config file /usr/share/npm/npmrc
verbose cache add [ 'nefit-easy-http-server', null ]
silly cache add: name, spec, args [ undefined,
silly cache add: name, spec, args   'nefit-easy-http-server',
silly cache add: name, spec, args   [ 'nefit-easy-http-server', null ] ]
verbose parsed url { pathname: 'nefit-easy-http-server',
verbose parsed url   path: 'nefit-easy-http-server',
verbose parsed url   href: 'nefit-easy-http-server' }
verbose addNamed [ 'nefit-easy-http-server', '' ]
verbose addNamed [ null, '' ]
silly name, range, hasData [ 'nefit-easy-http-server', '', false ]
verbose raw, before any munging nefit-easy-http-server
verbose url resolving [ 'https://registry.npmjs.org/', './nefit-easy-http-server' ]
verbose url resolved https://registry.npmjs.org/nefit-easy-http-server
http GET https://registry.npmjs.org/nefit-easy-http-server
ERR! Error: failed to fetch from registry: nefit-easy-http-server
ERR!     at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12
ERR!     at cb (/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9)
ERR!     at Request._callback (/usr/share/npm/lib/utils/npm-registry-client/request.js:136:18)
ERR!     at Request.callback (/usr/lib/nodejs/request/main.js:119:22)
ERR!     at Request.<anonymous> (/usr/lib/nodejs/request/main.js:212:58)
ERR!     at Request.emit (events.js:88:20)
ERR!     at ClientRequest.<anonymous> (/usr/lib/nodejs/request/main.js:412:12)
ERR!     at ClientRequest.g (events.js:156:14)
ERR!     at ClientRequest.emit (events.js:67:17)
ERR!     at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1256:7)
ERR! You may report this log at:
ERR!     <http://bugs.debian.org/npm>
ERR! or use
ERR!     reportbug --attach /home/pi/npm-debug.log npm
ERR! 
ERR! System Linux 4.1.17-v7+
ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i" "nefit-easy-http-server" "-g"
ERR! cwd /home/pi
ERR! node -v v0.6.19
ERR! npm -v 1.1.4
ERR! message failed to fetch from registry: nefit-easy-http-server
verbose exit [ 1, true ]

Internet connection is available and the page mentioned after GET does actually exist. Any advice?

Regards,
Niels

You need NodeJS 4

I had, but apparently not installed in the right way. Reinstallation did the trick. Thanks!

Short question: does this all work on Jessie?

Verstuurd vanaf mijn Nexus 6P met Tapatalk