bmercier
Employees
-
Joined
-
Last visited
Solutions
-
bmercier's post in Hue Light - HTTP error 400 : Device cannot be added to the spoken database was marked as the answerUse Select tool | Connectivity | Device Hint Editor
Choose your device and change the hint to 1.0.0.0.
This will make it recognized as a dimmable device.
-
bmercier's post in Bad Request When Saving New Program was marked as the answerPlease try again, this should work better now.
-
bmercier's post in UD Portal: Cannot add certain devices to a webhook was marked as the answerThis is happening because the device type is not recognized. If you try to use /rest/nodes/<your device address>, the type is probably 0.0.0.0. This is typical of early nodeservers.
To fix this, use Select Tool | Connectivity | Device Hint Editor.
I'm not sure what this device can do, but if it can be set to a value of 0 to 100, I would suggest to try 4.17.x.x, which is the equivalent of a dimmable ZWave dimmer. If this is only fully on/off, you can also use 2.x.x.x, which is the equivalent of an insteon non-dimmable switch.
-
bmercier's post in UD Mobile - 404 Errors was marked as the answerShould be fixed now. A server had lost it's connection to the database somehow.
-
bmercier's post in ISY Portal Logs showing Passwords? was marked as the answerThis is your ISY error log. Portal does not capture anything from this data.
But I agree it probably should not appear in the ISY error log in the first place.
-
bmercier's post in Echo spokens get duplicated and then when deleted, echo thinks they are still there. was marked as the answerAnother thigh to try:
go to Alexa.amazon.com. There is a place with a button to forget all devices. This might help.
-
bmercier's post in UD Mobile constantly "restarting connection" was marked as the answerProblem is now solved permamently.
Benoit
-
bmercier's post in Portal dead again? was marked as the answerIt's up now. ISYs are reconnecting.
-
bmercier's post in Is ISY Portal down ? was marked as the answer
-
bmercier's post in [RESOLVED] HTTP error 500 at login was marked as the answer