gusmuche / homebridge-zipabox-platform Goto Github PK

HAP Warning: Characteristic 00000079-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000081-0000-1000-8000-0026BB765291. Adding anyway.

I’ve received a request to have the plugin compatible with the V3 API of Zipato.

Today I don’t have the possibility to test it, cause my Zipabox is an old v1 and cannot be updated to v3 without a additional Zipatile or Zipabox v2.

I’ll have a look on a demo possibility of the API to check the code and maybe add the possibility to request on V3 API.

Since 1.2.0 we can use the settings edition through a Json Form. This need to be documented inside the Readme.

See it in the eve app who a door or window is already moving.

Maybe check to PositionState Characteristic who need to return int 2.

J’ai 2 capteurs qui affichent la température mais sans avoir une batterie, pourtant sur HomeKit il est affiché que la batterie est basse pour ces 2 accessoires, comment désactiver la batterie sur l’affichage ?

I think it’s possible to avoid the use of noStatus and let the plugin choose if a device is available with a status or not.

It can be difficult for wired device, but this question as to be checked

I am using homebridge-zipabox-platform v1.8.0
in the accessories type list I do not see dimmer as Type of accessory,
anything special needed to enable it?

Work great in local, but generate a Internal Server Error 500 in remote access.
Need to be fixe.

Since the begin I use the plugin installed on a docker on my synology server.

I did't find the way to avoid some connection issue where the plugin need a full restart of the docker app (not only the container itself).

Since today I test the plugin on a fresh installation on a Pi image. Development ongoing on the v2 version (multiple services to accessories and quick update)

Just for info

Change the readme to avoid misunderstanding of lower and uppercase.
Or rename uuidb on uuid2 ?

Need a debug

V3 is not supported by Homebridge.

Need an update of the NPT package

After unconfig an accessory and restart homebridge, some accessories are still viewed inside Home App but with no functionality.

Solution was to delete the cachedAccessories files.

Debug made : unregister accessories BEFORE the end of configureAccessory is not possible.

The plugin now store the accessories to unregister and wait the right moment.

Hi, I would like to get assistance,
Homebridge Zipabox Platform stop working after few hours, and there is no connection to the homekit,
I need to restart the homebridge to reconnect to zipato again.

Attached log file:

Homebridge Zipabox Platform - error.txt

Thanks!

This is the error message I get :

BOXAPI] [getAttributesValue] Error occurred on getAttributesValue : FetchError: invalid json response body at https://my.zipato.com/zipato-web/Index reason: Unexpected token < in JSON at position 121
at /usr/local/lib/node_modules/homebridge-zipabox-platform/node_modules/node-fetch/lib/index.js:273:32
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
type: 'invalid-json'
}

Once using a temperature sensor

In fact I found the solution : it's mandatory to enable : "refresh": 600

The value 600 was chosen in order to avoid a timeout with the server

Because else without a refresh it seems the connection to the server disconnects after some inactivity: time-out thus it's needed to re authenticate. If a refresh is enabled it maintains connection to the server and no disconnection because of no activity

I would recommend to enable by default a refresh for devices like temperature sensors or manage error : in case of the error relaunch a new connection to the server api this solution is better because it avoid to connect often to the server to maintain the connection

Hey there, first of all thank you for your work, it's amazing! I would like to ask that is there any way to control radiator valves through zipato with this plugin? Thank you!

Seems that using the option useCache = true freeze the value of some sensors.

Problem is know, on work

The list in Readme is not complete. I must add my accessories. Our user can maybe add this in this Issue.

Next release will validate this.

Also compatibility with the last package of config-UI

ZIPAC] [reconnectAfterError] Found error but not manage : [BOXAPI] [getSecurity Status] Bad return > no status find for this partition. undefined [alarm/Maison-DEV]

Have an error for some alarm. The status inside Zipato API disappear !

Get all correct when arming and disarm alarm form Zipato Deskboard.

Maybe putAlarm status is wrong...

Zipato interface give us the real percentage of battery level. Would be great if the plugin do the same additionally to the Lower Status.

API Zipato can send all the attributes UUID available in the box.
The plugin can then use it to check if the configured UUID are in this list or not and avoir mis configuration for this.

Hello,

Have this problem, when install a plugin

[9/22/2020, 9:49:22 PM] [ZipaboxPlatform] [BOXAPI] [fstatus] Error on fstatus. Unauthorized
[9/22/2020, 9:49:22 PM] [ZipaboxPlatform] [PTFM] [connectTheBox] Unexpexted error before security : Error: Unauthorized
at ZipaboxApi. (/homebridge/node_modules/homebridge-zipabox-platform-dev/lib/zipaboxApi.js:701:16)
at new Promise ()
at ZipaboxApi.fstatus (/homebridge/node_modules/homebridge-zipabox-platform-dev/lib/zipaboxApi.js:695:12)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
[9/22/2020, 9:49:22 PM] [ZipaboxPlatform] [PTFM] [connectTheBox] Error on connectTheBox after security : Error: Error: Unauthorized
at ZipaPlatform.manageError (/homebridge/node_modules/homebridge-zipabox-platform-dev/lib/platform.js:118:13)
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Issue from Thierry

Device is working with correct value but symbol in Home App stay as unactive

With 30 accessories, I need to update the plugin twice to have the values. That's not so good.I'm working with an iPad as concentrator, but didn't have any other choices.

Maybe avoid to call the api too much for some accessories

Add some examples of config file inside an example directory of the package

Bonjour
J’ai cette erreur dans les logs même avec la dernière version
Merci d’avance
Thierry