It means the app is disabled or crashed, a device can still report to Homey (what the dev tools shows) even when an APP is disabled or even completely non existent.
Then the only option will be to contact Athom with the bug and restart Homey to see if that fixes it.
Iâm only retrieving the current state of devices, and if that device states it is unavailable, then it should be unavailable in your devices (Homey app or web app) too.
Yes. I will do that, but Athom takes over 3 weeks to reply now.
Donât know what happened to their support
v1.15 just released with just another small addition, all your insight entries, looks like I had way! more then I expected with 1358 different (âuniqueâ) entries myself, even after a big clean-up .
Changelog:
- v1.15 (October 16, 2023):
- Added: Insight entries (boolean (yes/no) & numbers)
Hi,
Would it be possible to add a function like this:
âconst showWifiDevices = true; // Names of all Wifi devicesâ
?
If there was something like that possible I would, but Homey has no way of knowing which device is WiFi/LAN, there is no specific flag for that or something. (at least not 1 that all developers have used)
Thank you Caseda for sharing this Homeyscript, much appreciated.
//delete notifications - clear timeline
Homey.notifications.deleteNotifications();
Hello,
How can I get the output of this overview sent to email or something else?
I would like to run this on weekly basis to check on devices.
For that the code would need a pretty big change, donât think I have time to change (/make a variant) the code for that in the few upcoming weeks though.
Yes, you could run it in the Homeyscript flow card âRun code and return text tagâ;
Paste the script into the code field;
Change the final return
line to:
return other + 'Other devices' + allDevices + 'Total devices';
(Not tested, but itâs the principle)
That flowcard provides for a local tag, which holds the data the script returned;
That tag can then be used in a message app card of your choice, like, âEmail Senderâ
It returns:
Returned: â77Other devices99Total devicesâ
Iâve updated the script because of the new moods that Homey Pro (early 2023) now has.
But also the latest update for HomeyScript updates the used Homey API, and that has a very small change for the zigbee module (zigbee
vs zigBee
, see the difference? ) which failed the zigbee part of the overview, so the script is now taking this into account that it will work on the older HomeyScript version as well as the new version.
In the mean time iâve also added zone names as overview option (wanted the zones available for the Moods to make that overview more clear).
And also the image count (with URLs if you enable it).
the URLs overview will be only the latter part of the URL as the only full URL I can get is including the Cloud ID and I donât want people sharing that, even if it is accidentally.
Changelog:
v1.16
- Fixed: New API uses
zigbee
vszigBee
, now taking this into account - Added: Zone names overview
- Added: Moods (Homey Pro (early 2023) only, not available for the older Homey Pros (yet?))
- Added: Images (Homey Pro (early 2023) only, missing scopes on the older Homey Pros)
still no option to get the output in a tag
Cause it wonât be an option, it will be an entirely new script, as the amount of changes necessary it will be easier to start pretty much a new.
Not getting paid for it or anything, would do it out of the good of my heart, in my own free time, which I already lacked of the last 8/9 weeks.
If it helps I could donate some money for your time.
Schon mal ChatGPT gebeten das Script entsprechend anzupassen?
Sorry.
Meant to say: have you tried ChatGPT to get the script altered according your wish?
If you could please keep the conversation in English as much as possible, then more people will be able to participate. If you would rather not or canât communicate in English then please check out Non-English boards/categories:
But feel free to try it with ChatGPT or any other large language model âAIâ (that doesnât know the currently used API version).
Sorry a second time. Just tried the PC version of ChatGPT 3.5. It wasnât easy to make it understand what it should do. It provided on every try interesting solution snippets. Couldnât get it to deliver a complete one. Some snippets did work well, some not so.