INTERACT FORUM
Devices => Engen -- Home Automation with Z-Wave => Topic started by: flac.rules on December 29, 2016, 11:44:22 am
-
I upgraded from 33 to 39, and i got a weird problem. I have a very simple testing setup with a fibaro wall plug that can be switched on and off, a scene containing the plug (device), which turns it on and off, this worked fine in 33, but when i upgraded to 39. It stopped working. I depaired the plug and paired it again, which seems to work fine. (the plug has a colored LED that indicates it is paired), however the device in engen seem to be behaving somewhat odd, turning it on or off does nothing, and adding it to a scene and turning that on or off also does nothing, and the device info seems to not be populated properly. I don't know if it is related, but using http://localhost:52199/-interface is not working either, just the http://localhost:52125/
{
"0:7": {
"node_info": {
"controlclasses": [],
"cmdclasses": []
}
}
}
-
Try powering down and back up.
-
Try powering down and back up.
Powering down the computer? If so, I already tried, but maybe you where thinking about something else?
-
I would power everything down and back up.
-
Tried powering down everything and up again, tried removing the device, and that seems to work (LED indicates it is unpaired), if i then re-pair it, the led indicates that it is paired, but no device shows up, if i then pair it again, i get a similar problem, the node has very little info, and no commands seems to work
{
"0:10": {
"node_info": {
"controlclasses": [],
"cmdclasses": []
}
}
}
-
We will look at this problem next week. Thanks for the report.
-
Tried powering down everything and up again, tried removing the device, and that seems to work (LED indicates it is unpaired), if i then re-pair it, the led indicates that it is paired, but no device shows up, if i then pair it again, i get a similar problem, the node has very little info, and no commands seems to work
In the latest versions, the software saves the command classes in the database within 30 seconds after receiving them from the device. Some devices are fussy about sending this information at any time except when they are first added to the network. So here is something to try:
- Remove the device from the network.
- Add it back to the network.
- Observe whether the command classes are now shown. They should be.
- Wait at least 30 seconds, to allow the server time to write the database.
- Shutdown the server.
- Look in C:\Program Data\J River\Engen 1\Database\ubase_* and check if the command classes were written to the database. They should have been.
- Restart the server.
- On startup the server is supposed to restore the command classes from the database. Check if they are now displayed.
If the command classes are displayed in the last bullet, the problem should be cleared.
If the problem persists, then somewhere in the procedure above the command classes will not be present when they should be. Knowing when that happens will provide an excellent clue to the problem.