Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HM IP Sensors (HMIP-SWDO) - identified, but no reading #28

Closed
daNick73 opened this issue Aug 21, 2016 · 47 comments
Closed

HM IP Sensors (HMIP-SWDO) - identified, but no reading #28

daNick73 opened this issue Aug 21, 2016 · 47 comments

Comments

@daNick73
Copy link

Hi

I use a couple of HMIP-SWDO.

They work fine in CCU2, reads go.

Homebridge identifies these, but status is not read. Even if qualified as "door" in config, they are shown as a different type of sensor, but no readings.

Any recommendations? THX!

Best regards

Nico

@Samfox2
Copy link

Samfox2 commented Aug 28, 2016

Same with me. Did you make any progress on that?

@thkl
Copy link
Owner

thkl commented Aug 30, 2016

Currently there is no hmip support.

@daNick73
Copy link
Author

daNick73 commented Aug 31, 2016

Any chance that will change?
Maybe if those interested in the feature donate you a HMIP SWDO for free to test ? :)

Or just too difficult/ time consuming, so wont happen?

(THX btw for the plug in.. the rest works great, thats why it got me greedy) ;)

@thkl
Copy link
Owner

thkl commented Aug 31, 2016

It's not about the Hardware :) it's about the time it takes to implement all the stuff. The HMiP is an new interface Layer.

@fabz5
Copy link

fabz5 commented Oct 3, 2016

Are you actually planning to implement HMIP support? Or is this out of scope at the moment? The plugin is really great by the way, THX! :-)

@thkl
Copy link
Owner

thkl commented Oct 6, 2016

i am currently working on that.

@thkl
Copy link
Owner

thkl commented Oct 6, 2016

Ok here comes the HMIP-PSM (atm only the Switch Channel)

@daNick73
Copy link
Author

daNick73 commented Oct 6, 2016

Great start, thx so much! Looking forward to using my window/door sensors
(HMIP-SWDO) in homebridge/ HomeKit!
Thomas Kluge notifications@github.com schrieb am Do. 6. Okt. 2016 um
21:08:

Ok here comes the HMIP-PSM (atm only the Switch Channel)


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#28 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AULYhvZmUIixmZJEadOpMzCIMKZn94t-ks5qxUdIgaJpZM4JpUgw
.

@thkl
Copy link
Owner

thkl commented Oct 6, 2016

i do not own an swdo to test, but the latest github may work ...

@daNick73
Copy link
Author

daNick73 commented Oct 6, 2016

trying to test now (see it is updated), but still says

[10/6/2016, 8:21:14 PM] [HomeMaticCCU] NPM 0.0.37 vs Local 0.0.37

after

sudo npm update -g homebridge-homematic

RPI has internet access.

Any recommendation what I may miss here?

Best Nico

@thkl
Copy link
Owner

thkl commented Oct 6, 2016

Nope, you have to update from github. Npm is still at 0.0.37.

Replace the files at /usr/local/lib/node_modules/homebridge-homematic

@janforth
Copy link

janforth commented Oct 7, 2016

Thanks for implementing support for HMIP. How to replace the files at /usr/local/lib/node_modules/homebridge-homematic? Thanks, Jan

@daNick73
Copy link
Author

daNick73 commented Oct 7, 2016

  1. for me, HMIP-SWDOs are unchanged in 0.39: devices show up, but status is
    always "closed" (sensors are read correctly in CCU2).
  2. To copy the files, the following worked for me:

telnet into the rpi
sudo chmod -R 0777 /usr/local/lib/node_modules/homebridge-homematic
(This allows you to overwrite files in the step below)
Use an ftp client to copy all files from the homebridge-homematic
repository to the above directory on the rpi
janforth notifications@github.com schrieb am Fr. 7. Okt. 2016 um 06:05:

Thanks for implementing support for HMIP. How to replace the files at
/usr/local/lib/node_modules/homebridge-homematic? Thanks, Jan


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#28 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AULYhsma1ne1D_HWg79Fve8hhw46iRCQks5qxcUggaJpZM4JpUgw
.

@daNick73
Copy link
Author

daNick73 commented Oct 7, 2016

Thanks for investing your time for us. Let me know if you need support on
beta testing/ want me to check anything!
Thomas Kluge notifications@github.com schrieb am Fr. 7. Okt. 2016 um
07:00:

Ok. will check this. HMiP doesn't have an event system so HomeKit has
always pull states.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#28 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AULYhjDo1sCf_2Wgdosy-crs-o3_7uV_ks5qxdHxgaJpZM4JpUgw
.

@thkl
Copy link
Owner

thkl commented Oct 7, 2016

@daNick73

And please make sure that you have enabled hmip in the config.json

"enable_hmip":"true"

the following startup entries should appear

[HomeMatic CCU] XML-RPC server for interface HmIP-RF.is listening on port 9093
[HomeMatic CCU] Creating Local HTTP Client for CCU RPC Events
[HomeMatic CCU] CCU RPC Init Call on port 2010 for interface HmIP-RF.

@thkl
Copy link
Owner

thkl commented Oct 7, 2016

@daNick73

Ok i've added some logging to the current version. Please update from github and start the bridge in debug mode:

DEBUG=* homebridge -D

After homebridge initializing is completed , perform a state change of one of your swdo's and watch out for some logging like this

HomeMaticRPC RPC event for HmIP-RF.blabla:1 STATE with value true +174ms

i will need theese logging infos to dig into the issue ....

@janforth
Copy link

janforth commented Oct 7, 2016

HMIP support works perfectly well here. All devices are found and status (on/off for the switchable I have) can be changed via Apple HomeKit! Thank you so much! Great work and exactly what I needed!

@thkl
Copy link
Owner

thkl commented Oct 7, 2016

;o) i love to hear that. May you me please tell which devices are working well for you ... cause i do not own any of the hmip's this is all done from paperwork ...

@janforth
Copy link

janforth commented Oct 7, 2016

I only have several devices of "Schaltsteckdose, Pluggable Switch", Homematic IP, eQ-3, 141836A0A HMIP-PS

@daNick73
Copy link
Author

daNick73 commented Oct 7, 2016

Still struggeling, some info to check.

updated via gitgub

json for homematic

  "platform": "HomeMatic",
                                    "name": "HomeMaticCCU",
                                    "enable_hmip": "true",
                                    "ccu_ip": "192.168.178.5",
                                    "filter_device": [],
                                    "filter_channel": [],
                                    "outlets": [],
                                    "doors": [],
                                    "programs": [],
                                    "subsection": "siri"

homebridge start

[10/7/2016, 7:46:19 PM] [HomeMaticCCU] Initializing HomeMatic platform...
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] Homematic Plugin Version 0.0.37
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] Plugin by thkl https://github.com/thkl
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] Homematic is a registered trademark of the EQ-3 AG
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] Please report any issues to https://github.com/thkl/homebridge-homematic/issues
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] init RPC
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] Local IP: 192.168.178.3
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] XML-RPC server for interface BidCos-RF.is listening on port 9090
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] Creating Local HTTP Client for CCU RPC Events
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] CCU RPC Init Call on port 2001 for interface BidCos-RF.
[10/7/2016, 7:46:19 PM] [HomeMaticCCU] Fetching Homematic devices...

[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HMIP-SWDO 0000DxxxxEC:1'...
[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HMIP-SWDO 0000D3CxxxxxEB4:1'...
[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HMIP-SWDO 0000D3CxxxxxxF1E:1'...
[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HM-ES-PMSw1-Pl KEQ0xxxxx17:1'...
[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HMIP-SWDO 0000D3Cxxxx6247:1'...
[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HMIP-SWDO 0000D3C9xxxxx09:1'...
[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HM-WDS40-TH-I-2 LEQ03xxxx986:1'...
[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HM-WDS40-TH-I-2 LEQ108xxx2:1'...
[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HMIP-SWDO 0000D3C99xxxx24A:1'...
[10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HMIP-SWDO 0000Dxxxxxe4:1'...

DEBUG=* homebridge -D results in a lot of output, I identified only these lines with string "hmIP-rf"

[10/7/2016, 7:38:05 PM] [HomeMaticCCU] Error while executing rega script var d = dom.GetObject("HmIP-RF.0000D3C9xxxxEC:1");if (d){Write(d.State());}
[10/7/2016, 7:38:05 PM] [HomeMaticCCU] Error while executing rega script var d = dom.GetObject("HmIP-RF.0000D3C9xxxxxB4:1");if (d){Write(d.State());}
[10/7/2016, 7:38:05 PM] [HomeMaticCCU] Error while executing rega script var d = dom.GetObject("HmIP-RF.0000D3C9xxxxx1E:1");if (d){Write(d.State());}
[10/7/2016, 7:38:05 PM] [HomeMaticCCU] Error while executing rega script var d = dom.GetObject("HmIP-RF.0000D3C9xxxxx47:1");if (d){Write(d.State());}
[10/7/2016, 7:38:05 PM] [HomeMaticCCU] Error while executing rega script var d = dom.GetObject("HmIP-RF.0000D3C9xxxxx309:1");if (d){Write(d.State());}
[10/7/2016, 7:38:05 PM] [HomeMaticCCU] Error while executing rega script var d = dom.GetObject("HmIP-RF.0000D3C9xxxxx4A:1");if (d){Write(d.State());}

(xxx added to mask ID).

Does that help?

@thkl
Copy link
Owner

thkl commented Oct 7, 2016

hmm some lines are missing ...

[Fri Oct 07 2016 22:03:42 GMT+0200 (CEST)] [HomeMatic CCU] XML-RPC server for interface HmIP-RF.is listening on port 9093
[Fri Oct 07 2016 22:03:42 GMT+0200 (CEST)] [HomeMatic CCU] Creating Local HTTP Client for CCU RPC Events
[Fri Oct 07 2016 22:03:42 GMT+0200 (CEST)] [HomeMatic CCU] CCU RPC Init Call on port 2010 for interface HmIP-RF.
[Fri Oct 07 2016 22:03:42 GMT+0200 (CEST)] [HomeMatic CCU] Fetching Homematic devices...
[Fri Oct 07 2016 22:03:42 GMT+0200 (CEST)] Loading 0 accessories...
[Fri Oct 07 2016 22:03:44 GMT+0200 (CEST)] [HomeMatic CCU] Initializing platform accessory 'HMIP-PSM BLABLABLA:3'...

@daNick73
Copy link
Author

daNick73 commented Oct 7, 2016

I have iobroker.io running on the same RPI (installed, but not really using it). nothing else on the RPI ... could that be the cause?

@daNick73
Copy link
Author

daNick73 commented Oct 7, 2016

addition: if there is no easy fix: thx for investing time on MY request here.

Maybe you should wait whether others respond here that they would appreciate this... potentially, I am the only one using HMIP-SWDO with homebridge... and maybe I should have simply bought "normal" Homematic sensors, not HmIP :)

thx again!

@thkl
Copy link
Owner

thkl commented Oct 7, 2016

your logfile says that the hmip rpc service is not running. i am not sure why ...

@daNick73
Copy link
Author

daNick73 commented Oct 8, 2016

update ... almost there (I guess) :)

sudo npm -g update homebridge-homematic now got me to 0.40

which added the HmIP layer to the logfile :)

[10/8/2016, 11:52:49 AM] [HomeMaticCCU] Local IP: 192.168.178.3
[10/8/2016, 11:52:49 AM] [HomeMaticCCU] XML-RPC server for interface HmIP-RF.is listening on port 9092
[10/8/2016, 11:52:49 AM] [HomeMaticCCU] Creating Local HTTP Client for CCU RPC Events
[10/8/2016, 11:52:49 AM] [HomeMaticCCU] CCU RPC Init Call on port 2010 for interface HmIP-RF.
[10/8/2016, 11:52:50 AM] [HomeMaticCCU] Fetching Homematic devices...

Now, the initial reading of my HMIP-SWDO is correct, meaning: when I start homebridge and the window is open .... it shows open! :) :)

just that state does not change, so when the window closes, that is not detected.

In the debug, I noted lines like these:

_HomeMaticRPC Method event does not exist. - ["homebridge_HmIP-RF.","0000D3C99XXXXB4:1","STATE",1] +658ms

(appears when I open the window)

HomeMaticRPC Method event does not exist. - ["homebridge_HmIP-RF.","0000D3C99xxxB4:1","STATE",0] +134ms_

(appears when I close the window)

Also:

_HomeMaticRPC Method event does not exist. - ["homebridge_HmIP-RF.","0000D3C990XXXX4:1","PRESS_SHORT",true] +2s

HomeMaticRPC Method event does not exist. - ["homebridge_HmIP-RF.","0000D3C99XXXXB4:0","UNREACH",false] +127ms_

Anything needed from me to investigate that?

THX!

@thkl
Copy link
Owner

thkl commented Oct 8, 2016

Ah ok ... it seems that HMIP Events are not allways multicalls .. So i have to implement the rpc event method ...

@thkl
Copy link
Owner

thkl commented Oct 8, 2016

@daNick73 would you please replace the HomeMaticRPC.js with the actual github version and test that ...
thank you

@daNick73
Copy link
Author

daNick73 commented Oct 8, 2016

changing state now crashes homebridge entirely :)

TypeError: Cannot read property 'setValue' of undefined
at HomeMaticHomeKitContactService.HomeKitGenericService.event (/usr/local/lib/node_modules/homebridge-homematic/ChannelServices/HomeKitGenericService.js:220:13)
at /usr/local/lib/node_modules/homebridge-homematic/HomeMaticRPC.js:94:20
at Array.map (native)
at Server. (/usr/local/lib/node_modules/homebridge-homematic/HomeMaticRPC.js:92:38)
at emitThree (events.js:97:13)
at Server.emit (events.js:175:7)
at /usr/local/lib/node_modules/homebridge-homematic/node_modules/homematic-xmlrpc/lib/server.js:42:14
at callback (/usr/local/lib/node_modules/homebridge-homematic/node_modules/homematic-xmlrpc/lib/deserializer.js:65:7)
at Deserializer.onDone (/usr/local/lib/node_modules/homebridge-homematic/node_modules/homematic-xmlrpc/lib/deserializer.js:92:12)
at emitNone (events.js:67:13)
at SAXStream.emit (events.js:166:7)
at Object.SAXStream._parser.onend (/usr/local/lib/node_modules/homebridge-homematic/node_modules/homematic-xmlrpc/node_modules/sax/lib/sax.js:171:8)
at emit (/usr/local/lib/node_modules/homebridge-homematic/node_modules/homematic-xmlrpc/node_modules/sax/lib/sax.js:325:33)
at end (/usr/local/lib/node_modules/homebridge-homematic/node_modules/homematic-xmlrpc/node_modules/sax/lib/sax.js:363:3)
at Object.SAXParser.end (/usr/local/lib/node_modules/homebridge-homematic/node_modules/homematic-xmlrpc/node_modules/sax/lib/sax.js:137:24)
at SAXStream.end (/usr/local/lib/node_modules/homebridge-homematic/node_modules/homematic-xmlrpc/node_modules/sax/lib

@thkl
Copy link
Owner

thkl commented Oct 8, 2016

fck... sorry ... will check that asap'st
Edit : there should be a log entry just one line before the crash "RPC single event for ....." can you post it here ...

Edit2: i added a log entry .. would you please xchange the HomeMaticRPC.js once more .. it will crash but the rpc event will be logged as "Ok here is the Event ...."

Edit3: ok please also replace ChannelServices/HomeKitGenericService.js ... it should fix the crash

@Samfox2
Copy link

Samfox2 commented Oct 8, 2016

For me, HMIP-SWDOs are working as "windows" - thx for your update! "doors" are still appearing as "unsupported" in the ios app.

@daNick73
Copy link
Author

daNick73 commented Oct 8, 2016

@Samfox2 the SWDOs are also updated, I.e you start homebridge and
open/close change the reading?
Samfox2 notifications@github.com schrieb am Sa. 8. Okt. 2016 um 18:07:

For me, HMIP-SWDOs are working as "windows" - thx for your update! "doors"
are still appearing as "unsupported" in the ios app.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#28 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AULYhqRBO6MuApOVEtOCPqT5S417zoelks5qx7_ZgaJpZM4JpUgw
.

@Samfox2
Copy link

Samfox2 commented Oct 8, 2016

Ah, sorry. Thought it would be working as state is now open instead of closed like before. But still, no changes are recognized by the app 😔

@thkl
Copy link
Owner

thkl commented Oct 8, 2016

Can anybody with SwDo please start the Bridge in debug mode (DEBUG=* homebridge -D) , and post the rpc event log entries while opening and closing windows. So I am able to fix this.

Thank you.

@daNick73
Copy link
Author

daNick73 commented Oct 8, 2016

Will do tomorrow, Sunday. Thomas, your support is fabulous! Thx so much!
Thomas Kluge notifications@github.com schrieb am Sa. 8. Okt. 2016 um
18:38:

Can anybody with SwDo please start the Bridge in debug mode (DEBUG=*
homebridge -D) , and post the rpc event log entries while opening and
closing windows. So I am able to fix this.

Thank you.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#28 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AULYhvVOcVPGh8YiyOg0_DnPPC4l9Xvrks5qx8bmgaJpZM4JpUgw
.

@daNick73
Copy link
Author

daNick73 commented Oct 8, 2016

I updated to 0.0.41

I am pleased to confirm that homebridge now reports my SWDOs correctly (instant feedback on close and open)!

This case is SOLVED for now as far as I am concerned

Thomas: if you provide me a private email, I would be pleased to donate EUR 5 via amazon or paypal. Maybe, if others join, you will get your own SWDO :)

THX again for the worldclass support!

@Samfox2
Copy link

Samfox2 commented Oct 8, 2016

Nope, it's just not recognized and there is no log message in homebridge debug mode while state changes., the only message I get is [HomeMatic CCU]�There is no service for HMIP-SWDO:MAINTENANCE

@thkl
Copy link
Owner

thkl commented Oct 9, 2016

Please make sure that you have added the channel with number 1 to your homekit subsection.

@Samfox2
Copy link

Samfox2 commented Oct 9, 2016

 This is what it looks like

{
"platform": "HomeMatic",
"name": "HomeMatic CCU",
"ccu_ip": "192.168.2.xxx",
"local_port": "7xx77",
"ios10":"true",
"enable_hmip": "true",
"filter_device":[],
"filter_channel":[],
"outlets":[],
"doors":[],
"windows":["BidCos-RF.LEQxxxxx:1","BidCos-RF.MEQxxxxx:1","BidCos-RF.MEQxxxxx:1","BidCos-RF.MEQxxxxx:1","HmIP-RF.0000D3Xxxxxxx:1"]
}

@thkl
Copy link
Owner

thkl commented Oct 9, 2016

ah thats it, please read https://github.com/thkl/homebridge-homematic#configuration
I just updated the readme, to be more specific

@Samfox2
Copy link

Samfox2 commented Oct 9, 2016

Hmm, so what's the problem?

@thkl
Copy link
Owner

thkl commented Oct 9, 2016

there is no subsection key, so currently all channels are will mapped into homekit. depending on the number of devices, they go over 100, which is the limit of homekit devices behind a bridge.

In other cases, i do no have any glue whats going wrong with your installation

@Samfox2
Copy link

Samfox2 commented Oct 9, 2016

I changed that but it's still not recognized 😞

@daNick73
Copy link
Author

daNick73 commented Oct 9, 2016

So, using only "subsection", deleting all "windows" section content won't
do?
Samfox2 notifications@github.com schrieb am So. 9. Okt. 2016 um 11:33:

I changed that but it's still not recognized 😞


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#28 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AULYhmgJT9RLriy93CjXTGQbnBj6HNx4ks5qyLTLgaJpZM4JpUgw
.

@Samfox2
Copy link

Samfox2 commented Oct 9, 2016

No. Last thing to try would be to delete the persist folder and set the whole thing up again...

@thkl
Copy link
Owner

thkl commented Oct 9, 2016

first check, if the accessory init is correct :

[HomeMatic CCU] Initializing platform accessory 'mySWDOChannel_1_Name'...

@Samfox2
Copy link

Samfox2 commented Oct 9, 2016

Got it! I changed the port and now it is working! I saw in the protocol that for hmip a "2" is added to the port and this one was already assigned at my host. Now it is working 😄 Thx 2 all.

@thkl
Copy link
Owner

thkl commented Oct 9, 2016

Aaaah ok ... will close that issue now

@thkl thkl closed this as completed Oct 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants