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
Comments
Same with me. Did you make any progress on that? |
Currently there is no hmip support. |
Any chance that will change? 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) ;) |
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. |
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! :-) |
i am currently working on that. |
Ok here comes the HMIP-PSM (atm only the Switch Channel) |
Great start, thx so much! Looking forward to using my window/door sensors
|
i do not own an swdo to test, but the latest github may work ... |
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 |
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 |
Thanks for implementing support for HMIP. How to replace the files at /usr/local/lib/node_modules/homebridge-homematic? Thanks, Jan |
telnet into the rpi
|
Thanks for investing your time for us. Let me know if you need support on
|
And please make sure that you have enabled hmip in the config.json "enable_hmip":"true" the following startup entries should appear
|
Ok i've added some logging to the current version. Please update from github and start the bridge in debug mode:
After homebridge initializing is completed , perform a state change of one of your swdo's and watch out for some logging like this
i will need theese logging infos to dig into the issue .... |
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! |
;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 ... |
I only have several devices of "Schaltsteckdose, Pluggable Switch", Homematic IP, eQ-3, 141836A0A HMIP-PS |
Still struggeling, some info to check. updated via gitgub json for homematic
homebridge start [10/7/2016, 7:46:19 PM] [HomeMaticCCU] Initializing HomeMatic platform... [10/7/2016, 7:31:48 PM] [HomeMaticCCU] Initializing platform accessory 'HMIP-SWDO 0000DxxxxEC: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());} (xxx added to mask ID). Does that help? |
hmm some lines are missing ...
|
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? |
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! |
your logfile says that the hmip rpc service is not running. i am not sure why ... |
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 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! |
Ah ok ... it seems that HMIP Events are not allways multicalls .. So i have to implement the rpc event method ... |
@daNick73 would you please replace the HomeMaticRPC.js with the actual github version and test that ... |
changing state now crashes homebridge entirely :) TypeError: Cannot read property 'setValue' of undefined |
fck... sorry ... will check that asap'st 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 |
For me, HMIP-SWDOs are working as "windows" - thx for your update! "doors" are still appearing as "unsupported" in the ios app. |
@Samfox2 the SWDOs are also updated, I.e you start homebridge and
|
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 😔 |
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. |
Will do tomorrow, Sunday. Thomas, your support is fabulous! Thx so much!
|
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! |
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 |
Please make sure that you have added the channel with number 1 to your homekit subsection. |
{ |
ah thats it, please read https://github.com/thkl/homebridge-homematic#configuration |
Hmm, so what's the problem? |
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 |
I changed that but it's still not recognized 😞 |
So, using only "subsection", deleting all "windows" section content won't
|
No. Last thing to try would be to delete the persist folder and set the whole thing up again... |
first check, if the accessory init is correct :
|
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. |
Aaaah ok ... will close that issue now |
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
The text was updated successfully, but these errors were encountered: