[Domoticz] missing accessories after upgrades #270
Comments
|
Need to get Domoticz api output for each IDX and post here… see https://www.domoticz.com/wiki/Domoticz_API/JSON_URL%27s#Retrieve_status_of_specific_device |
|
(Also, could be because you’re running as a child bridge. Never managed to get child bridge setup working properly & showing all devices here, so can’t really vouch for it’s use 🤷🏼… and your MQTT config looks to be invalid so expect non-instant updates etc) |
|
Needs the specific output for the individual IDXs in question, not the device list. |
|
Sure I didn't see your comment, I was just updating my original post with more details for help. output for idx 836 as an example (a switch for power plug): { and output for idx 849 (temperature sensor) { |
About the child bridge comment:
And about MQTT config:
Thanks for your help! |
|
That’s incomplete… note the level of output at the wiki link = includes result:[] containing hardware type, subtype, switch type, current values etc.
Check your Domoticz security settings due to changes in v2023.x.
Does Domoticz user you’re connecting as from homebridge-edomoticz have access to those devices etc within Domoticz > Users?
All probably down to the stricter security in new Domoticz.
|
|
Regarding the security settings:
Regarding the output missing HW info etc:
It is the same they mentioned: Strange let me look to find another command with more details |
|
I think you now HAVE to auth as user. Try adding your local ip range or specific local ip addresses of both the Pi and your current device that you’re hitting API from to exemption list (192.168.0.x probably) as well as the loop back address, then see if you get result: [] back from the API. If so, restart homebridge, see if devices appear. OR connect with auth credentials. |
|
Tried that already :( Initially the exemption list was like this: 127.0.0.1 (FYI my local NW is 192.168.1.x vs 192.168.0.x) |
|
I have devices coming from different HW declared in Domoticz (RFXCom, Xiaomi gateway etc). All devices seem to appear fine in Homebridge except for the ones coming from 1 type of HW which is DeconZ (Zigbee Conbee II key) |
|
Yes that's what I did (with a wildcard though after the last "."). The wild card is not printing when I write here |
|
If no result element, it’s either auth issue, or the Deconz device type in Domoticz isn’t outputting correctly. Do you get result element for different devices from API when you use same method? |
|
Ok we are on something here. I just tested the API output for a working device and I have much more details { |
|
Right - says to me it’s either the Hardware plugin for that device over in Domoticz… OR, over on the default user in Domoticz, those devices aren’t included yet when you hit “set devices” for that user at /#/Users |
|
I don't have a default user... (since initial installation I removed the "admin" user that comes by default with domoticz for security reasons). Let me try to force adding all devices for all users (because not sure which one would be considered as default since I am the one who created all of them) and see whether there is a change in behaviour |
|
Well, let’s rule it out altogether. Make an admin user with all devices for homebridge-eDomoticz to use, and sling user:pass@ in front of IP over in homebridge-edomoticz config… |
|
Thank you so much!!! Probably a change in behaviour in the new Domoticz version as you mentioned. |
Hello,
After upgrading Domoticz and homebridge-edomoticz, a few accessories don't show up anymore in Homebridge (I was using them for years).
Current versions:
Tried the following but didn't get any positive results:
The common point between all missing devices is that they are all coming from the same hardware in Domoticz which is a ConbeeII Zigbee device (added in Domoticz through DeconZ plugin). The missing devices are a mix of temperature sensors and power plug switches.
Log
Below is the log. It doesn't show any problem with synchronisation:
Output of /json.htm?type=command¶m=devices_list from domoticz
Any help will be much appreciated as I ran out of ideas :(
(I am suspecting a code change in Domoticz that is not compatible anymore with homebridge-edomoticz)
Thanks
The text was updated successfully, but these errors were encountered: