@mwittig said in pimatic@0.9.47:

@ortin said in pimatic@0.9.47:

Could it be a solution to show a simple “-0” instead of “unknown” for an undefined value.

Possibly, yes…

In 0.9.50 the message still occures. Seems this is open. Must this be handled by the plugin or the core. I really have no clue!

I’m having some trouble with pimatic. It was running alright (although there seemed to be something wrong with de graph part, as no historical data was displayed, while I could still see new data come in every few minutes.

After adding a sensor in the config, and rebooting, the errors below started showing:

debug [pimatic]: Error: Error restarting pimatic, exit code 1
at EventEmitter.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic/lib/framework.coffee:650:23)
at emitOne (events.js:77:13)
at EventEmitter.emit (events.js:169:7)
at ChildProcess.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic/lib/framework.coffee:644:43)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:854:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
21:38:48error [pimatic]: Error restarting pimatic: Error restarting pimatic, exit code 1
21:38:22debug [pimatic]: TypeError: Cannot read property ‘trx’ of undefined
at /home/pi/pimatic-app/node_modules/pimatic/lib/database.coffee:201:44
at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:694:18)
at _drainQueueStep (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:138:12)
at _drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:131:9)
at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:147:5)
at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
at processImmediate [as _immediateCallback] (timers.js:383:17)

I don’t know what this means, is it database problems?

After removing the sensor from the config to check whether this gave problems, nothing seemed to change. Still the same “trx” messages.

I like to bump this even there was no considerable resonance.

Maybe it is more helpfull to see a picture and a more detailed description. My idea is to be able to create a dummy device like this:

It contains following elements:

VariableDevice DummySwitch DummyDimmer ButtonDevice

Basically all DummyDevices and some further usefull devices should be able to be added like:

InputDevice VariableInputDevice VariableTimeInputDevice DummyShutter DummyHeatingThermostat DummyContactSensor DummyPrecenceSensor DummyTemperaturerSensor

With this we are able to create a combined device for a room in really compact form. From my point of view it is more elegant as to have 4 seperate devices in a group call “Raum”

@Pedder
deconz already has a startup script so you can control the service via systemctl
you can check if the autostart is enabled

sudo systemctl is-enabled deconz # if disabled sudo systemctl enable deconz

No, I am using an mqtt server hosted on my server. (where pimatic also runs with the mqtt plugin)
the shellys provides only a webserver/api

yep, log file did it

17:35:36.887 [pimatic] info: Loading plugin: "pimatic-samsung-tv" (0.9.0) 17:35:36.910 [pimatic] error: Unexpected token {

But I honestly don’t know what to do with that information
The 2016-plugin isn’t my case just because my TV is pre-2016 built

you can use the command line program tuptime.
it indicates the last restart reason.

> tuptime ... System shutdowns: 1 ok -> 1 bad ... > tuptime -t -c -r | awk -F, 'NR==3 {print $5}' "BAD"