Closed btcdtc closed 2 weeks ago
@btcdtc Thank you for your report.
Based on my diagnosis from the screenshot, ECHONETLite2MQTT is not able to collect OperationalStatus from the device. Does restarting ECHONETLite2MQTT not improve this problem?
So far I don't know what the cause is. If possible, could you please provide the detailed log at the bottom of the LOG page?
Could you help to provide the REST API url so I can check what api it provides? Thanks.
I'm not sure what you need for this. The device REST API provided by ECHONETLite2MQTT is as follows.
/elapi/v1/devices/(device id) /elapi/v1/devices/(Device Id)/properties
However, the REST API has the same information as the WEB page.
@banban525
Thanks for you response,
I deployed many echonetlite tools and none of them able to collect or set OperationalStatus. the current ECHONETLite2MQTT and picoGW are deployed on raspberry pi with only Ethernet connect in the same 192.168.20.0/24 subnet.
seems none of the tools can successfully get a response if they request OperationalStatus, So my guess is maybe since it is already linked to my aiseg console, it will reject all other request. I will try to unlink it and try again tomorrow.
I found the rootcause. I delete it from aiseg and found aiseg cannot no longer pair with it succfully. and then I found when paried with a lock, HF-JA2 will enable 1:1 communication mode by default.
https://av.jpn.support.panasonic.com/support/share2/eww/jp/hnavi/manual_JA2_AiSEG.pdf
and I can't found how to turn it off. https://av.jpn.support.panasonic.com/support/share2/eww/jp/hnavi/hf-ja2_basic.pdf
@btcdtc
Thanks for reporting.
The following URL reports similar behavior, but for a different device:
https://x.com/Ranas_Genoa/status/1815672718299144580?t=F6mOmYxAU9TOTwrzVxVPYg&s=19
The problematic device may only be able to connect to either the aiseg2 or the echonetlite
I fixed the issue, the reason is the HF-JA2 adapter has been set to 1:1 mode. HF-JA2 has a simple management webui http://ip:8080 but there isn't much can be done, the pair mode is not there. so I reset the adapter and I confirmed it can be controlled. late when I tried hook it with Aiseg and I realized at the end of the setting it asks if this device is Aiseg only or Aiseg and home navigator. I assuemd this means 1:1 mode or 1:many mode and choose the later which is indeed 1:many mode. now I can control the lock through different management tool.
and thanks for your work on this, it is a life saver.
@btcdtc
I'm glad your problem was solved.
It seems the problem was with the mode and not the specifications. I don't have HF-JA2, so I didn't know about it.
I will mark this issue as closed
I have a lock hooked with HF-JA2 adapter, it works in aiseg controller but I found I am unable to control this lock when I tried this plugin.
I found there is OperationStatus under NodeProfile but no OperationStatus node under switch, the spec looks correct but I tried lock and unlock yet the every nodes stays the same.
Could you help to provide the REST API url so I can check what api it provides? Thanks.
update: I used picoGW and this is what I got. and all data stays the same regardless the lock status.