décembre 23, 2015 à 2:57 #2188
I’m trying to create a simple scene with blocky to control my zwaves devices.
meanwhile my devices are correctly controled under dashboard, I have 2 issues:
1- dashboard display is wrong, it showing a device “On” while it’s “Off” and vice versa. When I switch state the dashboard is switching but after 5 or 10 seconds it goes back to previous display state, but the device state does not change.
2- In Blocky scenes my devices are not controled, even with the simplest scene with just zwave device command, the device do no change state.
I’ve restarted all services, an even pulsestation, updated all modules, but nothing is changing.
Does anyone experience such issue and have a clue for resolution?décembre 26, 2015 à 8:32 #2214MikaMaître des clés
Did you already try to exlude and the reinclude your device to your controller ?décembre 26, 2015 à 4:01 #2222
Also make certain the device is not too far from your usb key while testing.
It may be range related.
K.Rensjanvier 2, 2016 à 10:35 #2316
Thanks for your answers.
Yes I allready exclude a reinclude my devices. And my devices are working well with the dashbord commands, there is only a few meters with he devices.
One other thing is that when I activate the scene service, one of my device is always shuting down.
I put it on through dashboard or device button, then after few seconds (1minute max) it goes off.
When I was using synozwave all worked fine, except dashboard refresh about devices state.
I once installed Domoticz with Zwave support and I had this behaviour too.
I can’t figure what in my system is doing that.janvier 2, 2016 à 11:14 #2317
Since the device turns off when you activate the scene service, I would assume one of your scenes is telling the device to turn off.
It should otherwise not do it.
Can you also check whether the device that is turned off is not associated to another device?
Maybe something is supposed to turn of, but since the devices are associated (coupled), it also turns of the other device.
If that doesn’t resolve it, we will have to look on your system what could be the cause.
K.Rensjanvier 4, 2016 à 12:18 #2328
I have tried with no scene at all and my device still goes off.
I got only 3 zwave devices on my system: 2 Fibaro wallplugs and one Aeon labs Zwave stick.
I don’t remember that I ever coupled device.
Maybe I have some old files from previous install, scenes on my system…janvier 5, 2016 à 5:20 #2337MikaMaître des clés
First, If you said that you have the same behaviour with Domoticz, it probably means that it’s something with OpenZwave and the configuration of your device.
Did you already try to reset your wallplugs ?
Do you see in the association tab that your wallplugs are only associated to your controller (zwave-1)janvier 6, 2016 à 2:01 #2345
I’ve reseted my entire system last month by desassociate my plugs and then reassociate them.
In the association tab I have only zwave-1 (which is my aeon stick) at the botom of the page, with a “delete association” option.
I have nothing in groups 1 and 2.janvier 6, 2016 à 2:09 #2346
I think I will have a look on your system.
Can you mail us (to the store mail adress) credentials to ps, url and precise explanation what is wrong at which step and what happens / should happen?
K.Rensjanvier 25, 2016 à 10:39 #2540
With the help of Mika and Koen it works for 2 days :D.
but now scene does not work anymore. No logs at all.
I’ve restarted scene service, change scene period, then reinstall it, then reboot DS, and nothing work, scene service still have no logs.
Is there a sort of cron? where can I look for a clue?janvier 31, 2016 à 1:07 #2572
And if you start the scene service from the command line?
Just put autorestart on no, stop the scene service and start it from the terminal?
K.Rensfévrier 1, 2016 à 7:14 #2608
Sure I can try,
how do I do that? Is it a curl command or something like that to launch?février 3, 2016 à 12:06 #2625
Instructions are here:
Basically you need to enable ssh and connect to your server in command line mode.
K.Rensfévrier 9, 2016 à 3:16 #2689
I don’t know why but the service worked the 1st of february for 00H00m to 18H18m and since then nothing.
I have been in /volume1/web/PulseStation/services/scene and launch ./scene, here is the result:
2016-02-09 14:14:48.253 Starting service scene at port : 4040
ps: invalid option — ‘a’
BusyBox v1.16.1 (2015-10-28 13:16:35 CST) multi-call binary.
Report process status
w Wide output
every minute I get this Ps error.février 9, 2016 à 4:12 #2690
I’ve desinstalled all and reinstall all again.
now I can’t even add a zwave controler to the dashboard…
I’m trying to reinstall again…
- Vous devez être connecté pour répondre à ce sujet.