Great! I’ll report once it’s there
-
Self - Ad iOS App Pimate
-
Another thing, I tried the app on my iphone and found some issues (maybe known?):
- VariablesDevice: Add option to choose which variable to show
- AqaraSensors: Value not showing (Temp/Humiditiy) (Bug?)
- Button device: Add custom label? Maybe “press” or something, so it’s better visible as a button
- MaxWindowSensors: No label shown (open/closed) (ios 12, iphone8) Bug?
-
@georg90
the supported device types are in the app description.
new ones are added per request and time after time.
I have the Aquara sensors on the schedule already, I’m just waiting for my aqara hardware
The Button should show the label you give it in Pimatic and are in a extra color make them better visible, if you have multiple buttons in one button array, a popup opens and you should see the buttons in the array.I’ll have a a look whats going on with the maxWindowSensors.
can you send me a configuration example of a variable device with multiple variables? then I can check if I can implement it.
-
Okay, my mistake. I thought all devices that show up are supported as well.
For the buttons: they are Mqtt buttons and are not showing a different label (maybe they just need to be added to the button type?)
Variables device with multiple variables:
{ "variables": [ { "name": "bathroom_temp", "expression": "$bathroom_temp", "type": "number", "unit": "°C", "acronym": "Bad", "discrete": true }, { "name": "livinroom-temp", "expression": "$livinroom-temp", "type": "number", "unit": "°C", "discrete": true, "acronym": "WZ" }, { "name": "bedroom_temp", "expression": "$bedroom_temp", "type": "number", "unit": "°C", "acronym": "SZ", "discrete": true }, { "name": "temp_buero", "expression": "$buero-temp", "type": "number", "unit": "°C", "discrete": true, "acronym": "Büro" }, { "name": "openwindow_temp", "expression": "$openwindow_temp", "type": "number", "unit": "°C", "acronym": "Offen", "discrete": true }, { "name": "Home", "expression": "$somebodyhome", "acronym": "Home" } ], "xAttributeOptions": [ { "name": "bedroom_temp", "displaySparkline": false }, { "name": "bathroom_temp", "displaySparkline": false }, { "name": "openwindow_temp", "displaySparkline": false }, { "name": "Home", "displaySparkline": false }, { "name": "livinroom-temp", "displaySparkline": false }, { "name": "temp_buero", "displaySparkline": false } ], "id": "saved-temperatures", "name": "Saved temperatures", "class": "VariablesDevice" }
MQTT buttons:
{ "buttons": [ { "id": "haustuer-oeffnen", "text": "Öffnen", "topic": "/espTuer/hausTuer", "message": "oeffnen" }, { "id": "testKlingelRule", "text": "testKlingelRule", "topic": "/nothing/nothing" } ], "id": "mqtt-haustur-oeffner", "name": "Haustür Öffner", "class": "MqttButtons" }
-
@georg90
great, thanks for the examples, I’ll see what I can do -
@georg90
Update should be online -
@theslashy said in Self - Ad iOS App Pimate:
@georg90
Update should be online@georg90
can you send me the output of the maxcontact sensor api, just from your browser like this:
http://192.168.1./api/devices/maxcontactI can’t really test it, because without the max cube the contact sensor always stays “unknown”
The mqtt Buttons will work in the next update, I work on the other things too.
-
Here you go. They are maxcul-sensors in fact. Does this make a difference?
{ "device":{ "id":"windowssensor", "name":"Schlafzimmer Tür", "template":"maxcul-contact", "attributes":[ { "description":"State of the contact", "type":"boolean", "labels":[ "closed", "opened" ], "label":"Contact", "discrete":true, "name":"contact", "value":true, "history":[ { "t":1538570273588, "v":false }, { "t":1538570704978, "v":false } ], "lastUpdate":1538669706535 }, { "label":"Battery State", "description":"state of the battery", "type":"string", "labels":[ "low", "ok" ], "acronym":"Bat.", "discrete":true, "name":"battery", "value":"ok", "history":[ { "t":1538634483015, "v":"ok" } ], "lastUpdate":1538670482419 } ], "actions":[ { "description":"Returns the current state of the contact", "returns":{ "contact":{ "type":"boolean" } }, "name":"getContact" }, { "params":{ }, "name":"transferConfigToDevice" } ], "config":{ "id":"windowssensor", "class":"MaxculShutterContact", "name":"Schlafzimmer Tür", "deviceId":"013318", "pairIds":[ ] }, "configDefaults":{ "deviceId":"000000", "groupId":"00", "guiShowConfigButton":false, "pairIds":[ ] }, "capabilities":[ "Sensor", "ContactSensor" ] }, "success":true }
-
@georg90
thanks I’ll have a lookIt will take a few days more.
I just managed to kill my test enviroment with the 0.9.43 update. -
@theslashy said in Self - Ad iOS App Pimate:
@georg90
thanks I’ll have a lookIt will take a few days more.
I just managed to kill my test enviroment with the 0.9.43 update.So an update should be online now,
It supports mqtt Buttons and MaxCul Shutters, check it out! -
Looks good! Thank you!
I like the app 💪 Good work!
-
@georg90 said in Self - Ad iOS App Pimate:
Looks good! Thank you!
I like the app 💪 Good work!
Great, glad you like it!
If you have any suggestions just drop me a message.
-
Hello … On the application I do not see the status of the raspbee sensors. In my case the door sensor and temperature, humidity. Can you provide an update please?
-
@andi-tudor
I will have a look at it, I have no raspbee devices, so i have to try -
@andi-tudor said in Self - Ad iOS App Pimate:
Hello … On the application I do not see the status of the raspbee sensors. In my case the door sensor and temperature, humidity. Can you provide an update please?
could you send me the output of the rest-api for the devices you want?
I can’t really simulate this without a rasbpee device myself.Something like this: https://IPADDRESS:PORT/api/devices/raspee-contact
-
@theslashy hi… reupload the output
-
@theslashy Hello. Thanks for the update. It works very well.