Page 42 of 55
Re: [MyDomoAtHome] Support thread
Posted: Sunday 08 October 2017 13:14
by epierre
Hmmm do you are running 0.2.29?
Re: [MyDomoAtHome] Support thread
Posted: Sunday 08 October 2017 14:49
by febalci
@epierre, Yes i am using 0.2.29. In the beginning I was running 0.2.26 on Synology using jadahl package, everything was working fine. Then i updated to 0.2.27 jadahl package; "tempmode not defined" error showed up. Updated to jadahl 0.2.29, same error again. Uninstalled jadahl 0.2.29 and reinstalled 0.2.29; same error again. Then i created a config.json file under /etc/mydomoathome as per your suggestion; this solved everything.
Re: [MyDomoAtHome] Support thread
Posted: Wednesday 11 October 2017 20:56
by epierre
ok thanks for the clarification, I've had many support request on the french forum, I'll investigate how to get this info from domoticz directly to avoid further issues like this...
Re: [MyDomoAtHome] Support thread
Posted: Saturday 21 October 2017 19:05
by reza
hi guys
i have problem...
Code: Select all
pi@raspberrypi:~ $ wget -q http://www.e-nef.com/domoticz/mdah/nodejs_4.4.2_armhf.deb
pi@raspberrypi:~ $ sudo dpkg -i nodejs_4.4.2_armhf.deb
(Reading database ... 139411 files and directories currently installed.)
Preparing to unpack nodejs_4.4.2_armhf.deb ...
Unpacking nodejs (4.2.2) over (0.10.29~dfsg-2) ...
dpkg: error processing archive nodejs_4.4.2_armhf.deb (--install):
trying to overwrite '/usr/bin/node', which is also in package nodejs-legacy 0.10.29~dfsg-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
nodejs_4.4.2_armhf.deb
Re: [MyDomoAtHome] Support thread
Posted: Saturday 21 October 2017 19:10
by epierre
Hello, you must remove the previous node package which conflicts
Re: [MyDomoAtHome] Support thread
Posted: Saturday 21 October 2017 19:10
by epierre
You must remove the previous node package whixh conflicts
Re: [MyDomoAtHome] Support thread
Posted: Sunday 22 October 2017 10:33
by reza
epierre wrote: ↑Saturday 21 October 2017 19:10
You must remove the previous node package whixh conflicts
thank you . resolve problem. but a question. i have a private ip (static) from my ISP.and a ip from modem for raspberry pi and a local ip for imperihome. i am confuse

i want when i am in home , so i can connect to domoticz locally(with raspberrypi ip) and when i am out of home can connect with private ip from isp.
now i can connect just locally. this is my setting:
http://127.0.0.1:8080/json.htm
http://192.168.1.201:3002
and i have a private ip from isp:
X.X.X.82
can you help me ?how do this setting for auto connect locally and remote (both) ?
Re: [MyDomoAtHome] Support thread
Posted: Sunday 22 October 2017 10:53
by epierre
Looks like a nat or firewall rule to add to your isp box
Re: [MyDomoAtHome] Support thread
Posted: Tuesday 24 October 2017 10:39
by Eternity
Installed the latest version on my Synology DS214+
The package starts, but stops after a couple of seconds:
This started after I installed the suggested update....
How can I solve this?
Thank you!
PS
Previously posted in wrong forum ... sorry
Re: [MyDomoAtHome] Support thread
Posted: Tuesday 24 October 2017 13:48
by epierre
@eternity as we said previously, you need to do:
ssh admin@nas
sudo mkdir /etc/mydomoathome
sudo nano /etc/mydomoathome/config.json
in the file do add:
{
"app_name": "MyDomoAtHome",
"auth": null,
"tempmode": "C",
"domoticz": {
"ssl": false,
"host": "127.0.0.1",
"port": "8084",
"path": "/",
"auth": null
},
"port": "3002",
"passcode": ""
}
Re: [MyDomoAtHome] Support thread
Posted: Tuesday 24 October 2017 14:11
by Eternity
@epierre
Sorry about that!
I managed to create the dir and file and all is working nicely again!
Thanks for the help!
Re: [MyDomoAtHome] Support thread
Posted: Tuesday 24 October 2017 14:16
by epierre
great ! I've not had time to overturn this issue htat does not occur on every syno ... will do that mater !
Re: [MyDomoAtHome] Support thread
Posted: Thursday 26 October 2017 15:00
by bmath
Hi ,
like many users, i've an issue with the last update.
i tried to apply what said before but nothing works.
in /etc/mydomoathome/config.json
Code: Select all
{
"app_name": "MyDomoAtHome",
"auth": null,
"tempmode": "C",
"domoticz": {
"ssl": false,
"host": "127.0.0.1",
"port": "7777",
"path": "/",
"auth": { "username": "login", "password": "passord" },
},
"port": "3002",
"passcode": ""
}
mydomoathome is installed with domoticz (port 7777) on the same raspberry.
when i tried to start MyDomoAtHome :
Code: Select all
error: Global conf parsing issue !
error: Error: Error parsing your configuration file: [/etc/mydomoathome/config.json]: Unexpected token }
at File.loadSync (/usr/share/mydomoathome/app/node_modules/nconf/lib/nconf/stores/file.js:160:11)
at Provider.add (/usr/share/mydomoathome/app/node_modules/nconf/lib/nconf/provider.js:137:23)
at Provider.use (/usr/share/mydomoathome/app/node_modules/nconf/lib/nconf/provider.js:110:10)
at loadGlobalConf (/usr/share/mydomoathome/app/mdah.js:94:9)
at Object.<anonymous> (/usr/share/mydomoathome/app/mdah.js:2701:1)
at Module._compile (module.js:435:26)
at Object.Module._extensions..js (module.js:442:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:311:12)
at Function.Module.runMain (module.js:467:10)
error: Global conf load issue !
error: Error: Error parsing your configuration file: [/etc/mydomoathome/config.json]: Unexpected token }
at File.loadSync (/usr/share/mydomoathome/app/node_modules/nconf/lib/nconf/stores/file.js:160:11)
at loadStore (/usr/share/mydomoathome/app/node_modules/nconf/lib/nconf/provider.js:396:26)
at /usr/share/mydomoathome/app/node_modules/nconf/node_modules/async/lib/async.js:356:13
at async.forEachOf.async.eachOf (/usr/share/mydomoathome/app/node_modules/nconf/node_modules/async/lib/async.js:233:13)
at _asyncMap (/usr/share/mydomoathome/app/node_modules/nconf/node_modules/async/lib/async.js:355:9)
at Object.map (/usr/share/mydomoathome/app/node_modules/nconf/node_modules/async/lib/async.js:337:20)
at loadBatch (/usr/share/mydomoathome/app/node_modules/nconf/lib/nconf/provider.js:405:11)
at Provider.load (/usr/share/mydomoathome/app/node_modules/nconf/lib/nconf/provider.js:449:7)
at loadConf (/usr/share/mydomoathome/app/mdah.js:105:15)
at Object.<anonymous> (/usr/share/mydomoathome/app/mdah.js:2702:1)
warn: basic configuration not found in /etc/mydomoathome/config.json, defaulting
warn: domoticz access configuration not found in /etc/mydomoathome/config.json, defaulting
info: Domoticz server: http://127.0.0.1:8080/json.htm
info: Node version: 4.2.2
info: MDAH version: MyDomoAtHome 0.2.29
info: OS version: Linux linux 4.9.41-v7+
info: Hostname: raspberrypi 192.168.1.17 in /var/www /
there is someting that i don't understand
thanks per advance for ur help
Re: [MyDomoAtHome] Support thread
Posted: Thursday 26 October 2017 15:16
by epierre
"auth": { "username": "login", "password": "passord" },
no coma before }
Re: [MyDomoAtHome] Support thread
Posted: Thursday 26 October 2017 15:24
by bmath
that works! thanks =)
Re: [MyDomoAtHome] Support thread
Posted: Saturday 28 October 2017 17:19
by gdusordet
still experiencing the same issue, I have added the file
vi /etc/mydomoathome/config.json
{
"app_name": "MyDomoAtHome",
"auth": null,
"tempmode": "C",
"domoticz": {
"ssl": false,
"host": "127.0.0.1",
"port": "8084",
"path": "/",
"auth": null
},
"port": 3002,
"passcode": ""
}
grant the right
chmod a+rx /etc/mydomoathome
chmod a+rx /etc/mydomoathome/config.json
unfortunatly each time I start ImperiHome, mydomoathome is crashing
info: Domoticz server:
http://127.0.0.1:8084/json.htm
info: Node version: 4.8.4
info: MDAH version: MyDomoAtHome 0.2.29
info: OS version: Linux linux 3.10.102
info: Hostname: BG-Station 169.254.171.110 in /root /root
info: Refreshing version cache: v0.2.30
291 Open 1 100
809 Closed 0 0
712 Closed 0 0
528 Open 1 100
564 Closed 0 0
713 Closed 0 0
/volume1/@appstore/MyDomoAtHome/app/mdah.js:421
params.push({"key": "Value", "value": ret[lvl].toString()});
^
TypeError: Cannot read property 'toString' of undefined
at DevMultiSwitch (/volume1/@appstore/MyDomoAtHome/app/mdah.js:421:51)
at Request._callback (/volume1/@appstore/MyDomoAtHome/app/mdah.js:2437:45)
at Request.self.callback (/volume1/@appstore/MyDomoAtHome/app/node_modules/request/request.js:200:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.<anonymous> (/volume1/@appstore/MyDomoAtHome/app/node_modules/request/request.js:1067:10)
at emitOne (events.js:82:20)
at Request.emit (events.js:169:7)
at IncomingMessage.<anonymous> (/volume1/@appstore/MyDomoAtHome/app/node_modules/request/request.js:988:12)
at emitNone (events.js:72:20)
Re: [MyDomoAtHome] Support thread
Posted: Saturday 28 October 2017 17:35
by epierre
@gdusordet your issue is different, can you send me the domoticz definition of your multiswitch ?
http://169.254.171.110:8080/json.htm?ty ... order=Name
Re: [MyDomoAtHome] Support thread
Posted: Sunday 29 October 2017 21:57
by gdusordet
Hi epierre, how do I get the definition of the multiswitch?
Thanks for your help
Re: [MyDomoAtHome] Support thread
Posted: Monday 30 October 2017 7:25
by epierre
From the link above as it seems it was your ip
Re: [MyDomoAtHome] Support thread
Posted: Tuesday 31 October 2017 9:12
by Stockfisch
Hi,
on my system, ImperiHome stops displaying the instant energy reporting a few hours after restarting domoticz for most of my devices.
This is happening for all my wall plugs (FGWPF-102) plugs and my dimmer (EFGD-212). For my in wall switches (FGS-213) the instant energy is displayed without any problems.
Is anyone having the the same issue?
Thanks Dirk