Can you open the console in your browser (preferably Chrome) and look at the object that’s printed from settings.js:50 and post a screenshot of it here?
(should look a bit like this:)
The error in the log breaks my head, I can’t really find what causes it, it doesn’t say which capability is invalid or what line caused the error. Not sure if it causes the Surveillance Mode to be not ready or it not being ready causes it but I think they’re linked.
Surprisingly the zones are now shows for both the Status and Instellingen pages.
I still had contact with my cousin. “According to my cousin we walked through the house and that’s the only thing we got to see. Couldn’t produce anything else but this.” I hope this is enough for you to continue with this. For me it is all acadabra so far because I have no knowledge of this.
We played with the settings, and if we turn off the speach settings, it’s possible to disable the setting. So this part is solved. Only the logs of the sensors when not armed remaines( blue lines). When armed it is registered in the log( light red).
Yes, that’s the settings, thanks.
They do look ok, I wonder why Delays showed up as undefined earlier, somehow the settings couldn’t be read at that point in time and may have caused the problems with not being able to change settings. I think that’s an isolated problem and seems to be not appearing anymore.
About the invalid_capability error at the beginning of the log, I’ve been able to reproduce that on my ‘production’ Homey that runs 2.5.2 (my dev runs 3.0.0) and I think that comes from a device who’s app has been updated to 3.0 and uses the new energy feature. The error is returned when calling the athom-api but I can’t find out which device but also found out it causes no issues so I’ll ignore it because the error is not thrown on 3.0.0 (which I expect to be released )
So, the remaining problem, not logging for devices that should log… I’m gonna dive into that part of the code again, I must be overlooking something…
I’ll keep you posted on progress!
(It could help if you could post a part of the log here when you run Heimdall from the cli and activate a sensor that should log, basically the part you posted earlier starting with the line of dashes just before stateChange)
I still had contact with my cousin. “According to my cousin we walked through the house and that’s the only thing we got to see. Couldn’t produce anything else but this.” I hope this is enough for you to continue with this. For me it is all acadabra so far because I have no knowledge of this.
@Ben found it!
Must have read over it a hundred times
With this release I commented out a lot of lines that log to the console, mistakenly I’ve also commented out the line that writes to the Heimdall log.
Fixed bug, introduced in 2.0.21, that caused devices to not log
Added condition flowcard to check if a device is logged
Added action flowcard to add logging to device
Added action flowcard to remove logging from device
In this version the bug introduced in 2.0.21 that caused devices to not log is fixed. Thanks to @Ben for reporting and providing information to help me fix the bug.
With this new update you can add or remove the Log setting from a device from a flow.
For example, remove the Log setting when the first person gets home:
That’s phase 2 of the changes that brings dynamic configuration of device settings in Heimdall through flows.
Next up is phase 3, which will enable you to set the Full and Partial settings on devices. Stay tuned!
Hi Danee,
Thanks. Everything works as before. Only the honor belongs not only to me but to @Jurgen_Heine and of course not to forget you. Thank you again
When the alarm is triggered, I want all my (hue) lights (± 20 lights) in the entire house to blink at full brightness (100%), at the same color and at the same speed (so on off on off etc) until the alarm is disarmed. I have Hue switches attached to the wall, so I want the lights to continue blinking even if someone presses the “off” button on the switch, but that’s quite easy to fix.
Does anyone have an idea how to create this? Any help is much appreciated!
You can make 2 flows that will loop one each other with condition “while alarm activated”. But be aware that it can be load to network to control 20 light at once on/off continuously.
Once alarm will be disarmed/canceled, flows will stop and you add another flow to turn off all lights or other condition.
I did a quick search, but nothing popped up. But I can’t imagine that no one has asked this: does Heimdall support smoke and CO-sensors? I can’t find it in the app, but it would be a great addition.
Hi. I created the flows for arming and disarming. Somehow i dont know why it keeps on arming and disarming on its own multiple times and stucks the flow. Can you address this please thanks