For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Think about update stable version to 0.3.1

Version: stable=0.3.0 (1056 days old) => latest=0.3.1 (15 days old)
Installs: stable=83 (79.05%), latest=undefined (NaN%), total=105
Click to edit

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/ioBroker/ioBroker.pimatic

• [E104] No common.titleLang found in io-package.json
• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [E301] Tests on Travis-ci.org are broken. Please fix.
• [E605] No actual year found in copyright. Please add "Copyright (c) 2017-2022 bluefox [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2017-2022 bluefox [email protected]" at the start of LICENSE

I have also found warnings that may be fixed if possible.

• [W505] setTimeout found in "main.js", but no clearTimeout detected

Thanks,
your automatic adapter checker.

Think about update stable version to 0.2.1

Version: stable=0.1.5 (1056 days old) => latest=0.2.1 (15 days old)
Installs: stable=141 (89.81%), latest=16 (10.19%), total=157
Click to edit

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Hi Bluefox, this is really THE plugin I've waited for!!!

But when starting it seems to have issues with defied variables (all kinds: text, bolean etc.) when tries to map. My pimatic Version is the version (0.9.5).
When i look into the pimatic.0 object list, only the first device in my pimatic list is loaded (but also without any value)

Here is the log from ioBroker:

pimatic.0	2017-03-24 17:57:57.726	info	disconnected
pimatic.0	2017-03-24 17:57:57.719	error	at Decoder.add (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/node_modules/socket.io-parser/index.js:246:12)
pimatic.0	2017-03-24 17:57:57.719	error	at Decoder.Emitter.emit (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/node_modules/socket.io-parser/node_modules/component-emitter/index.js:134:20)
pimatic.0	2017-03-24 17:57:57.719	error	at Decoder. (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
pimatic.0	2017-03-24 17:57:57.719	error	at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/lib/manager.js:332:8)
pimatic.0	2017-03-24 17:57:57.719	error	at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
pimatic.0	2017-03-24 17:57:57.719	error	at Manager. (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
pimatic.0	2017-03-24 17:57:57.719	error	at Socket.onpacket (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/lib/socket.js:228:12)
pimatic.0	2017-03-24 17:57:57.719	error	at Socket.onevent (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/lib/socket.js:270:10)
pimatic.0	2017-03-24 17:57:57.719	error	at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
pimatic.0	2017-03-24 17:57:57.719	error	at Socket. (/opt/iobroker/node_modules/iobroker.pimatic/main.js:512:50)
pimatic.0	2017-03-24 17:57:57.719	error	TypeError: Cannot read property 'mapping' of undefined
pimatic.0	2017-03-24 17:57:57.712	error	uncaught exception: Cannot read property 'mapping' of undefined
pimatic.0	2017-03-24 17:57:57.699	warn	Unknown state: pimatic.0.devices.dewpoint-diff-trigger-AZ
pimatic.0	2017-03-24 17:57:57.699	warn	Unknown state: pimatic.0.devices.pump-available-master
pimatic.0	2017-03-24 17:57:57.699	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-kaminraum-tag
pimatic.0	2017-03-24 17:57:57.699	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-treppe-lila
pimatic.0	2017-03-24 17:57:57.698	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-treppe-hell
pimatic.0	2017-03-24 17:57:57.698	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-treppe-ambiente
pimatic.0	2017-03-24 17:57:57.698	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-ALARM
pimatic.0	2017-03-24 17:57:57.697	warn	Unknown state: pimatic.0.devices.panikmode
pimatic.0	2017-03-24 17:57:57.696	warn	Unknown state: pimatic.0.devices.testvariable3
pimatic.0	2017-03-24 17:57:57.696	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-ambiente-kaminfeuer
pimatic.0	2017-03-24 17:57:57.696	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-lesen
pimatic.0	2017-03-24 17:57:57.696	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-ambiente-blau
pimatic.0	2017-03-24 17:57:57.696	warn	Unknown state: pimatic.0.devices.hue-user
pimatic.0	2017-03-24 17:57:57.695	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-stereomodus
pimatic.0	2017-03-24 17:57:57.695	warn	Unknown state: pimatic.0.devices.stereo-modus
pimatic.0	2017-03-24 17:57:57.695	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-discomodus
pimatic.0	2017-03-24 17:57:57.695	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-relax
pimatic.0	2017-03-24 17:57:57.694	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-normal
pimatic.0	2017-03-24 17:57:57.693	warn	Unknown state: pimatic.0.devices.hue-scene-lichter-security-standard
pimatic.0	2017-03-24 17:57:57.693	warn	Unknown state: pimatic.0.devices.hue-scene-tv-dunkel
pimatic.0	2017-03-24 17:57:57.693	warn	Unknown state: pimatic.0.devices.hue-scene-tv-hell
pimatic.0	2017-03-24 17:57:57.693	warn	Unknown state: pimatic.0.devices.s
pimatic.0	2017-03-24 17:57:57.693	warn	Unknown state: pimatic.0.devices.h
pimatic.0	2017-03-24 17:57:57.692	warn	Unknown state: pimatic.0.devices.c
pimatic.0	2017-03-24 17:57:57.692	warn	Unknown state: pimatic.0.devices.d
pimatic.0	2017-03-24 17:57:57.692	warn	Unknown state: pimatic.0.devices.disco-modus
pimatic.0	2017-03-24 17:57:57.692	warn	Unknown state: pimatic.0.devices.cams-aussen-routine-running
pimatic.0	2017-03-24 17:57:57.691	warn	Unknown state: pimatic.0.devices.cams-innen-routine-running
pimatic.0	2017-03-24 17:57:57.691	warn	Unknown state: pimatic.0.devices.cams-innen-routine
pimatic.0	2017-03-24 17:57:57.691	warn	Unknown state: pimatic.0.devices.cams-aussen-routine
pimatic.0	2017-03-24 17:57:57.691	warn	Unknown state: pimatic.0.devices.simulationmode
pimatic.0	2017-03-24 17:57:57.691	warn	Unknown state: pimatic.0.devices.lichter-routine
pimatic.0	2017-03-24 17:57:57.690	warn	Unknown state: pimatic.0.devices.dewpoint-diff-trigger
pimatic.0	2017-03-24 17:57:57.690	warn	Unknown state: pimatic.0.devices.ospi-hitze-bewaesserung-already-run-today
pimatic.0	2017-03-24 17:57:57.690	warn	Unknown state: pimatic.0.devices.ospi-hitze-bewaesserung-15min
pimatic.0	2017-03-24 17:57:57.690	warn	Unknown state: pimatic.0.devices.ospi-hitze-bewaesserung-30min
pimatic.0	2017-03-24 17:57:57.690	warn	Unknown state: pimatic.0.devices.alarmmode
pimatic.0	2017-03-24 17:57:57.689	warn	Unknown state: pimatic.0.devices.anybodyhome
pimatic.0	2017-03-24 17:57:57.688	warn	Unknown state: pimatic.0.devices.lichter-routine-running
pimatic.0	2017-03-24 17:57:57.189	info	connected
pimatic.0	2017-03-24 17:57:54.663	info	starting. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.pimatic, node: v4.7.0
host.mon-pi	2017-03-24 17:57:52.316	info	instance system.adapter.pimatic.0 started with pid 27681
host.mon-pi	2017-03-24 17:57:22.301	info	Restart adapter system.adapter.pimatic.0 because enabled```

Connection to pimatic server "solar-srv" fails, host connection ok, but pimatic failed.
I looked around and found an issue from last year, but that should have been repaired.
Here is the debug code after pimatic reset:

• debug system.adapter.admin.0: logging true
• debug redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1528283774569,"q":0,"from":"system.adapter.admin.0","lc":1528283774569}
• debug redis pmessage io.pimatic.0.* io.pimatic.0.info.connection {"val":false,"ack":true,"ts":1528283768146,"q":0,"from":"system.adapter.pimatic.0","lc":1528187888302}
• debug Connect: http://solar-srv:80/?username=admin&password=xxx
• info starting. Version 0.1.5 in /opt/iobroker/node_modules/iobroker.pimatic, node: v8.11.1
• info States connected to redis: 127.0.0.1:6379
• debug statesDB connected
• debug objectDB connected
• info instance system.adapter.pimatic.0 started with pid 8091

http connection to the pimatic api are working:
http://solar-srv/api/devices -> all connected devices

Thanks for your help

I couldn't find a function to synchronize iobroker with pimatic.
My iobroker is implemented on an ubuntu server, which is switched off over night.
Is there any method to get past data from pimatic into iobroker so vis can display all data.
A symmetric synchronisation is not necessary.

Hey,

first you Adapter works great! Thank you alot for it :)

I hope this project is not dead =/ ... it is possible to also get the Variables in Iobroker? I had some Variablesdevices in Pimatic there get his Values in the moment over a PHP-Script that gets the Values over the Iobroker REST API (Simple API) now i want to change it and want use "blocky" to Update the values but it seems its not possible to push values directly over the "VariablesDevices" thats already in Iobroker.

Greetings
Milcho

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

here my Logfile

so heute noch mal in das Log geschaut nach dem der Adapter immer noch auf Rot steht... da stand dann das

pimatic.0 2018-08-23 09:45:09.124 info disconnected
pimatic.0 2018-08-23 09:45:09.116 error at Decoder.Emitter.emit (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-parser/node_modules/component-emitter/index.js:134:20)
pimatic.0 2018-08-23 09:45:09.116 error at Decoder. (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/component-bind/index.js:21:15)
pimatic.0 2018-08-23 09:45:09.116 error at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/lib/manager.js:332:8)
pimatic.0 2018-08-23 09:45:09.116 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/component-emitter/index.js:133:20)
pimatic.0 2018-08-23 09:45:09.116 error at Manager. (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/component-bind/index.js:21:15)
pimatic.0 2018-08-23 09:45:09.116 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/lib/socket.js:228:12)
pimatic.0 2018-08-23 09:45:09.116 error at Socket.onevent (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/socket.io-client/lib/socket.js:270:10)
pimatic.0 2018-08-23 09:45:09.116 error at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.pimatic/node_modules/component-emitter/index.js:133:20)
pimatic.0 2018-08-23 09:45:09.116 error at Socket. (/opt/iobroker/node_modules/iobroker.pimatic/main.js:510:9)
pimatic.0 2018-08-23 09:45:09.116 error at syncDevices (/opt/iobroker/node_modules/iobroker.pimatic/main.js:213:87)
pimatic.0 2018-08-23 09:45:09.116 error TypeError: Cannot read property 'replace' of undefined
pimatic.0 2018-08-23 09:45:09.116 error uncaught exception: Cannot read property 'replace' of undefined
pimatic.0 2018-08-23 09:45:09.064 info connected
pimatic.0 2018-08-23 09:45:07.630 info starting. Version 0.1.5 in /opt/iobroker/node_modules/iobroker.pimatic, node: v6.14.2

????????????????????
please help

Hey,

i've got a problem with my pimatic (maybe in general). Pimatic stops working and in my logs I found a message like 'SQLITE_BUSY: database is locked'.

Does this adapter connects to the pimatic database?

I guess that when the adapter reads or write something, my pimatic stops working with this message.

Thanks in advance! :)

https://travis-ci.org/ioBroker/ioBroker.pimatic

Values of pimatic variables are updated in pimatic when edited in ioBroker, but not vice versa (means if I updated the value in pimatic, changes didn't synchronize to ioBroker

I am an automatic service from ioBroker that searches adapters and makes suggestions.

I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.

Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.

Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.

Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.

On questions, the other developers will support in the forum or via GitHub issues too.

If no detection is possible, simply close this issue and I won't bother you again. ;-)

Thanks,
your automatic adapter checker.

After migrating to Controller Version 4.x the adapter throws errors when writing to pimatic variables objects ''devices':

The missing part of the code is the new mandatory definition of "common.type"

Object of state "pimatic.0.devices.xxxxxxxxx" is missing the required property "common.type"

Could you pls. update the adapter to be compatibel with controller 4.x and node 14.x / 16.x

This adapter is 'mission critical' and absolutely necessary for my setup!

THX in advice

decrypt/encrypt are available on adapter directly migrateEncodedAttributes is no longer existing.

Selected methods will be exposed via adapter-core in the near future