homebridge-edomoticz Plugin

[chrispazz]

[chrispazz]

The sensor at right border is the sensor movement ms13 x10

[chrispazz]

The first on the second line instead is a x10 security movement sensor

[Marci]

Ah. No idea then as don't have access to either. I've recreated your device here using your JSON output and it works fine in iOS9.3.4 & Eve & Home.

Try it on a non-beta OS. Until iOs10 is properly released I can't offer support to anyone running it.

[chrispazz]

Ok. Thank you anyway for your time

[Marci]

(S'cos service types and characteristics are defined by hap-nodejs, part of homebridge, not part of the plugin. KhaosT has already said over on the hap-nodejs repo that he can't update hap-nodejs for iOS10 services & chars til the fall - some have changed, others have been added. Until he does that, anyone on iOS10 may have issues with some service types within homebridge.)

[deejc]

ok so this is "Learning on the job"

i have realised i actually need an mqtt broker!, so i installed one on my pi, thats now working, domo is subscribed, I'm not sure what i should be subscribed too in the mqtt app to see the messages but the plugin still does not show me any messages in the home bridge log which is what i am expecting see.
when i switch a light on in domo i see the mqtt messages increase on the broker status page of the app i am using MQTT.fx

[Marci]

Domoticz publishes messages to the broker on domoticz/out, so you connect MQTT apps to the broker's IP on port 1883 and then subscribe specifically to domoticz/out, and you should see messages.

Presume you've added relevant bits to config.json to enable MQTT in the plugin?

[deejc]

Ok , I got a 5am start so I'll leave it for tonight, once again thanks for all your help


Sent from my iPhone using Tapatalk

[simon_rb]

Speaking of new services, doorbell and live camera views sound great!

[Marci]

Indeed... but I'm not entirely sure domoticz exposes cameras in a way that can be translated via the plugin. They'll be THE trickiest element of the lot. Might have to depend on external homebridge plugins to talk direct to the IP Cam.

[simon_rb]

Indeed... but I'm not entirely sure domoticz exposes cameras in a way that can be translated via the plugin. They'll be THE trickiest element of the lot. Might have to depend on external homebridge plugins to talk direct to the IP Cam.

I think your right, only other option is for gizmocuz to update domoticz to export the cams a different way. Early days yet anyways

[Marci]

KhaosT says it'll need an RTP/SRTP node module.

[TheRamon]

Ok. Thank you anyway for your time

Hi Chris,

I have just added your sensor to my system, and shows up properly as a "motion sensor" in HomeKit (iOS 10, too). No switch or anything.. I think it really has to do with your local caching. Somehow HomeKit still thinks this is a switch, like it was before.

[TheRamon]

ok so this is "Learning on the job"

i have realised i actually need an mqtt broker!, so i installed one on my pi, thats now working, domo is subscribed, I'm not sure what i should be subscribed too in the mqtt app to see the messages but the plugin still does not show me any messages in the home bridge log which is what i am expecting see.
when i switch a light on in domo i see the mqtt messages increase on the broker status page of the app i am using MQTT.fx

Yep, you need a broker. Normally Mosquitto (the broker) is shipped with Domoticz by default. You just enable it by going to "Setup > Hardware > MQTT Client Gateway with LAN interface". Fill in remote address "localhost" and port 1883 and add the "hardware".

Domoticz now publishes all events on MQTT.
You then go to the config.json of the plugin (~/.homebridge/config.json) and add the MQTT config, resulting in:

Code: Select all

"platform": "eDomoticz",
"name": "eDomoticz",
"server": "127.0.0.1",
"port": "8080",
"ssl": 0,
"roomid": 0,
"mqttenable": 1,
"mqttserver": "localhost",
"mqttport": "1883",
"mqttauth": 0,
"mqttuser": "",
"mqttpass": ""

You should then restart homebridge on your Pi and see the messages coming in!

[chrispazz]

Ok. Thank you anyway for your time

Hi Chris,

I have just added your sensor to my system, and shows up properly as a "motion sensor" in HomeKit (iOS 10, too). No switch or anything.. I think it really has to do with your local caching. Somehow HomeKit still thinks this is a switch, like it was before.

This is more and more strange ahaha
Thank you, this evening I will play again with it....

Can you post the json output for your sensor?

[Marci]

You're not getting how things work - we spool up a fake web server that imitates Domoticz by serving YOUR JSON output, which replicates your sensor exactly, therefore, the JSON output we're using is exactly as you shared earlier in the thread - a direct copy & paste.

[simon_rb]

Will this MQTT method speed up the updating/refreshing of domoticz devices within HomeKit?


Sent from my iPhone using Tapatalk

[Marci]

Yes, should be instantaneous when on same LAN. When over the net, dependant on lots of things out of our hands.

[simon_rb]

Yes, should be instantaneous when on same LAN. When over the net, dependant on lots of things out of our hands.

Excellent!! Looking forward to this! eDomoticz works very well, just HomeKit is slow to update and grab statues when you open the app which will now be a thing on the past. Might go and setup MQTT now so it's ready!! Thanks everyone for you hard work.

These projects seem to be going from strength to strength!


Sent from my iPhone using Tapatalk