Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


  • 0

[SCENE] Smart Message Hub {v1.2} - NEW RELEASE


AutoFrank

Question

Hi Everyone

 

Smart Message Hub v1.2 (SMsgH v1.2) is now available.

This release includes fixes tor three bugs that had various impacts and support for international characters.

Thanks to @Sankotronic and @szmyk for locating the faults and extra feature for international characters

 

"FIRST TIME USERS" -  Please read below and follow the instructions laid out for first time users

UPGRADING FROM 1.1b to 1.2 - Please use this

Please login or register to see this link.

 - if you are a current user and may wish to consider  avail of the fixes or extra feature

 

This scene enables a user to send a message from either a scene or a virtual device to a number of notification and TTS services with a startScene call

Please login or register to see this code.

The scene also enables messages to be re-routed or queued depending on whether the house is set to Away mode, Sleep mode or if internet is not available. (See below for more details)

 

A demo  VD {v1.1} is also available to help demonstrate the scene features.

 

SCENE FEATURES

Smart Configuration options include the ability to re-route and/or queue all messages under certain conditions. (Internet unavailability , home occupancy mode presentState = Away)

Messages with international characters are also supported

  • Notification messages can be redirected to Home Center 2 Popup notification service if the internet is offline or unavailable
  • Notification messages can be queued if the internet is offline or unavailable. 
    • All Messages in the queue will be released as one combined message once the internet come s back online.
  • All TTS messages can be redirected to Home Center 2 Popup notification service if the internet is unavailable or offline or if the sonosAPI is offline if this solution is being leveraged
    • All TTS messages can be queued if presentsState = Away. 
  • All TTS messages in the queue will be announced once presentsState = Home
  • Simplified the message invocation method to startScene
    • Invoked via startScene(SMsgHid, {message string} (SMsgHid is the id of the SMsgH scene when it is saved to your system )
    • See below for examples
    • messageHub global no longer required (please delete when you have migrated all your scenes to using 1.1)
  • Added support for sleepState (no TTS messages if set to Sleep)
  • Additional support for HC2 popup notifications
    • Types (Critical, Successs, Info, Warning)
    • Images (use full url)
    • Buttons (represented as a table) - See @Sankotronic 

      Please login or register to see this link.

      on popup notifications to see how to format
    • Added ability to delay unloading of TTS messages by predefined time in seconds
    • Added support for custom language in for TTS and Notify redirects default Popup title and subtitle
    • Minor bug fixing and code cleaning

 

Configuration options also include a default message notification target, title, subtitle and volume but all these can also be specified as part of the message invocation.

There are three levels of debug verbosity. In normal mode there is a minimal amount of information displayed as the scene is triggered.

The two other modes allow for much more expressive displaying of scene variables as well as configuration settings if enabled

deBgVar is enabled in the scene so you can see the interactions- it can be disabled in normal running mode

 

SCENE MESSAGING OPTIONS
The supported services in this release include the following (supported in 1.0 & 1.1)

  • Pushover Notifications ------------------------------------------------------->  

    Please login or register to see this link.

  • allinone ( jompa68 scene)
  • Telegram messages
  • hc2email (Home Center 2 email service) 
  • hc2push (Home Center 2 push notification service)
  • hc2popup (Home Center 2 Popup Notification service) -------------------> [TUTORIAL}

    Please login or register to see this link.

     
  • Sonos-api based TTS -------------------------------------------------------->  [TUTORIAL] 

    Please login or register to see this link.

  • Sonos VD Remote based TTS ----------------------------------------------->

    Please login or register to see this link.

 

I have also included a Companion Demo VD. The virtual device will allow the user to demonstrate the scenes queuing/unloading capabilities.

CAUTION: The companion VD in demo mode can adjust the presentState and sleepState globals and will cause any other scene you may have with this as a trigger to execute

 

A simplified version of the LAN Monitor VD called  the WWWAPI Monitor will monitor just the sonos-api if desired and does not any in-built notification options like the LAN Monitor VD 2.5.Smart Message Hub users should use either the WWWAPI Monitor or LAN Monitor 2.6

 

Special thanks extended to  @Sankotronic @petergebruers, @jompa68 and @szmyk for their contributions leading to 1.2

 

Once the scene configuration is complete I would recommend running the demonstration virtual device.

This will give you a better understanding of the options and features as well providing some sample messages that you can run.

 

Ideas for subsequent revisions are always welcome
_f

    
  RELEASE CHANGELOG
  v1.0  - First release (march 4th 2017)

  v1.1 - Second release (march 17th 2017)

  v1.2 - Third Release (june 24th 2017) 

 

 

                                                                            ================================================

                                                                             FIRST TIME USERS - INSTALLATION & CONFIGURATION

                                                                            ================================================
The code is available in both lua and txt format below

Paste code into scene and run - All global variables will be automatically created (Please do not adjust global triggers in scene header)

  • Configure options as required at top of scene (line 100 onwards)
  • Configure enable smart redirects
  • Configure HC2 email settings, HC2 push settings and TTS services
  • Configure default message titles, subtitles and volume
  • Configuration notification settings, tokens, etc
  • Enable/Disable increased debug and config verbosity for troubleshooting

  
MESSAGE INVOCATION
  This message hub can be called from either a scene or a virtual device using a startScene call. The following is an example Sample invocations are included below

Please see the section on Message Invocation lower down in this post of you wish to send messages with international characters

Please login or register to see this code.

Note: Replace IDofSMsgHscene with HomeTable reference of numerical ID of the SMsgH scene when it is installed on your system    

You need to include all parameters up to last one you populate. For example, if you want to specify a subtitle, you need to include message, target, volume and title as well.

You CANNOT leave out a parameter in the call. Leave as "" if not used/required and default will be invoked.

 

**USER CONFIGURATIONS & SETTINGS**


OPTIONS FOR SMART RE-ROUTING OF MESSAGES
The following four options can be set to true or false depending on what features you wish to enable.

Please login or register to see this code.

Set to true to enables re-routing of sonos TTS messages from either the Sonos VD or the sonos-api solution to HC2 notification Popup if the sonos-http-api or Internet is unavailable/offline to your local LAN  

Please login or register to see this code.

Enable to Silence  TTS announcement in sleepState, TTS announcements are NOT queued, they are simply discarded

Please login or register to see this code.

 

Enable a Delay before TTS announcements are unloaded (seconds). Leave as "" for no delay

Please login or register to see this code.

 

Set to true to enable Sonos TTS messages to queue when presentState = 'Away'. When presentState is set to Home it triggers the scene to automatically unload all the messages in the TTS queue to the default player that has been named in the configuration section  

Please login or register to see this code.

Set to true to enable all notifications to re-route to HC2Popup notifications if the internet is unavailable/offline to your local LAN  

Please login or register to see this code.

Set to true to enable all notifications to queue when presentState= 'Away'. When presentState is set to Home it triggers the scene automatically and unloads the message in the notifications queue to the default notification service that has been named in the configuration section below

 

The scene as provided has all these 4 options set to true and this is the recommended setup if you wish to leverage full functionality and the demo
  
OPTIONS TO MONITOR THE INTERNET STATUS
To achieve the most benefit from this scene the internet and sonos-api should be dynamically monitored. Dynamically monitoring the internet will enable messages (TTS and notifications) to be queued while the internet if offline. Queued message can also be sent as hc2 pop notifications on the local LAN. The preferred monitoring option is named here. The example below is setup to use the LAN Monitor VD 2.5

Please login or register to see this code.

There are 3 options available: 

  • Select 'manual' if you wish internet and sonos-api to be permanently set to online. Please 
  • note that this option does NOT enable queuing of notification messages.
  • Select 'networkTable' to leverage the LAN Monitor VD 2.5, 
  • Select 'wwwapiTable' to leverage the new simplified WWWAPI Monitor 1.0

                               
 

HC2 EMAIL CONFIGURATION

Please login or register to see this code.

List all users that you want to be able send messages to. The user id's are located from the HC2. Select Configuration, then Access Control to see the current users.

 

 

HC2 PUSH CONFIGURATION

Please login or register to see this code.

List all users that you want to be able send push messages to. The mobile devices ID can be found by going to http://<HC_IP>/docs/ and looking under iosDevices section. 

Please login or register to see this code.

Select a default user from this list and this is used if there is no user specified as part of the message invocation. 

                               
 

TTS PREFERENCES

Select your TTS preference. If you use the sonos-http-api solution please enter API. 
If you use the Sonos VD Remote solution please enter REM. 

Please login or register to see this code.

Default volume for TTS announcements

Please login or register to see this code.

This allows you to select a default volume and this aplies to both the API and REM sonos solutions. This volume can be changed by including a different volume in the message invocation

 

 

SONOS-API PREFERENCES
Configure this section if you have selected API in the above section.

Please login or register to see this code.

List all the sonos players you want to send TTS messages to.

The zone/player names must match exactly what is on your sonos native application

Please login or register to see this code.

The default player/zone selected is used to unload the TTS message when presentState = Home.

The default player must be included in the overall players list above

Please login or register to see this code.

                          

The ip address and port are of the device that is hosting the sonos-api

Please login or register to see this code.

The final item here is the language or voice code for the respective TTS service. Thisoculd be something like en-gb for google or Amy for AWS Polly
                                 

 

SONOS REMOTE VD PREFERENCES
Configure this section if you have selected REM in the above section.

Please login or register to see this code.

List all the sonos player virtual devices you want to send TTS messages to. The virtual device id's and process button id’s much match exactly what is on your HC2 for each virtual device. Please note the process button may differ if you have modified the standard virtual device. 

Please login or register to see this code.

The default player/zone is user to unload the TTS message when presentState = Home.

This zone must be included in the overall REMplayers table and the name must match exactly.

Please login or register to see this code.

The final item in this section is the language or voice code for the respective TTS service

 

 

DEFAULT TITLES AND SUBTITLES

This scene has default titles and subtitles and these are used if no title or subtitle is included in the message invocation. 

Please login or register to see this code.

Adjust the default titles and subtitles as you require. Note: Subtitles are only used for PopUp Notifications

 

 

NOTIFICATION SERVICES
There is a broad range of notification services available to use. Some are native to the home center and others are third party services provided by external vendors.

Please login or register to see this code.

                               
Select the default notification service that you wish to use. This default service will be used if no service is invoked in the message and is also used as the service to unload the queued messages when presentState = Home

 

 

PUSHOVER CONFIGURATION
This service is provided by pushover.org. You will need to register with them and obtain a token and user key.

Please login or register to see this code.

     
Once registered you will need to select the devices that you wish to send the pushover notifications to. Once they are added to your pushover account you will need to add their details below. Currently there is only one setting for device which means that all messages to pushover will be send to the devices named in this list. Priority can be set at ) like I have below

Please login or register to see this code.

                                  
TELEGRAM CONFIGURATION
This service is provided by telegram.org. You will need to register with them and obtain a token and a chat ID

Please login or register to see this code.

DEBUG VERBOSITY OPTIONS
This allows a number of levels of debug verbosity. There is a minimal amount of debug window responses running in normal mode but these two capabilities allow the user to observe extra information in the debug window when  the scene is running. 

Please login or register to see this code.

 

OCCUPANCY/PRESENCE STATE

I am also supporting the presentState as it is defined by Sankotronic and others.
-- "PresentState" is predefined global value that determines if you are at home
-- or away. This variable value is set by other scene or VD. Enter name of your
-- global variable between "" if called different or leave as it is

Please login or register to see this code.

-- Enter corresponding values that you use for presence in your language. Change
-- the one in quotes or leave as it is

Please login or register to see this code.


HOMETABLE
There is also support for the hometable solution. Hometable is a approach to storing all device ID in a global variable. Please Uncomment the following line if you wish to use Hometable data in scene

Please login or register to see this code.

 

 

POPUP MESSAGE TYPES

Default popup message type, possible values: Success, Info, Warning, Critical.

Please define popup message default popup type, button caption and buttons if you wish

These defaults can be left as is or modified/translated into your own language 

Please login or register to see this code.

Please refer to Sankotronic Tutorial "Popup Notifications and Custom Images" for format and examples

 

POPUP REDIRECT TITLES AND SUBTITLES

Please amend the text sent to PopUp Notification when Internet or TTS is offline to your own language if you wish. Both Title and subtitle can be modified

Please login or register to see this code.

 
SAMPLE MESSAGE INVOCATIONS
The message function can be invoked with as little as one parameter or as many as five parameters. The following examples will provide a good understanding. 
 
Send message to default notification service, with default titles/subtitles

Please login or register to see this code.

Send message to specific notification service
(The notification service must match exactly what is contained in the notifySve table in the variables section)

Please login or register to see this code.

(The hc2user in the message invocation must match exactly what is contained in the hc2emailUsers table in the user configuration section)

Please login or register to see this code.

(The hc2push device in the message invocation must match exactly what is contained in the hc2emailUsers table in the user configuration section)

Please login or register to see this code.

(The sonos player name in the message invocation must match exactly what is contained in either the APIplayers or REMplayers table in the user configuration section)

 

The target can also specify sonos player or VD id for TTS with options

Please login or register to see this code.

Custom titles and subtitles can also be specified. These will overwrite the default titles and subtitles. Subtitles are only available for HC2 Popup notifications. They can be used with or with a target notification. If the target is omitted it will send to the default notification service that has been named in the configuration section

Please login or register to see this code.

Finally an example of a Message to popup with specified popup type

 

Please login or register to see this code.

 

MESSAGE WITH INTERNATIONAL CHARACTERS

 

If you want to send message with special characters just use urlencode function:

Please login or register to see this code.

Please login or register to see this code.

 

COMPANION DEMONSTRATION VD INSTRUCTIONS (1.1)

A number of sample notification and TTS messages can be activated  giving the user an understanding of the message invocation format and options
Demonstration mode enabled the toggling of 'Internet online/offline', presentState Home/Away, sleepState Sleep/Awake modes. This capability allows the used to observe the queuing and unloading of queued notification messages and TTS messages in action. 

 

Import the VD into your home center 2.

Review the messages and adjust based on your own implementation of Smart Message Hub
Send messages and TTS as required
To demonstrate the queuing and unload of queue’s

  1. Set demo mode to ON. 
  2. Send messages and TTS and observe in selected notification services and apps, 
  3. Set internet to offline, sent messages and observe queuing, 
  4. Set internet to online, observer unloading of queue. 
  5. Set presetState to Away, send messages and observe queuing. 
  6. Set presentState to Home and observe unloading of queue. 
  7. Set sleepState to Sleep and observe TTS are silenced. 
  8. For normal operation - set Demo mode to OFF

 

 

FILES

[Smart Message Hub SCENE]  

Please login or register to see this attachment.

    (lua file)

 

WWWAPI Monitor Virtual Device

[VIRTUAL DEVICE] 

Please login or register to see this attachment.

 

Companion Virtual Device

[VIRTUAL DEVICE] 

Please login or register to see this attachment.

  

Edited by AutoFrank
Link to comment
Share on other sites

Recommended Posts

  • 0

Just for all the NOOBS like me that can't get it to work.

 

The demo VD won't do anything if the name of the scene is anything else than "SMsgH v1.1"

 

Its probably stupid of me but I am sure others have the same brain farts as me :)

Link to comment
Share on other sites

  • 0
  • Inquirer
  • 1 hour ago, deloosem said:

    Just for all the NOOBS like me that can't get it to work.

     

    The demo VD won't do anything if the name of the scene is anything else than "SMsgH v1.1"

     

    Its probably stupid of me but I am sure others have the same brain farts as me :)

     

    Hi @deloosem

     

    Yes - this is correct and was deliberate.

    This was so the demo VD would auto-detect the SMsgH scene ID from the scene name and avoid having the user enter the id of their SMsgH scene on their HC2

     

    At the start of every demo vd button their is the following...

     

    Please login or register to see this code.

     

    If you want to have a different name instead of SMsgH v1.1 you could 

    1) change the name from SMsgH v1.1 in the code to you name of choice

    2) change the block of code above to the following and replace 67 with the id of your scene

    Please login or register to see this code.

    That should get the demo vd running...

     

     

    Link to comment
    Share on other sites

    • 0

    SMsgH is great, but I've got 1 doubt.

     

    Is SMsgH safe? What happend if WWWAPI Monitor doesn't know yet, that Internet is offline (because it checks Internet status every 5 minutes in my configuration)? Will I lose my message? Even while pinging every 3 seconds there is risk to lose message.

     

    Maybe SMsgH should ping the Internet by itself before sending every message? What do you think about it?

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • 47 minutes ago, szmyk said:

    SMsgH is great, but I've got 1 doubt.

     

    Is SMsgH safe? What happend if WWWAPI Monitor doesn't know yet, that Internet is offline (because it checks Internet status every 5 minutes in my configuration)? Will I lose my message? Even while pinging every 3 seconds there is risk to lose message.

     

    Maybe SMsgH should ping the Internet by itself before sending every message? What do you think about it?

     

    @szmyk

    I check 6 devices every 250 ms wit my WWWAPI

    Checking the internet every message will delay each message by 5 seconds at least.

     

    If the internet is offline it will send as popup or queue and will be picked up later, no message should be lost...

     

     

     

     

     

    Link to comment
    Share on other sites

    • 0

    Why 5 seconds if it takes only 250 ms as you've written.

     

    Main loop of WWWAPI VD is running every 3 seconds by HC2. It means that if suddenly we lost Internet connection, WWWAPI will know that in 3 sesonds in the worst case. For these 3 seconds all messages will be lost in my opinion.

     

    Of course SMsgH is much better than plain old fibaro api, but it'd be cool to have safe queueing. Maybe additional flag to you api.

     

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • 2 hours ago, szmyk said:

    Why 5 seconds if it takes only 250 ms as you've written.

     

    Main loop of WWWAPI VD is running every 3 seconds by HC2. It means that if suddenly we lost Internet connection, WWWAPI will know that in 3 sesonds in the worst case. For these 3 seconds all messages will be lost in my opinion.

     

    Of course SMsgH is much better than plain old fibaro api, but it'd be cool to have safe queueing. Maybe additional flag to you api.

     

     

    @szmyk

     

    The main loop runs every 3 seconds and with each loop the devices are checked at intervals of 250 seconds so you're correct that in reality each check of the internet is 3 seconds apart. I set mine to 250 ms as I have 6 devices I check and I want to make sure they are all checked within that 3 second window. You're also correct that is the internet was to become unavailable in that window that the message could be lost. I think that the current setup for most users and I certainly wouldn't advocate using it for any life or death situation.

     

    The tcp request I use doesn't have an acknowledge so its not possible to ping the internet and get a go/no go before would mean that I would have to have the VD wait until the request is completely finished which could be up to 4 or 5 seconds

     

    One option may be to use just the WWWAPI to ping the internet alone complete it multiple times during that 3 second window. This may allow you get an earlier indication that the internet is unavailable.   I won't be updating this anytime soon but you're more than welcome to take my code and improve it or make it more responsive. It would be great to hear how you get on....

     

    thanks for the feedback

    _af 

    Link to comment
    Share on other sites

    • 0
    On 13.05.2017 at 8:22 AM, activ said:

    I'm trying to install this scene, but all I manage to get is this error:

    [DEBUG] 08:17:02: line 74: bad argument #1 to 'match' (string expected, got nil)

    [DEBUG] 08:17:02: line 74: bad argument #1 to 'match' (string expected, got nil)

     

    I've found the bug. To fix it we need to change these lines:

    Please login or register to see this code.

    to these ones:

    Please login or register to see this code.

     

    Link to comment
    Share on other sites

    • 0
    17 hours ago, szmyk said:

    Same here. So thanks!

     

    17 hours ago, szmyk said:

    I've found the bug. To fix it we need to change these lines:

    Please login or register to see this code.

    to these ones:

    Please login or register to see this code.

     

     

    Link to comment
    Share on other sites

    • 0

    Great work @AutoFrank! I've been setting it up and testing it this afternoon and your code really works nice and well.

     

    One thing I however cannot get up and running, and that is "following" an sensor instead of manually triggering alerts. My use case is that I have 1 "ON/OFF FIBARO SWITCH" where I setup 2 notifications (by email and push). Because I found that is safer and more reliable that triggering the message from all scenes and devices where I initiate the usage of this specific switch. But also two notications I have setup on my "SENSATIVE STRIP" works this way. 

     

    Does your message center also support this kind of usage? Because I would love to upgrade these notifications to pushover ;-)

     

     

     

     

     

     

     

     

     

    Edited by ckh
    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • 5 hours ago, ckh said:

    Great work @AutoFrank! I've been setting it up and testing it this afternoon and your code really works nice and well.

     

    One thing I however cannot get up and running, and that is "following" an sensor instead of manually triggering alerts. My use case is that I have 1 "ON/OFF FIBARO SWITCH" where I setup 2 notifications (by email and push). Because I found that is safer and more reliable that triggering the message from all scenes and devices where I initiate the usage of this specific switch. But also two notications I have setup on my "SENSATIVE STRIP" works this way. 

     

    Does your message center also support this kind of usage? Because I would love to upgrade these notifications to pushover ;-)

     

     

     

     

     

     

     

     

     

     

    Hi @ckh

    Thanks for the kind comments !!

     

    I'm not 100% sure I follow you but here goes

     

    You want to trigger a message when a switch changes state ?

    .. This cant be done directly as the message hub can only be invoked by a startscene

    if you want to use a scene you could have one that is trigger by the switch (using the scene header) and have that scene just send a message

    I'm reasonably sure that scene triggering via the header is very reliable

     

    if I misunderstood, pleas let me know

     

    Thanks

    _f 

     

    Link to comment
    Share on other sites

    • 0

    Of course....

     

    What was I thinking, thanks! I love the way this was solved for all sensors in one script:  

    Please login or register to see this link.

     So I'll use this as inspiration ;-)

     

     

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • 2 minutes ago, ckh said:

    Of course....

     

    What was I thinking, thanks! I love the way this was solved for all sensors in one script:  

    Please login or register to see this link.

     So I'll use this as inspiration ;-)

     

     

     

    @ckh

    Go for it !!

     

    let me know how you get on...

    Link to comment
    Share on other sites

    • 0

    Hi @autofrank, All my door-notifications are working very well right now. In 1 master script ;-) A nice to have now is however to also use pushover's default option to send high priority alerts. Like 

    Please login or register to see this link.

    . I saw you mostly like TTS messaging when you are at home, any chance your next upgrade might include priority messaging for when you are out of home? #justasking

     

     

    Link to comment
    Share on other sites

    • 0

    @AutoFrank, there is a liitle bug in line 915.

    This line:

    Please login or register to see this code.

    should be:

    Please login or register to see this code.

    Edited by szmyk
    Link to comment
    Share on other sites

    • 0

    WWWAPI Monitor VD and Network Device Monitor VD should be changed to trigger sending queued messages. Actually if Internet comes back online VD sends message first and later changes Internet status. This first message doesn't trigger sending queued messages. Only the second message does it.

     

    My version of LAN Monitor which handles Smart Message Hub and triggers sending queued messages in the first time:

    Please login or register to see this attachment.

    Link to comment
    Share on other sites

    • 0

    @Autofrank and all others,

     

    I created the following helper scene, to both create my own personalised messaging hub and maxime the usage of public scene's such as Smart Messaging Hub. With this code you can hard code notifications in all your scripts in 1 unified format like

     

    Please login or register to see this code.

     

    and then trigger the desired notifications and formats from 1 scene instead of all scenes in your HC2.

     

    --[[ 
    %% autostart
    %% events
    %% properties 
    %% globals
    --]] 
     
    -- read the HomeTable
    local hT = json.decode(fibaro:getGlobalValue("HomeTable"))
     
    -- whether or not to display debug messages
    local debug = hT.Config.Debug
     
    -- how many instances are running
    local nrOfScenes = fibaro:countScenes()
    if debug == 1 then fibaro:debug("New session: total number of concurrent running scenes is now " .. nrOfScenes) end
     
    -- do we have a message to process?
    local messageType = ""
    local messageTitle = ""
    local messageText = ""
     
    local params = fibaro:args()
     
    if (params) then
    for k, v in ipairs(params) do
    if (v.stype) then messageType = v.stype end
    if (v.title) then messageTitle = v.title end
        if (v.message) then messageText = v.message end
    end
    end
     
    if messageText == "" then
    if debug == 1 then fibaro:debug("No new message to process found. Halting.") end
    fibaro:abort()
    end
     
    -- should we sent an alert?
    if messageType == "alert" then
     
      -- sent an alert
    -- INSERT ALERT MESSAGE CODE
     
    -- /INSERT ALERT MESSAGE CODE  
    fibaro:debug("Alert Sent. Title: " .. messageTitle .. ". Message: " .. messageText .. ".")
     
     -- should we sent a notification?
    elseif messageType == "notification" then
     
      -- sent a notification
    -- INSERT NOTIFICATION MESSAGE CODE
     
    -- /INSERT NOTIFICATION MESSAGE CODE  
    fibaro:debug("Notification Sent. Title: " .. messageTitle .. ". Message: " .. messageText .. ".")
     
    -- and else, we log a debug message
    else
    fibaro:debug("Unknown message format to process found. Halting.")
    fibaro:abort()
    end
    Edited by ckh
    Link to comment
    Share on other sites

    • 0
    On 25.04.2017 at 10:14 PM, Sankotronic said:

    Hi @AutoFrank,

     

    I have problem with sending letters with accents and emojis to SMsgH scene. I try to replace them with UTF codes but still the same. It's about this letters "ČčĆ抚ĐđŽžáäéè" and so on.

    @AutoFrank, @Sankotronic, @DonQuischopp

     

    I've found a solution :)

     

    Add this code to the SMsgH at "HELPER FUNCTIONS" section:

    Please login or register to see this code.

    and replace this line:

    Please login or register to see this code.

    with this code:

    Please login or register to see this code.

    If you want to send message with special characters just use urlencode function:

    Please login or register to see this code.

     

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • 14 minutes ago, szmyk said:

    @AutoFrank, @Sankotronic, @DonQuischopp

     

    I've found a solution :)

     

    Add this code to the SMsgH at "HELPER FUNCTIONS" section:

    Please login or register to see this code.

    and replace this line:

    Please login or register to see this code.

    with this code:

    Please login or register to see this code.

    If you want to send message with special characters just use urlencode function:

    Please login or register to see this code.

     

     

     

    good find @szmyk:-)

     

    Link to comment
    Share on other sites

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Answer this question...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...