Domoticz

Mooseknuckle wrote:Hi,

Has anybody succesfully added the following wireless switch to the gateway?
http://www.gearbest.com/access-control/pp_626695.html
I tried to add it as a round wireless switch but It doesn't work. Maybe I just have to wait for a gateway update but I was curious if others did succeed in adding the switch.

Mooseknuckle wrote:Hi,

It is what quack3d said, adding it to the gateway does not work. The strange thing is that when I add it, the mihome app counts it as a device but I cannot see it under the devices. Also in Domoticz I see the new switch but nothing changes when I press the button. I can add other devices to the gateway so I think I have to wait for a firmware update from Xiaomi.

levynger wrote:

Mooseknuckle wrote:Hi,

It is what quack3d said, adding it to the gateway does not work. The strange thing is that when I add it, the mihome app counts it as a device but I cannot see it under the devices. Also in Domoticz I see the new switch but nothing changes when I press the button. I can add other devices to the gateway so I think I have to wait for a firmware update from Xiaomi.

So you are able to add it to mi home apl?
In this case, you won't see it in domoticz devices if it uses new ID.

After paring it in mi home app, click on it, and in domoticz logs you should see the unknown line with the new device id.
Paste it here, and corbin would be able to do his magics..

Sent from my SM-N920G using Tapatalk

corbin wrote:Was the error when smoke was detected?

You can enable the raw gateway messages to appear in the Domoticz log by creating a user variable 'XiaomiMessage' of type Integer and value 1. (Setup -> More Options -> User Variables). Then restart the Gateway hardware in Domoticz. from http://www.domoticz.com/wiki/Xiaomi_Gat ... leshooting

XiaomiGateway: unhandled model: natgas
{"cmd":"report","model":"natgas","sid":"158d0001112b11","short_id":14003,"data":"{\"alarm\":\"0\"}"}
{"cmd":"report","model":"natgas","sid":"158d0001112b11","short_id":14003,"data":"{\"density\":\"0\"}"}
XiaomiGateway: unhandled model: natgas
{"cmd":"heartbeat","model":"natgas","sid":"158d0001112b11","short_id":14003,"data":"{\"voltage\":3600}"}

StefanoA wrote:PROBLEM OF COMMUNICATION AFTER REBOOT

I don't know if this is normal/happening to everyone, but for me it's a problem
After restart/reboot of Raspberry Pi3 & domoticz, if I look at LOG I always find communication problems like below



I figured out that if I go to HARDWARE page, select xiaomi gateway line and just push UPDATE button, the communication thread is restarted and communication is fixed and everything's working properly like shown below



so again, is this normal/happening to everyone else ?
is there any way to prevent this problem automatically in case of reboot/power loss ?

thanks

Coldman wrote: Could you please add Gas Sensor to Domoticz, logs:

corbin wrote:

Coldman wrote: Could you please add Gas Sensor to Domoticz, logs:

Thanks, have added to https://github.com/corbinmunce/domoticz

Setting it as a smoke detector, type same as the actual smoke detector. Anyone know if there is a more suitable device type for Gas?

Mat2Vence wrote:is there anyway to know easily in Domoticz which voltage device correspond to which sensor?
I saw reference of the hex code in another post, but there is nothing matching on my device list... anything I am doind wrong?

Swifty wrote:
Not sure if it helps, as I don't seem to have this problem, but if you run 'raspiconfig' I think there is an option in there to 'Wait for network on boot' (or something along those lines).
Maybe try to turn that on so that the network stack is fully up and address allocated etc. before Domoticz starts?

corbin wrote:If you don't have many devices, try matching them by battery level on the devices page